Users cannot access to the project release page
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
Problem
Users get The Jira server could not be contacted. This may be a temporary glitch or the server may be down error when they try to access the Releases page.
The request is done successfully on the server-side but the following appears in the console logs when a HAR file is generated:
1
batch.js?agile_global_admin_condition=true&jag=true&jaguser=true&locale=en-SE:5257 GET https://xxxxxxxx/rest/projects/1.0/project/PROJECT_KEY/release/allversions-nodetails?_=1646216837011 net::ERR_CONNECTION_RESET 200Diagnosis
Environment
Any relevant information that clarifies the environment that an issue occurs in such as Database (type and version/s), Browser (type and version/s), OS (type and version/s), Java version, etc...
Diagnostic Steps
HAR file indicates that the transaction runs for a long time (in this example, it's more than 30 seconds)
Check if the proxy timeout is shorter than the server response time or not
If possible, bypass the proxy, log in to one of the Jira nodes over node IP and Tomcat connector port which is defined in the server.xml, and see if you can access the related page.
Cause
One of the root causes here is the proxy timeout parameter being shorter than the server response time.
Solution
Workaround
If this is the case, increase the load balancer/proxy timeout duration to a higher value. Also, consult Atlassian Support to understand why it takes so long.
Was this helpful?