Unable to create or edit issues using port number after upgrading to JIRA 7

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

  1. After upgrading from JIRA 6.x.x to JIRA 7.x.x, it is not possible to edit or create any issues in Jira when using port number for example 8080.

  2. There are no issues editing or creating issues in JIRA when using the proxy URL

  3. Although there are no issues creating or editing issues using the FQDN, for example, http://jira.atlassian.com, the user requires issues to be created or edited using http://jira.atlassian.com:8080 because of 3rd party integrations such as the Kantata (formerly Mavenlink) connector.

Diagnosis

Environment

Diagnostic Steps

  1. Ensure that there is only one connector configured on the server.xml :

    1 2 3 4 5 6 7 8 9 10 11 12 13 <Connector port="8080" proxyName="jira.atlassian.com" proxyPort="80" maxThreads="150" minSpareThreads="25" connectionTimeout="20000" enableLookups="false" maxHttpHeaderSize="8192" protocol="HTTP/1.1" useBodyEncodingForURI="true" redirectPort="8443" acceptCount="100" disableUploadTimeout="true"/>

  2. Access JIRA using http://jira.atlassian.com:8080

  3. It will not be possible to create or edit an issue

  4. Recording a HAR file as per Generating HAR files and analyzing web requests while reproducing the issue will display the error XSRF check failed / 403 Forbidden

    (Auto-migrated image: description temporarily unavailable)

Cause

Is is not possible to use the same port number that is being used by the proxy to create or edit issues in JIRA.

Solution

Resolution

  1. Stop JIRA

  2. Add a 2nd HTTP connector to the JIRA_INSTALL/conf/server.xml file:

    1 2 3 4 5 6 7 8 9 10 11 <Connector port="8081" maxThreads="150" minSpareThreads="25" connectionTimeout="20000" enableLookups="false" maxHttpHeaderSize="8192" protocol="HTTP/1.1" useBodyEncodingForURI="true" redirectPort="8443" acceptCount="100" disableUploadTimeout="true"/>

  3. Start JIRA and the access JIRA using http://<domain>:8081

  4. It is now possible to create or edit issues using http://<domain>:8081 and http://<domain>

Updated on April 2, 2025
Platform
Data Center only
Product
Jira Software Data Center
On this pageSummaryDiagnosisCauseSolution

Still need help?

The Atlassian Community is here for you.
Ask the Community