JSD portal spinning

[Deleted user]

Hi,

we have upgraded jira software to 8.10.1  and jira  service desk 4.10.1 from 8.4.2 and 4.4.2 accordingly on our test environment. We encountered no problem but running JSD portal which wants to start a http session(picture at1). We would expect a https over the ngix proxy. There is no portal response, the cursor is spinning (picture at2). Chrome console error:

Mixed Content: The page at 'https://jira-test3.marand.si/plugins/servlet/project-config/MAIN/notifications' was loaded over HTTPS, but requested an insecure frame 'http://jiratest3.marand.si:8080/servicedesk/customer/portal/301'. This request has been blocked; the content must be served over HTTPS.

We have also tried to upgrade to 8.11.1&4.11.1 with the same result. There was no problem in version 4.10.1. What is changed?

BR Andrej

[Andy Heinzer · Accepted solution]

Hi Andrej,

I see that you have recently upgrade Jira and Jira Service Desk, but since that time you seem to be getting a mixed content error message where pages are not loading correctly.  This mixed content here will happen for a couple of different reasons:

1. The Base URL in Jira is set to use the HTTP value, but the page you are directly requesting is the HTTPS one.  Check the base url setting to confirm.
2. The other common cause here is that the $JIRAINSTALL/conf/server.xml could be missing some parameters in the connector tag.  You mentioned using nginx to proxy for Jira, and we see that there is an http connector on port 8080.  Find that connect in the server.xml file on port 8080 and then check to make sure this tag also has the correct proxyName, proxyPort, and scheme parameters.

I would expect that it would look something like this:

<Connector acceptCount="100" bindOnInit="false" connectionTimeout="20000" disableUploadTimeout="true" enableLookups="false" maxHttpHeaderSize="8192" maxThreads="150" minSpareThreads="25" port="8080" protocol="HTTP/1.1" relaxedPathChars="[]|" relaxedQueryChars="[]|{}^\`&quot;&lt;&gt;" useBodyEncodingForURI="true"
proxyName="jira-test3.marand.si" 
proxyPort="443"
scheme="https"/>

Without these last 3 parameters, Jira does not correctly understand that traffic to it is being proxied through another application.  Try making sure these values exist, save that file, and then restart Jira for any changes to take effect.

Let me know if this helps.

Andy

[Deleted user]

Hi Andy,

thank for your kind suggestion, but it does not solve the problem. All required parameters are set. In fact we use the same server.xml  as on version 4.4.2. which is working fine

The only thing I do not understand how is jira software resolving https correctly, but not JSD.  In the meantime I have noticed that also attachment are not served over https

Talk soon

Andrej

[Andy Heinzer]

I found one other case that appeared to have the same error, but it was not this version.  In that case the admin changed the connector port from 8080 to 8085 in both Jira's server.xml and in their proxy configuration as a means to resolve this.

Do you still have the 4.4.2 version up and running?  Are the hostnames different?  Perhaps if we can better understand the details of the previous configuration (both Jira and nginx) perhaps we can better understand the behavior here.

[Deleted user]

Thanks Andy. We had a typo error as there were two Connector on port 8080 defined in server.xml. Problem solved.