HTTPS mixed content warning still showing even if base_url is set to https

[Rachel Smith]

Hi,

We encounter mixed content warning on any browser we use. Checked base_url and it was set to HTTPS.

The error is specific to one image only
images/icons/issue_subtask.gif

Your help will be much appreciated.

Thank you so much!

We are using
JIRA v5.2.11 running on nginx 1.6.2

[David Di Blasio]

Hi Rachel, 

Check your server.xml and ensure  "scheme", "proxyName" and "proxyPort" attributes are added, and match your environment. More on this can be found in the following article:

https://confluence.atlassian.com/display/JIRA/Integrating+JIRA+with+Apache#IntegratingJIRAwithApache-Step1:ConfigureTomcat

Cheers!

David Di Blasio | Atlassian Support

[Rachel Smith]

Hi David,

Thanks for your response. But after checking server.xml, all attributes are correct.

I wonder if it has something to do with our nginx configuration. Can help us figure out which one could be the cause of this?

Here is our /etc/nginx/conf.d/default.conf

proxy_cache_path /var/cache/nginx/jira levels=1:2 keys_zone=jira-cache:50m max_size=50m inactive=1440m;
server {
listen 8080;
server_name OURDOMAIN;
rewrite ^ https://$server_name:8443$request_uri? permanent;
}
server {
listen 8443 ssl;
server_name  OURDOMAIN;
ssl on;
ssl_certificate /etc/nginx/new_cert.pem;
ssl_certificate_key /etc/nginx/server_3year.key;
ssl_session_timeout 5m;
ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
# ssl_ciphers HIGH:!aNULL:!MD5;
# ssl_prefer_server_ciphers on;
ssl_session_cache shared:SSL:10m;
access_log /var/log/nginx/jira/jira.access.log main;
error_log /var/log/nginx/jira/jira.error.log error;
client_max_body_size 300M;

[David Di Blasio]

Hi Rachael, It looks like the location portion is missing from this configuration snippet. Do you have a location section that looks like what is described in the following article? https://confluence.atlassian.com/display/JIRAKB/Integrating+JIRA+with+Nginx

[Rachel Smith]

Hi David, Thank you very much for your help. But we also have location on our nginx config (default.conf) location / { proxy_set_header X-Forwarded-Host $host; proxy_set_header X-Forwarded-Server $host; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_pass http://OURDOMAIN:8100; set $do_not_cache 0; if ($request_uri ~* ^(/secure/admin|/plugins|/secure/projects|/projects|/admin)) { set $do_not_cache 1; } proxy_cache_bypass $do_not_cache; } Here is our server.xml <Connector port="8100" 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="OURDOMAIN" proxyPort="8443" secure="false" /> Did we miss something? Why only one image is causing mixed content warning?