So, I've configured Bitbucket & Bamboo using almost the same method and it worked. I'm following this guide: https://confluence.atlassian.com/jirakb/configure-jira-server-to-run-behind-a-nginx-reverse-proxy-426115340.html
Jira is v8.4. Nginx is 1.10.3 (Debian 9).
What happens on my https://jira.domain.com
My server.xml (8082 for debug purposes):
<Connector port="8080" relaxedPathChars="[]|" relaxedQueryChars="[]|{}^\`"<>"
maxThreads="150" minSpareThreads="25" connectionTimeout="20000" enableLookups="false"
maxHttpHeaderSize="8192" protocol="HTTP/1.1" useBodyEncodingForURI="true" redirectPort="8443"
acceptCount="100" disableUploadTimeout="true" bindOnInit="false" secure="true" scheme="https"
proxyName="jira.domain.com" proxyPort="443"/>
<Connector port="8082" relaxedPathChars="[]|" relaxedQueryChars="[]|{}^\`"<>"
maxThreads="150" minSpareThreads="25" connectionTimeout="20000" enableLookups="false"
maxHttpHeaderSize="8192" protocol="HTTP/1.1" useBodyEncodingForURI="true" redirectPort="8443"
acceptCount="100" disableUploadTimeout="true"/>
My nginx.conf is stock and I added jira.conf in the sites-enabled folder of nginx:
server {
listen 443 ssl;
# listen [::]:443 ssl;
server_name jira.domain.com;
ssl_certificate /etc/letsencrypt/live/jira.domain.com/fullchain.pem; # managed by Certbot
ssl_certificate_key /etc/letsencrypt/live/jira.domain.com/privkey.pem; # managed by Certbot
include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot
# HSTS (ngx_http_headers_module is required) (63072000 seconds)
# add_header Strict-Transport-Security "max-age=63072000" always;
location / {
client_max_body_size 10M;
proxy_pass http://localhost:8080/;
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;
}
}
# redirect http to https for jira subdomain
server {
if ($host = jira.domain.com) {
return 301 https://$host$request_uri;
}
listen 80;
server_name jira.domain.com;
return 404;
}
I can access Jira through the debug HTTP connector.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.