We set up a application link between our JIRA server and our Bitbucket server. Both run on different host in the same network. The link from JIRA to Bitbucket works perfect. In the other direction I'm shown an 503 error.
In the other direction I'm shown an 503 error (service unavailable). If I log onto the Bitbucket server, I can open our JIRA instance.
What can I do to resolve that? Why is it only working one way?
Are you using SSL on JIRA? If so, I'd bet something is wrong with your SSL cert configuration. Application links are pretty sensitive to SSL being set up exactly right. You may have skipped setting up the intermediate cert or need to import your JIRA self-signed cert in to the Java key store on Bitbucket. I hope that helps point you in the right direction.
The problem is with JIRA. Somehow the Application Link is not happy with the way it is connecting to the JIRA Application. Do you have a reverse proxy server ahead of JIRA? If so, have you modified JIRA's server.xml to add in the proxy configuration lines?
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot