Forums

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

JIRA Server is having difficulty contacting Bitbucket Server

CAMTECH SAS
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
October 2, 2019
  • Screen Shot 2019-10-02 at 12.44.34 PM.pngJira is having difficulty contacting Atlassian Bamboo, fisheye, and Bitbucket. If this condition persists, please contact your Jira administrators.

  • We try everything In the web, application link, project links, permissions.

  • Jira is configure users with LDAP, and Bitbucket with Jira.
  • We install the products according to the official documentation, and following every step and requirement.
  • We don't know something more to do!

1 answer

1 accepted

0 votes
Answer accepted
Andy Heinzer
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
October 3, 2019

Hi

Sorry to hear that Jira is having problems trying to connect to these other development tools.  There are number of different possible causes for these kinds of errors.  Unfortunately the web interface of Jira isn't very good at telling us more information about why this is happening.

Ideally, we would want you to recreate this error once more, and then take a look immediately in the $JIRAHOME/log/atlassian-jira.log file.  This log file should be recording some more details about why this might be failing in Jira.

I ran across two Jira KBs that have clear and specific error messages in the logs that might be applicable here:

  1. JIRA shows "JIRA is having difficulty contacting <Application>. If this condition persists, please contact your JIRA Administrators" message in the Development Panel 
  2. JIRA throws "JIRA is having difficulty contacting <application name>. If this condition persists, please contact your JIRA administrators." in the Development Panel 

The first KB deals with the system clock of the host operating system for Jira and Bitbucket being too far out of sync.  When this happens, the OAuth authorization fails.

The second KB deals with a scenario where the database that Jira is using on the backend might not have the needed permissions to be able to search in SQL as expected.  However before trying either resolution, I would want to make sure that you see the corresponding logs that indicate this is the problem.

If neither of those apply, then there is a third more general troubleshooting KB for this topic that also contains a few different causes for this error here, check out Troubleshoot the Development Panel in Jira server.

If you are having any trouble following these steps, I would be interested to see if we can take a closer look at your Jira logs to see if we can be additional assistance in pinning down the root cause here.

Cheers,

Andy

CAMTECH SAS
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
October 3, 2019

The problem was with the database, the requirements must be fully met to work well! Thanks for your advice!

Like Andy Heinzer likes this

Suggest an answer

Log in or Sign up to answer