Error after switching to SSL on Service Desk 8,0

Eric February 14, 2019

I have a new install of Jira Service Desk 8,0. When I switch to http redirect to https I receive the message in the stdout log:

JIRA-Bootstrap ERROR      [c.a.jira.startup.DefaultJiraLauncher] JIRA has failed to start because of the following errors: [(Event: Level = (EventLevel: error) , Key = (EventType: setup) , Desc = Tomcat is misconfigured , Exception = The server.xml file is missing parameters needed by Jira to handle requests that contain special characters.<br/>)]

I see this in the access.log

"GET /secure/johnson/data HTTP/1.1" 503 5 270 

 

The error page I see in the browser shows that the installed certificate is valid,

I tried updating the server.xml from this article:

https://confluence.atlassian.com/jirakb/changing-server-xml-to-handle-requests-with-special-characters-958453799.html

 

This is on Windows 2016 server with SQL Server 2014 and regular http works with no issues.

 

 

 

 

 

 

 

 

2 answers

1 accepted

0 votes
Answer accepted
Eric February 15, 2019

I fixed the issue.

I added this to the end of the second connector entry:

relaxedPathChars="[]|" relaxedQueryChars="[]|{}^\`&quot;&lt;&gt;" 

0 votes
Daniel Eads
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
February 15, 2019

Hi Eric,

Would you mind posting the connector portion of your server.xml file? This will help me see what's going on under the hood to suggest a fix.

I personally also prefer to terminate HTTPS at a reverse proxy and then use the standard http connector between the reverse proxy and Tomcat, but I understand you might have reasons for not using a reverse proxy or encrypting between a proxy and Tomcat (for instance if they are on separate servers).

If your connector is currently configured for HTTPS, you can blank out the keystorePass parameter if you've changed it from the default "changeit" before posting.

Thanks,
Daniel | Atlassian Support

Eric February 15, 2019

There are two, The first one is from line 33 and the second one is from line 109. This is the setup from the config,bat without updating the relaxedQueryChars from the article.

<Connector acceptCount="100" bindOnInit="false" connectionTimeout="20000" disableUploadTimeout="true" enableLookups="false" maxHttpHeaderSize="8192" maxThreads="150" minSpareThreads="25" port="80" protocol="HTTP/1.1" redirectPort="443" relaxedPathChars="[]|" relaxedQueryChars="[]|{}^\`&quot;&lt;&gt;" useBodyEncodingForURI="true"/>
<Connector SSLEnabled="true" acceptCount="100" clientAuth="false" connectionTimeout="20000" disableUploadTimeout="true" enableLookups="false" keyAlias="1" keystoreFile="C:\Program Files\Atlassian\JIRA\certs\wildcard.jks" keystorePass="xxxxxx" keystoreType="JKS" maxHttpHeaderSize="8192" maxSpareThreads="75" maxThreads="150" minSpareThreads="25" port="443" protocol="org.apache.coyote.http11.Http11NioProtocol" scheme="https" secure="true" sslProtocol="TLS" useBodyEncodingForURI="true"/>

 

I have a working 7.12 Service Desk installation on Server 2012, SQL Server 2012, and the server.xml files are identical with the exception of the following in the new installation (version 8).

relaxedPathChars="[]|" relaxedQueryChars="[]|{}^\`&quot;&lt;&gt;"


Like Jin Kim likes this
Jin Kim
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
July 31, 2019

Had the same issue, this solution has worked for me as well.  Thank you Eric

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events