New to administering Atlassian cloud products? Learn about Atlassian organizations and what it means to be an organization admin.
Managing products from an organization? Learn what's available to organization admins.
Need to control change in cloud? Test and manage product changes for Jira and Confluence Cloud.
Need to integrate your Atlassian products? Use application tunnels to connect your organization to the products in your network.
Are users signing up for products you don’t know about? Learn how to control the cost and security of your product footprint.
Adding or reorganizing teams? Move projects, spaces, users, and other data from one instance of a product to another
Understand more about our artificial intelligence features and determine if AI is right for your organization
Enable HIPAA compliance for eligible Atlassian products and protect your sensitive data.
Enterprise-grade scale, security, and governance controls for Jira Software, Confluence, and Jira Service Management
Stay on top of users and data across your organization with all the reports and tracking options we offer.
Here’s some troubleshooting information for application tunnels.
Enable extra logging in your self-managed 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:
For more info on how to enable logging for different products, see:
Jira: Logging and profiling
Confluence: Configure logging
Bitbucket: Enable debug logging
Bamboo: Logging in Bamboo
You might encounter the following issues:
Status is Error
Because of an incident on our side, some application tunnels might have stopped working. If a tunnel worked previously, but now displays the Error status, restart the Marketplace app in your self-managed instance.
Status is Unavailable in the self-managed instance
The tunnel client (Marketplace app) can’t connect to the tunnel server in Atlassian Cloud. You need to enable logging to identify the cause.
Status is Error in the self-managed instance
The tunnel client was able to reach the tunnel server, but it can’t validate the security key. Make sure the key you added is correct. You can also regenerate the key, or delete the tunnel and create a new one.
Status remains in Connecting in the self-managed instance
At least one of the nodes hasn’t connected to the tunnel. You can try the following solutions:
Status is Connected, but there’s no response after creating application links
Try the following actions:
Application links show Config error on both instances
This issue often appears when the reciprocal link on the self-managed instance is created by a different admin. In such a case, the application link in your Cloud product might be created with the local authentication disabled, while it should be set to OAuth.
To fix this:
Was this helpful?