Setting up SSL NGINX. Any expected issues after implementation?

Tripline

Anyone setup https for Jira and ran into any issues? After reading about Jira Collaborative editing not working with Apache SSL, I was wondering if there was any unforeseen errors I can expect.

I'm running Jira Software on top on Windows 2016.

https://confluence.atlassian.com/confkb/confluence-collaborative-editing-does-not-work-with-ssl-and-apache-2-4-9-or-earlier-872132268.html

Mike Rathwell

Hi @Tripline 

Yes... it will work and take far less time than trying to figure out the ins/outs/wherefores of doing it even on a supported version of Apache. Here's the config I used for Confluence successfully:

server {
server_name .confluence.company.com;
listen 80;

location / {
return 301 https://$server_name$request_uri;
   }
}

server {
listen 443 ssl;
server_name .confluence.company.com;
ssl_certificate /etc/nginx/certs/confluence-chained.crt;
ssl_certificate_key /etc/nginx/certs/confluence.key;

ssl_session_timeout 5m;

ssl_protocols SSLv2 SSLv3 TLSv1 TLSv1.1 TLSv1.2;
ssl_ciphers HIGH:!aNULL:!MD5;
ssl_prefer_server_ciphers on;

location /{
client_max_body_size 0;
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://localhost:8090/;
}
location /synchrony {
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://localhost:8091/synchrony;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "Upgrade";
}
}

 Note that I used the vernacular ".confluence.company.com" with the leading dot. I have wildcard certs and this allows me to use the same NGINX config for both "https://confluence.company.com" and "https://test.confluence.company.com" for example.