cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Not a customer? Start a free trial

Click the Start a free trial link to start a 15-day SaaS trial of our product and join our community as a trial user. If you are an existing customer do not start a free trial.

AppDynamics customers and established members should click the sign in button to authenticate.

NET (Agent, Installation)

Failed to contact Controller : 401 Unauthorized

Failed to contact Controller : 401 Unauthorized

Dear Support,

 

When configuring the .Net Agent to connect the controller in SAAS mode, I get the following error message :

 

Controller communication failed. Details: The remote server returned an error: (401) Unauthorized.
Please use certmgr.msc to add Controller Certification Authority certificate to
"Trusted Root Certification Authorities" at computer account (system) level.

I follow this doc with no succes : https://docs.appdynamics.com/display/PRO42/Enable+SSL+for+.NET

 

 

We have a proxy beetween .Net Agent and Controller.

When we use Internet Explorer, we get access to the Controller.

 

Do you have any idea ?

 

Best regards

By replying you agree to the Terms and Conditions of the AppDynamics Community.
Failed to contact Controller : 401 Unauthorized
2 REPLIES 2
Raunak.Mohanty
AppDynamics Team (Retired)

Re: Failed to contact Controller : 401 Unauthorized

Hi Stephane,

 

   This does not seem to be SSL related issue. Infact SSL related error message is just an red herring.

The issue seems to be with "Account Access Key" which you are using at config.xml. Can you double check the value there? Please run the AppDynamics Agent configuration tool and verify all the Account level information is correct.

 

Thanks,

Raunak



Found something helpful? Click the Accept as Solution button to help others find answers faster.
Liked something? Click the Thumbs Up button.
jayaram.sai
Creator

Re: Failed to contact Controller : 401 Unauthorized

same here... correcting the account access key resolved the issue.

 

i was mislead with this message and ended up downloading the CERTs for the controller and updating it in agent side Windows machine