Forums

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

Upgraded from 7.11.2 to 8.22.6 and now HTTPS not working due to server.xml.

amazingcharts-admin January 14, 2024

After upgrading form Jira 7.11.2 to 8.22.6, we're getting this error:  The server.xml file is missing parameters needed by Jira to handle requests that contain special characters.

After trying the solution in https://confluence.atlassian.com/jirakb/jira-server-startup-fails-with-tomcat-misconfigured-error-958453799.html, we are still getting this error.

If we use HTTP it works.  HTTPS, not so much.

 

1 answer

0 votes
Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
January 14, 2024

Welcome to the Atlassian Community!

An upgrade of Jira will usually overwrite your old settings files with a standard default install, and that usually includes the server.xml file.  It will have warned you of what files it is going to change, but there's no way to write simple code for merging.

First, have a look at the old version of the server.xml file.  Hopefully, you backed up before upgrade.  Given your versions, a "diff" will probably only highlight a few lines as changed, and those can guide you as to what you need to re-add to it.

Second (or if you have no backup), run through https://confluence.atlassian.com/adminjiraserver0817/running-jira-applications-over-ssl-or-https-1071816718.html for configuring Tomcat for SSL

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
SERVER
VERSION
8.22.6
TAGS
AUG Leaders

Atlassian Community Events