Connection Problems

If your browser cannot connect to the Splunk AppDynamics EUM cloud and you use an on-premises Controller, but not an on-premises EUM Server, it is possible that:

You have no Internet connectivity
A firewall is blocking the port

Verify Connectivity

Navigate to eumaggregator/ping SaaS Domains and select your geolocation. Find the EUM API Domain and add the following endpoint:

If you receive a "ping" in the panel, you should be able to connect to the EUM Cloud.

Note: If you are using IE on a Windows system, make sure the browser itself does not have a proxy (with authentication) set up. If it does, the test link may work but not the actual connection.

Make sure you have also unblocked any firewalls and verified the keystore entries.

Unblock Your Firewall

The Controller needs to be able to use HTTP over SSL (HTTPS) on port 443 to reach the EUM Cloud Aggregator in your region.

Navigate to SaaS Domains and select your geolocation. Find the EUM API Domain and add the following endpoint: eumaggregator/ping.

If your Controller is behind a firewall, you can either open your Controller's firewall or use a forward proxy.

To open the firewall, see the instructions unique to your firewall.

Note: You only need to open the firewall for the specific host and port, not for the entire *.eum-appdynamics.com domain.

Use a Forward Proxy

Set up an HTTP proxy to your SaaS EUM API Server. Navigate to SaaS Domains and select your geolocation. Find the EUM API Domain and add the following endpoint: eumaggregator/ping .

Note: This is a cleartext/pass-through proxy. Authentication is not supported on the first level. If the client network itself requires authentication, you must set up an intermediate proxy between your Controller and this proxy to pass on the credentials you need to get out of your network.
Configure the HTTP proxy host and port in the <Controller-Installation-Directory>/appserver/glassfish/domains/domain1/config/domain.xml file by adding the following JVM options to the existing java-config element:
```
<jvm-options>
     -Dappdynamics.controller.http.proxyHost=myhost
</jvm-options>
<jvm-options>
     -Dappdynamics.controller.http.proxyPort=8888
</jvm-options>
```
Restart the Controller's app server.