Tunnelled Application Link Error: "No response was received from the URL you entered - it may not be valid. Please fix the URL below, if needed, and click Continue"
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
When generating a tunneled application link, Jira Cloud - Application links produce the following error message:
"No response was received from the URL you entered - it may not be valid. Please fix the URL below, if needed, and click Continue"
Environment
Jira Data Center 9.x
Diagnosis
A configured Application Tunnel exists between Atlassian Cloud and Jira Data Center, indicated as being connected.
However, when trying to establish a Tunnelled Application Link, communication with the target application (Jira Data Center instance) cannot be established.
The subsequent error message was identified in the cloud log:
1
2
3
4
msg: com.atlassian.sal.api.net.ResponseStatusException: Unexpected status: 500
stack: com.atlassian.applinks.spi.manifest.ManifestNotFoundException: com.atlassian.sal.api.net.ResponseStatusException: Unexpected status: 500
at com.atlassian.applinks.core.manifest.AppLinksManifestDownloader.doDownload(AppLinksManifestDownloader.java:238)
at com.atlassian.applinks.core.manifest.AppLinksManifestDownloader$1$1.<init>(AppLinksManifestDownloader.java:169)After examining the application log, it has come to notice that instead of the specified port 8089 (the same port number you used for the HTTP connector) defined in the system property, the application is making calls to default port 8093. This situation typically arises when the port specified during system startup is either already in use or hasn't been configured correctly:
1 22023-10-10 07:23:51,884+0000 tunnel-executor:thread-1 DEBUG userxxxx 323x25137x2 kn1hvk 10.174.51.98 /rest/secure-tunneling/latest/tunnel [c.a.tunnel.process.InletsClientManager] [INLETS CLIENT] 2023/06/19 05:23:51 Starting client - version 2.1.0-atlassian1-31-g33b2f95 2023-10-10 07:23:51,884+0000 tunnel-executor:thread-1 DEBUG userxxxx 323x25137x2 kn1hvk 10.174.51.98 /rest/secure-tunneling/latest/tunnel [c.a.tunnel.process.InletsClientManager] [INLETS CLIENT] 2023/06/19 05:23:51 Upstream: ****** => http://127.0.0.1:8093Upon reviewing the Jira startup configuration, it has been recognized that the startup parameter designated for the upstream port is delimited by a comma instead of a space within the quotation marks:
1JVM_SUPPORT_RECOMMENDED_ARGS="-Dhttp.socketTimeout=60000 -Djava.net.preferIPv4Stack=true,-Dsecure.tunnel.upstream.port=8089"
Cause
When initiating the creation of an Application Link within an Atlassian application, an attempt is made to establish a connection with the target application's manifest. This manifest holds crucial details such as the target application's id, name, type, version, application link version, and authentication types. Failure to retrieve this information will lead to an unsuccessful creation of the application link.
With the Application Tunnel configured, users should now be able to create their Application Links using the recently created tunnel, however, if something goes wrong with the upstream port configuration, it can result in the following error:
1
"No response was received from the URL you entered - it may not be valid. Please fix the URL below, if needed, and click Continue"Solution
In this particular scenario, address the configuration of the upstream port by ensuring that the parameter "-Dsecure.tunnel.upstream.port=$portNumber" for JVM_SUPPORT_RECOMMENDED_ARGS is properly defined within the setenv.sh file, with space separation within the quotation marks.
Was this helpful?