Forums

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

Caddy Reverse Proxy In Front of Jira - Mismatched URL Scheme

fudnet
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!
August 15, 2023

Greetings- I've been running Jira behind a Caddy reverse proxy for quite some time. Today, I upgraded to the latest Jira 9.10.1 and I'm now seeing errors related to a "Mismatched URL Scheme". I followed the instructions available on the document site, commenting out the default connector in /opt/atlassian/jira/conf/server.xml and uncommenting the proxy version, with my desired parameters. That connector statement looks like this:

<Connector port="8080" relaxedPathChars="[]|" relaxedQueryChars="[]|{}^&#x5c;&#x60;&quot;&lt;&gt;"
maxThreads="150" minSpareThreads="25" connectionTimeout="20000" enableLookups="false"
maxHttpHeaderSize="8192" protocol="HTTP/1.1" useBodyEncodingForURI="true" redirectPort="8443"
acceptCount="100" disableUploadTimeout="true" bindOnInit="false" secure="true" scheme="https"
proxyName="jira.domain.net" proxyPort="443"/>

I then restarted Jira, and the same error in the web UI persists regarding the mismatched URL scheme. I'm not certain where else to make the required change(s), nor am I finding any additional workable solutions on the Atlassian Community site, or elsewhere on the Internet.

Can you please provide guidance on how to resolve this issue?  

1 answer

0 votes
Michael Kornatzki
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.
October 30, 2023

Do you have a second connector?

I try to upgrade from 9.1.1 to 9.11.2 and see now in the dashboards

 

Mixed Content: The page at '<URL>' was loaded over HTTPS, but requested an insecure stylesheet '<URL>'. This request has been blocked; the content must be served over HTTPS.


If i remove the maintenance-Port (18080) then the dashboard works as expected.

 

<Connector port="18080" relaxedPathChars="[]|" relaxedQueryChars="[]|{}^&#x5c;&#x60;&quot;&lt;&gt;"
           maxThreads="150" minSpareThreads="25" connectionTimeout="20000" enableLookups="false"
           maxHttpHeaderSize="8192" protocol="HTTP/1.1" useBodyEncodingForURI="true" redirectPort="8443"
           acceptCount="100" disableUploadTimeout="true" bindOnInit="false"/>
        <Connector port="8080" relaxedPathChars="[]|" relaxedQueryChars="[]|{}^&#x5c;&#x60;&quot;&lt;&gt;"
                   maxThreads="150" minSpareThreads="25" connectionTimeout="20000" enableLookups="false"
                   maxHttpHeaderSize="8192" protocol="HTTP/1.1" useBodyEncodingForURI="true" redirectPort="8443"
                   acceptCount="100" disableUploadTimeout="true" bindOnInit="false" secure="true" scheme="https"
                   proxyName="svr-jirau" proxyPort="443"/>

Suggest an answer

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

Atlassian Community Events