AppD Archive

controller configuration: configuration server failed

CommunityUser
Splunk Employee
Splunk Employee

  Ive gotten the server installed when I go to add it I get

Controller communication failed. Details: The remote server returned an error: (404) Not Found.

using  mycustomername.saas.appdynamics.com/controller


Port 80

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

Hi,

 I think you are trying to test the controller connection from App Agent using the below Server Name

mycustomername.saas.appdynamics.com/controller

If I am correct please remove the " /controller" and try the below server name for controller configuration.

 

mycustomername.saas.appdynamics.com

Please get back if the issue persists.

Regards,

Swapna.

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

Hi, I'm having the same problem and that didn't solve my issue.

I receive this message.

There is something comfusing people I think.

This video says to introduce localhost rather than what you say.

https://appdynamics-static.com/education/video/dotNETAgentManualInstallationandConfiguration/dotNETA...

I receive this message when introducing xxxx.saas.appdynamics.com

Controller communication failed. Details: Unable to connect to the remote server


And this message when inserting localhost 8090 (as video suggest)

Controller communication failed. Details: Unable to connect to the remote server

 


One more thing, where should I install the agent? in my Windows PC or in my Windows Server box, where the application is? 

0 Karma

Venu_Babu_Thang
Communicator

Hi Walter,

The AppDynamics Agent should be installed on the server where your application is hosted and you would like to instrument it. 

To test the controller connectivity, please run the AppDynamics Agent Configuration wizard and on "Controller Configuration" tab enter the controller Server(Name/IP) and port details and click on "Test Controller connection" button.

For an on-premise Controller, use the value for Application Server Host Name you provided when you installed the Controller. If you use the AppDynamics SaaS Controller, see the Welcome email from AppDynamics.

The Controller port attribute specifies the HTTP(S) port of the AppDynamics Controller. If the Controller ssl attribute is set to true, specify the HTTPS port of the Controller; otherwise specify the HTTP port.

For On-premise installations, the defaults are port 8090 for HTTP and port 8181 for HTTPS.

For the SaaS Controller, use port 80 for HTTP or port 443 for HTTPS.

If you still face any connectivity issues, please open the controller in IE(Internet Explorer) and check if you are able to access it.  Also, check if you are configured any proxy on the server(where AppDynamics Agent is installed). If yes, please configure the proxy in AppDynamics Agent Configuration wizard and check the connectivity.

For on-premise Controller installations, open a browser at:
http://<Application_Server_Host_Name>:<HTTP_Listener_Port>/controller


For the SaaS Controller Service, open a browser at the URL provided to you by AppDynamics.
http(s)://<customer>.saas.appdynamics.com/controller

Please let us know if you face any issues.

Thanks,

Venu.

0 Karma
Get Updates on the Splunk Community!

See just what you’ve been missing | Observability tracks at Splunk University

Looking to sharpen your observability skills so you can better understand how to collect and analyze data from ...

Weezer at .conf25? Say it ain’t so!

Hello Splunkers, The countdown to .conf25 is on-and we've just turned up the volume! We're thrilled to ...

How SC4S Makes Suricata Logs Ingestion Simple

Network security monitoring has become increasingly critical for organizations of all sizes. Splunk has ...