Troubleshoot application connectivity

How to get your application back up and running.

The application card displays status information about your application. If the application status on the card appears as “App is down,” then the application’s server is not reachable by the EAA connector. Note that the health status will not update automatically. It may also be the case that your applications deploy but do not work when users try to access them. Complete these steps to troubleshoot.

How to

  1. Check that the application origin server is running. Try to access the application without using EAA. If the application can be accessed without EAA, continue troubleshooting.
  2. Make sure the application is deployed. See Deploy the application.
  3. Test connector connectivity to applications with troubleshooting tools.
  4. Review the application’s access parameters in EAA and make changes as needed. To learn more about the access parameter fields see Configure access parameters for an application, Configure and deploy a SSH application, or Configure and deploy a remote desktop (RDP) application. Issues are commonly found with the information entered into these fields:
    1. Application IP/FQDN protocol. Verify the protocol, such as SSH, HTTP, or HTTPS, is correct based on the application profile.
    2. Application IP/FQDN first field. Verify the IP address or URL to access the application within your network is correct as it appears in the field and that the fully qualified domain name (FQDN) resolves to that IP.
    3. Application IP/FQDN second field. Verify the IP port number is correct.
    4. For SSH applications check these fields. SSH Username: If you identify an SSH username for the application, the application asks for a password at login. If you do not identify an SSH username for the application, the applications asks for both a username and password at login. SSH Private Key and SSH Passphrase: If your SSH server is set up with SSH keys, you can enter your private key and optionally your SSH passphrase. If your server requires an SSH passphrase and you did not choose to enter it here, you will have to enter it every time you access SSH server via EAA.
  5. Make sure that the CNAME is configured correctly on the DNS server.
    1. To learn more about configuring a CNAME redirect see Set up a CNAME redirect for an application.
    2. To test whether a DNS server resolves to an IP address, Run a connector troubleshooting utility using the dig tool.
  6. Make sure the directory can be reached by the connector. Test connectivity between the directory and connector.
  7. Make sure the EAA health check is configured correctly. You configure health check information as part of the following:
  8. For remote desktop protocol applications (RDP), make sure the server Network Level Authentication field is unchecked. See Connect a Microsoft Windows server to an RDP application.

Next steps

If you need to continue troubleshooting, see Troubleshooting overview and tips.