Forums

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

Jira wont load after switching to SSL

tim and June 17, 2020

I added a self-signed cert to my jira server and was able to access it using port 443 but when it loads now I get a plethora of errors.2020-06-17_17-35-12.png

2 answers

0 votes
tim and June 20, 2020

this was an install of the latest jira server, it already has these lines

tim and June 20, 2020

im going to reinstall this software one more time then im over trying this, any modern self respecting software should be running with a self signed cert from the jump anyway

0 votes
Andy Heinzer
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
June 19, 2020

Hi,

Sorry to hear about these problems, but thanks for posting the screenshot here.  It helps us understand exactly what is happening.

You are going to need to make some changes to the $JIRAINSTALL/conf/server.xml file in order to make this work.  We detail these in the KB Jira server startup fails with Tomcat misconfigured error.  Basically you need to locate each <Connector> tag in that file and then add the two following parameters to each one:

relaxedPathChars="[]|" relaxedQueryChars="[]|{}^&#x5c;&#x60;&quot;&lt;&gt;"

Once this is done, you then need to save that file, and restart Jira.  That should correct this problem, but please note that if you have Jira configured to use more than one port such as 443 and 80, you'll have to repeat that step in each <Connector>

 

That screenshot also shows another unrelated problem Jira has, I can see that your Jira is aware of an unsupported collation on the database in use here.  That can pose other problems with Jira not working as expected.   After you have fixed the server.xml issue, I'd then recommend these steps in order to correct the collation problem.

  1. Select a database type/version from our Supported platforms - Atlassian Documentation
  2. Create a new blank database per Connecting Jira applications to a database - Atlassian Documentation, (paying close attention to the correct collation for that database type)
  3. Gather an XML backup of your Jira instance. Even if you can't start Jira, you can still find a recent one of these backups in the filesystem of the Jira server. By default this is saved in <jira-home>/export/ folder
  4. Stop Jira,
  5. Run the Jira Configuration tool to tell Jira to use the new blank database, save these changes, (if you can't run this, then you can just directly edit the <jira-home>/dbconfig.xml file to make these changes)
  6. Start Jira up again (when Jira starts with an empty database, it automatically launches the setup wizard)
  7. Copy the export XML zip file from <jira-home>/export/ into <jira-home>/import/
  8. Then you can import the backup using the 'Import your data' link in the setup wizard

By following these steps you can then import your previous data into a supported database with the correct database setup.

 

Let me know if you have any questions.

Andy

Suggest an answer

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

Atlassian Community Events