Can't configure .NET Agent for SaaS Controller

[CommunityUser]

I received an email with my SaaS hostname and port, but when I put it into the dialog in agent configuration, it tells me:

If I use SSL:

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.

If I don't:

Controller communication failed. Details: The underlying connection was closed: The connection was closed unexpectedly.

I assume '443' means I should use SSL?

What gives? New Relic wasn't this difficult...

Jeff

[Theo_Jungeblut · Accepted solution]

Hi Jeff,

From the information you provided it seems there is an authentication error (401) happening.

Did you put in the SaaS credentials as provided? You find details here:

https://docs.appdynamics.com/display/PRO13S/Configure+the+App+Agent+for+.NET

After addressing the authentication issue the setup should be straight forward but if you have questions regard HTTP setup you find details here:

https://docs.appdynamics.com/display/PRO39/Enable+SSL+for+.NET

If neither of this information helped addressing the issue please let us know and we assist you further.

Kind regards,

Theo 

[CommunityUser]

For those who are looking for the access key, it can be found in your portal under the license section.

The documentation should be updated to indicate this. It should not be assumed a first-time installer will know to look there.

[CommunityUser]

hello,

i am getting a similar error 

Controller communication failed. Details: The remote name could not be resolved: 'none7530.saas.appdynamics.com'
Please use certmgr.msc to add Controller Certification Authority certificate to
"Trusted Root Certification Authorities" at computer account (system) level.

how can this be resolved?

Regards,

[Theo_Jungeblut]

Did you follow the steps for SSL:

https://docs.appdynamics.com/display/PRO41/Enable+SSL+for+.NET

Cheers,

Theo

[CommunityUser]

Hi,

I also opened a trial account and gets an error :

"Controller communication failed. Details: Unable to connect to the remote server
Please use certmgr.msc to add Controller Certification Authority certificate to
"Trusted Root Certification Authorities" at computer account (system) level."

I also get it when I tried to turn off SSL in the controller side, and change the port to 80.

Till now I couldn't find any simple documentation regarding where to import the AppDynamics certificate from.

Pretty dissappointing onboarding experience.

[Jean-Baptiste_M]

Sorry for this disappointment, Ofer.
Have a look here:
https://docs.appdynamics.com/display/PRO42/Enable+SSL+for+.NET

By the way, if you use the controller OnPrem it is by default on port 8090
for HTTP and port 8181 for SSL.
For SaaS, you cannot use HTTP.
Hope it helps and provide a better experience.
JB

[CommunityUser]

Thanks.

Already saw this guide, unfortunately it didn't help.

The only relevant paragraph which relates to my case is the following:

"

• The AppDynamics SaaS Controller uses certificates signed by DigiCert. In some cases, SaaS customers must import the DigiCert root certificates into the Windows Trusted Root Certification Authorities store.

"

There's no explanation regarding how to do so, and besides, I have 3 DigiCert certificates in the Trusted Root Certification Authorities list:

DigiCert Assured ID Root CA

DigiCert Global Root CA

DigiCert High Assurance EV Root CA

Using Windows 8.1 Enterprise.

[Matt_Jensen]

Hi there! 

The error you provided is a bit misleading (we're working to make it more clear).

The important part of the meessage is this: Details: Unable to connect to the remote server.  This means that there is no network connectivity from your Agent to the SaaS controller. If SSL negotiation was the issue, you'd see an error message that looked like this "The remote certificate is invalid according to the validation procedure." The majority of customers won't need any special SSL configuration because most up to date Windows servers  trust Digicert as a Certificate Authority by default. 

That said, to troubleshoot this, please verify that you can access your controller using the same address/port using Internet Explorer from the server that the agent is installed on.  If this works,  it's very likely the Web Browser on your server is using a Proxy which will need to be added in the Agent Configuration Wizard so that the agent can use it as well. If this doesn't work, you'll need to talk to your Network team to ensure there is network connectivity from the Agent server to the Controller.

I hope this helps!

Thanks,

Matt

[CommunityUser]

Hi,

Thanks for your reply.

Connection from browser (both IE and Chrome) succeeds - it leads to the URL https://soluto.saas.appdynamics.com/controller/#/location=AD_HOME_OVERVIEW

However, in the .NET Agent configuration wizart, I still get an error: "Controller communication failed. Details: The remote server returned an error: (401) Unauthorized."

I checked with our network team, we don't have any proxy configuration. Also, there are no blocks from my machine in the Firewall log.

Ofer

[Matt_Jensen]

401 Unauthorized means that the account name or account access key is
invalid (or there is a proxy blocking access, which we can rule out if no
proxy is in use).

[CommunityUser]

Details were taken directly from the subscription page.

However, I now noticed that the "Account name" text box was disabled, although it contained a wrong name - "customer1".

Only when I checked the "Multi-Tenant Controller" box I could edit it. When I changed to "Soluto" the connection succeeded.

This interface is so confusing, it really needs a facelift...

Thanks for your help.

[Matt_Jensen]

Happy to hear it's working for you now, Ofer.   Thanks for the feedback. I've noted this discussion internally as part of our efforts to enhance the Wizard.

Take care,

Matt

[CommunityUser]

Hi,

Still waiting for a solution. I'm writing here since I didn't find any direct way to contact your support.

Ofer

[Jean-Baptiste_M]

help@appdynamics.com 😉

[CodePoet]

The issue I just spent figuring out is that selecting EnableSsl still lists the port as 80. The actual ssl port is 443 hence the certificate error. So changing 80 to 443 made the certificate error go away and things work correctly.

[CommunityUser]

I was being stupid and not providing the username/accesscode.

My bad