We’re renaming ‘products’ to ‘apps’

Atlassian 'products’ are now ‘apps’. You may see both terms used across our documentation as we roll out this terminology change. Here’s why we’re making this change

Troubleshoot application tunnels

Who can do this?
Role: Organization admin
Atlassian Cloud: All plans
Atlassian Government Cloud: Not available

Here’s some troubleshooting information for application tunnels.

Enable extra logging in your Data Center instance

If you can’t find the solution on this page, set the log level for the com.atlassian.tunnel to TRACE and look for references for the key classes:

  • TunnelConnectionService

  • InletsClientManager

  • TunnelClientProcessStateManager

  • InletsClientProcessFactory

For more info on how to enable logging for different Data Center products, see:

Check connections of application tunnels

In admin.atlassian.com, you can check the connection of application tunnels. It’s a set of health checks that we run against the tunnels to make sure they’re working correctly. If there’s a problem, an appropriate status will be displayed.

To check the connections:

  1. Go to admin.atlassian.com.

  2. Select Settings > Application tunnels.

  3. In the top-right, select Check connections.

Here are some common problems indicated by the statuses. Note that some statuses are different between Cloud and Data Center.

Status in cloud

Status

Description

Incomplete

The tunnel has been created in admin.atlassian.com, but its security key hasn’t beed added to your Data Center instance.

To solve this issue:

  1. Edit the tunnel in admin.atlassian.com, and copy the security key.

  2. Add the key to your Data Center instance.

Unavailable

The tunnel is unavailable right now. There are a few issues that might cause this:

  • Application tunnels in Cloud were temporarily down and your Data Center instance hasn’t reconnected yet. Wait until the status changes, as your instance might still be attempting to connect.

  • The security key in your Data Center instance is incorrect or no longer valid. Make sure the key is correct or generate a new one.

  • Your Data Center instance is down.

Misconfigured

The tunnel is misconfigured. This usually happens when you create a tunnel without configuring the required connections and upstream ports in your Data Center instance.

To solve this issue:

Error

The tunnel isn’t working, but we’re unable to determine an exact cause. This is usually caused by problems with your Data Center instance, so try the following actions:

  • Check the state of your Data Center instance.

  • Check the log files in your Data Center instance.

  • Regenerate the security key and update it in your Data Center instance.

  • Recreate the tunnel.

Timed out

We tried checking the status, but didn’t get any response from the tunnel.

To solve this issue:

  • Your Data Center instance might be under heavy load and can’t service this check. Reduce the load on this instance and bring it back to a healthy state.

  • The check might be timing out because of network issues. Investigate the network connection of your Data Center instance.

Status in your Data Center instance

Status

Description

Unavailable

Your Data Center instance can’t authenticate to the tunnel server in Cloud.

To solve this issue:

  1. Regenerate the security key to make sure it’s up to date.

  2. Add the new security key to your Data Center instance.

Limited

Some Data Center nodes aren’t connected to the tunnel. The connection performance is degraded.

To solve this issue:

  1. Go to Administration > Clustering.

  2. Check the status of your Data Center nodes to make sure they’re up and running.

Error

Application tunnels in Cloud are either being restarted or not working.

To solve this issue:

  1. Wait and check if the status changes. This might be a temporary restart caused by some other issue on our side.

  2. Check the Data Center log files to determine the cause.

  3. If these solutions don’t help, recreate the tunnel.

Connecting (for a long period of time)

At least one of the nodes hasn’t connected to the tunnel. You can try the following solutions:

  • In your Data Center instance, go to Administration > Clustering and check the status of your nodes to make sure they’re up and running.

  • Enable logging to get more information

Connected (and no response after creating application links)

Try the following actions:

  • Make sure you used the right application tunnel for your application link.

  • Make sure you have completed the required configuration steps that include adding a HTTP connector and upstream port. Learn how to configure application tunnels.

  • Make sure the base URL of your Data Center instance is correct.

Other problems

Status

Description

Application links show Config error on both instances

This issue often appears when the reciprocal link on the Data Center instance is created by a different admin. In such a case, the application link in your cloud app might be created with the local authentication disabled, while it should be set to OAuth.

To fix this:

  1. Edit the application link in your cloud app.

  2. Set the Local authentication to OAuth for both outgoing and incoming communication.

Details of an application link, showing Local authentication set to OAuth for both directions.

Still need help?

The Atlassian Community is here for you.