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. )] 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.

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; } } }

Error after switching to SSL on Service Desk 8,0

Eric_503qgc

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.

Accepted answers

Eric_503qgc

I fixed the issue.

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

relaxedPathChars="[]|" relaxedQueryChars="[]|{}^\`"<>"

All comments

Daniel Eads

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_503qgc

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="[]|{}^\`"<>"

Eric_503qgc

I fixed the issue.

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

relaxedPathChars="[]|" relaxedQueryChars="[]|{}^\`"<>"

Jin Kim_3246zi

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

Welcome!

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

Quick Links

Find more posts tagged with

server

jira-service-desk

jira-service-desk-server