|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
The main idea, that nginx config was touched several months ago. And anything worked properly more than for a year.
I've updated nginx to the latest versiona available. I've checked that configuration is equal to the link you refer. (first one, second is not applicable as jenkins is not on the same host)
Here it is for you to be sure
server { listen *:80;server_name build.example.com build.other.tld; rewrite ^/(.*) https://build.example.com/$1; } server { listen *:443; server_name build.example.com build.other.tld; location / { proxy_pass http://10.0.0.19:8080/; proxy_set_header X-Real-IP $remote_addr; proxy_set_header Host $host:$proxy_port; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; proxy_redirect http:// https://; } client_max_body_size 400m; ssl on; ssl_certificate /root/chain/chained/build.example.com.crt; ssl_certificate_key /root/chain/keys/build.example.com.key; }And firstly I've asked about this bug on a Jenkins IRC chat, and `orrc` confirmed that he has the same behavior.