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

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

1 answer

1 votes

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

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;

 

 

 

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

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?

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,138 views 13 19
Join discussion

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
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot