Error "ERR_SSL_PROTOCOL_ERROR" when trying to access Jira after configuring HTTPS
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
After configuring JIRA to work over HTTPS, the following error came up when the user tries to access the site:
1
2
ERR_SSL_PROTOCOL_ERROR (Chrome)
ssl_error_rx_record_too_long (Firefox)Diagnosis
Check catalina.out for the following INFO message at startup:
1
2
3
4
5
6
7
8
9
10
11
12
13
INFO [http-nio-8444-exec-8] org.apache.coyote.http11.Http11Processor.service Error parsing HTTP request header
Note: further occurrences of HTTP request parsing errors will be logged at DEBUG level.
java.lang.IllegalArgumentException: Invalid character found in method name [0x160x030x010x020x000x010x000x010xfc0x030x030x0c0x000xbf0xf00x820xcfv50xaa0xdah0x1c0xa5s,0xd4F0x1f0x950xaf0xff0xb10;0xcc0x9d0x900x830x8f!0xff0xfa]. HTTP method names must be tokens
at org.apache.coyote.http11.Http11InputBuffer.parseRequestLine(Http11InputBuffer.java:431)
at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:503)
at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65)
at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:831)
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1634)
at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.lang.Thread.run(Thread.java:748)Cause
This exception can occur when you try to execute HTTPS requests from a client or endpoint which isn’t HTTPS enabled. The client will encrypt request data when the server is expecting raw data.
Solution
Ensure the SSLEnabled="true" parameter is configured under the server.xml file:
Example:
1
2
3
4
5
6
7
8
<Connector port="8443" protocol="org.apache.coyote.http11.Http11NioProtocol"
maxHttpHeaderSize="8192" SSLEnabled="true"
maxThreads="150" minSpareThreads="25"
enableLookups="false" disableUploadTimeout="true"
acceptCount="100" scheme="https" secure="true"
sslEnabledProtocols="TLSv1.2,TLSv1.3"
clientAuth="false" useBodyEncodingForURI="true"
keyAlias="jira" keystoreFile="<Jira_HOME>/jira.jks" keystorePass="changeit" keystoreType="JKS"/>Double-check the Running Jira applications over SSL or HTTPS page to ensure all parameters are present.
Was this helpful?