Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

How do I set up an application link from Bitbucket DC v.8.18.0 to Jira DC v.10.3.6 on the same host?

Kevin Nelson July 11, 2025

When trying to set up an application connection from Jira to Bitbucket, I'm getting "No response was received from the URL (our Bitbucket URL) - it may not be valid.  Both applications are on the same host on different ports, so I configured JIra to allow all hosts.  However, I have not found instructions for configuring Bitbucket to allow all hosts.  I tried the same think in bitbucket.properties, but it still gives me a warning about "local host" and "restricted addresses"  How can I set up the application link between Jira and Bitbucket?  

1 answer

0 votes
Aman Shrivastava
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
July 11, 2025

Hi @Kevin Nelson 

Atlassian advises installing different products on separate servers. However, if you're only installing to test features, it's acceptable, and the applink should function in this scenario too. You need to ensure the network and SSL connectivity to both application URLs. Since both applications are on the same server, you can execute the commands on the same server.

  • Check application connectivity using the following commands on the Linux server running both applications; both should return a RUNNING status. If there's a timeout, your Linux/Network firewall may be blocking the connection and you will need to fix it
curl <Bitbucket-Base-URL>/status
curl <Jira-Base-URL>/status
  • If you access both applications using HTTPS, download the SSLPoke utility from here and copy it to the Linux server where the applications are running.
    Execute the following command as detailed in the KB article from the same path where you copied the file. If you see the error "PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target" instead of a CONNECTED status, follow this KB article to import the certificate into the Java trust store, restart Bitbucket and Jira applications and then create the application link. 

 

$JAVA_HOME/bin/java SSLPoke <Jira-domain> 443
$JAVA_HOME/bin/java SSLPoke <Bitbucket-domain> 443


Regards,
Aman 

Kevin Nelson July 14, 2025

Thanks for the response.  Connectivity is confirmed.  SSL Certificate is confirmed.  Your reply:  “However, if you're only installing to test features, it's acceptable, and the applink should function in this scenario too.”, however is not confirmed.  The same server configuration works fine for Confluence to Jira link, just not Bitbucket to Jira link.  All links were working prior to upgrade.  Separate servers is not an option in this scenario. 

I’m sure that this can be done as this is how the applications have functioned for years in the past.  If not, this should be communicated by Atlassian in any upgrade procedures.

 

Thanks,

K

Aman Shrivastava
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
July 14, 2025

Hi @Kevin Nelson 

If the SSL connectivity is up then there might be some thing on the application level that might be restricting the application link creation. I would suggest to raise a ticket to support team to get it checked.
What I meant was that the production application shouldn't be installed on the same server, with performance being one of the primary reasons. It's ok if you're using it for testing purposes. However, the applink should still work correctly even if both applications are running on the same server.

Regards,
Aman

Kevin Nelson July 14, 2025

I agree, it is something at the application level.  In Confluence, you can set a Java switch to allow all hosts.  As long as they're on different ports, it all works.  However that same thing does not work with Bitbucket.  I understand the desire to install applications on different hosts, but I inherited this configuration and have to deal with it.  This configuration worked for many years before the latest upgrades in Atlassian software.  

Thanks,

k

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
SERVER
VERSION
8.18.0
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events