-
Bug
-
Resolution: Not A Defect
-
Minor
Hey,
I have recently updated Jenkins from version 2.73.3 to 2.121.1 and I am now encountering an error message about our reverse proxy configuration being broken. Regardless of the warning, everything is working fine so far. I didn't change anything besides swapping the jenkins.war and updating some plugins.
I have tried everything from this wiki page:
- Jenkins URL configured in the System Configuration matches the URL we're using to access Jenkins
- set X-Forwarded-Proto header but it didn't help
- running the cURL script lead to a 400 Bad Request
I also checked similiar JIRA-issues but unfortunately couldn't find anything applicable.
Any other idea? FYI we're running Jenkins in a Tomcat 8 Container behind a F5 load balancer.
Kind regards,
Robin