Issue integrating HTTPS into jira

Im having some issues trying to make HTTPS work nicely with jira. I have enable HTTPS support using the instruction provided in jira.

However, im still getting this error and i cannot find the cause of issue:

2017-05-17 15:15:41,621 http-nio-8080-exec-14 WARN admin 915x1978x1 jhdkh2 172.16.192.253,127.0.0.1 /rest/webResources/1.0/resources [c.a.p.r.c.security.jersey.XsrfResourceFilter] Additional XSRF checks failed for request: https://jira-test.xxx.net:80/rest/webResources/1.0/resources , origin: https://jira-test.xxx.net , referrer: https://jira-test.xxx.net/secure/Dashboard.jspa , credentials in request: true , allowed via CORS: false
2017-05-17 15:15:41,777 http-nio-8080-exec-6 ERROR admin 915x1982x1 jhdkh2 172.16.192.253,127.0.0.1 /plugins/servlet/gadgets/dashboard-diagnostics [c.a.g.d.internal.diagnostics.DiagnosticsServlet] DIAGNOSTICS: FAILED
com.atlassian.gadgets.dashboard.internal.diagnostics.UrlPortMismatchException: Detected URL port, '80', does not match expected port, '443'
	at com.atlassian.gadgets.dashboard.internal.diagnostics.Diagnostics.checkExpectedPort(Diagnostics.java:71)
	at com.atlassian.gadgets.dashboard.internal.diagnostics.Diagnostics.check(Diagnostics.java:33)

I search for this issue in the comunity and added some lines as per Resolutions recomendation but still not working :( 

Below is part of my server.xml file:

Service name="Catalina">

        <Connector port="8080"

                   maxThreads="150"
                   minSpareThreads="25"
                   connectionTimeout="20000"

                   enableLookups="false"
                   maxHttpHeaderSize="8192"
                   protocol="HTTP/1.1"
                   useBodyEncodingForURI="true"
                   redirectPort="8443"
                   acceptCount="100"
                   disableUploadTimeout="true"

                   scheme="https"
                   proxyName="jira-test.xxx.net"
                   proxyport="443" />
      <Connector port="8443" protocol="org.apache.coyote.http11.Http11Protocol"
              maxHttpHeaderSize="8192" SSLEnabled="true"
              maxThreads="150" minSpareThreads="25"
              enableLookups="false" disableUploadTimeout="true"
              acceptCount="100" scheme="https" secure="false"
              clientAuth="false" sslProtocol="TLS" useBodyEncodingForURI="true"/>
        -->

Please help, thanks. 

1 comment

Josh Steckler Community Champion May 17, 2017

The apache proxy instructions miss the fact that you need to set your ServerName directive to the fully qualified domain name that you're using. This is commented out by default in ssl.conf for apache.

 

ServerName jira-test.xxx.net:443

Thanks, i added that line to the ssl.conf file but error is still the same

internal.diagnostics.DiagnosticsServlet] DIAGNOSTICS: FAILED
com.atlassian.gadgets.dashboard.internal.diagnostics.UrlPortMismatchException: Detected URL port, '80', does not match expected port, '443'
 at com.atlassian.gadgets.dashboard.internal.diagnostics.Diagnostics.checkExpectedPort(Diagnostics.java:71)
 at com.atlassian.gadgets.dashboard.internal.diagnostics.Diagnostics.check(Diagnostics.java:33)

Any other advise? 

And just as FYI the page loads over HTTPS but some objects are unable to be displayed likely due to this error. 

Josh Steckler Community Champion May 17, 2017

Are you sure you changed this in the right place? The right virtualhost?

 

The ProxyPass and ProxyPassReverse directives should only be on the port 443 virtualhost. The port 80 virtualhost should only be used to forward users to port 443. Take a look at my answer on this question: https://community.atlassian.com/t5/Questions/Jira-Apache-ajp-proxy-redirect-to-https/qaq-p/583660#M50131

Comment

Log in or Sign up to comment
How to earn badges on the Atlassian Community

How to earn badges on the Atlassian Community

Badges are a great way to show off community activity, whether you’re a newbie or a Champion.

Learn more
Community showcase
Published Thursday in Jira

5 ways you can make the most of Jira Software and Bitbucket Cloud

As part of the Bitbucket product team I'm always interested in better understanding what kind of impact the use of our tools have on the way you work. In a recent study we conducted of software devel...

76 views 0 5
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you