nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

HTTP Status 405 Error after upgrade

andrea price

I just upgraded JIRA Software/Core from 8.21 to 9.1. We are able to log into JIRA to open tickets, and we can directly access tickets. However, when we try to access administrative menus such as Projects we get an error -

HTTP Status 405 - Method Not Allowed

Type Status Report

Description The method received in the request-line is known by the origin server but not supported by the target resource.

Apache Tomcat/9.0.63

Accepted answers

Kris Jacobs_jsdjl8

I think I have found the problem on our instance. I upgraded Jira Software from 8.x to 9.1.0, but Jira Service Management is still at 4.20

So I'll need to get JSM up to 5.10 and go from there.

All comments

Benjamin_tmh9yg

Hi @andrea price ,

On your upgrade report, was there any reported issues? Are you able to get to the troubleshooting and support page to see if there is any health issue? Also, take a look at your jira logs to see on further details on the issue.

Also, try logging into incognito incase something is cache.

-Ben

Kris Jacobs_jsdjl8

I am experiencing the exact same problem, exact same scenario as Andrea's original post.

I narrowed it down to my two SERVICE Projects - SOFTWARE Projects work fine.

Jira Service Management, on premise install.

Browse Projects Page

Click on the Maintenance Project, URL = https://jira.ourdomain.name/browse/MAINT

URL changes to https://jira.ourdomain.name/projects/MAINT/queues which displays the Tomcat error page:

HTTP Status 405 – Method Not Allowed

Type Status Report

Description The method received in the request-line is known by the origin server but not supported by the target resource.

Apache Tomcat/9.0.63

Kris Jacobs_jsdjl8

No reported issues on my upgrade report.

Instance Health on Troubleshooting & Support looks good.

Running Log Analyzer now.

Thanks Ben.

Kris Jacobs_jsdjl8

I think I have found the problem on our instance. I upgraded Jira Software from 8.x to 9.1.0, but Jira Service Management is still at 4.20

So I'll need to get JSM up to 5.10 and go from there.

Kris Jacobs_jsdjl8

Fixed.

I had to run the installer at the OS level for JSM 5.10.

This page is what got me in trouble: https://confluence.atlassian.com/adminjiraserver/upgrading-jira-installer-938846937.html

"If you're upgrading both Jira Core/Software and Jira Service Management, upgrade Jira Core/Software only. You'll later upgrade Jira Service Management directly in Jira, without a separate installer."

There was no facility to upgrade JSM "directly in Jira" after I upgraded Jira Software to 9.1.0

andrea price

Kris - thanks for your input. That worked for me. Oddly, I was still prompted to update Service Mgmt in JIRA Applications after I ran the executables and brought JIRA back up. At least I got that far this time - last time I couldn't open any administrative screens. Next step...the cloud migration.

Kris Jacobs_jsdjl8

You're welcome Andrea!

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira

jira-software

jira-software-server

atl-gruland