[JIRA] [core] (JENKINS-32024) Wrongly claims reverse proxy broken

[aristedes@java.net (JIRA)]

aristedes created an issue

Jenkins / JENKINS-32024 Wrongly claims reverse proxy broken Issue Type: Bug Assignee: Unassigned Components: core Created: 11/Dec/15 5:35 AM Priority: Minor Reporter: aristedes Our Jenkins instance sits behind Apache httpd 2.4. There is no functional problem, but a recent update (sometime at or before 1.639) shows the message: It appears that your reverse proxy set up is broken Running the recommended script give me this result: http://build.acme.com/manage vs. https://build.acme.com/manage Clearly Jenkins is confused about the missing SSL, however apache is taking care of the SSL within the virtualhost before the ProxyPass kicks in. ProxyPass / http://localhost:8180/ nocanon ProxyPassReverse / http://localhost:8180/ ProxyRequests Off AllowEncodedSlashes NoDecode This looks like an error in Jenkins. Add Comment

This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)

[dbeck@cloudbees.com (JIRA)]

Daniel Beck resolved as Not A Defect

This behavior is documented on the wiki page linked from the error message: https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+says+my+reverse+proxy+setup+is+broken

Jenkins / JENKINS-32024 Wrongly claims reverse proxy broken

Change By: Daniel Beck Status: Open Resolved Resolution: Not A Defect

Add Comment

[aristedes@java.net (JIRA)]

aristedes reopened an issue

Sorry, but I've read that page several times and cannot find any reference to the fact that Jenkins cannot be run behind a proxy that does SSL. There is in fact no actual problem with the operation of Jenkins, but the error message in this case is extraneous with no obvious way to get rid of it.

Jenkins / JENKINS-32024 Wrongly claims reverse proxy broken

Change By: aristedes Resolution: Not A Defect Status: Resolved Reopened

Add Comment

[dbeck@cloudbees.com (JIRA)]

Daniel Beck commented on JENKINS-32024

Re: Wrongly claims reverse proxy broken The giant yellow box on top says: Make sure the Jenkins URL configured in the System Configuration matches the URL you're using to access Jenkins. It looks like you specified an HTTP URL in the global config, but access Jenkins via HTTPS.

Add Comment

[aristedes@java.net (JIRA)]

aristedes commented on JENKINS-32024

Re: Wrongly claims reverse proxy broken

If you mean the global setting with the label "Jenkins URL" under the heading "Jenkins Location" then no, I already checked that and it starts with "https".

Add Comment

[dbeck@cloudbees.com (JIRA)]

Daniel Beck commented on JENKINS-32024

Re: Wrongly claims reverse proxy broken

Next possibly relevant quote from the linked web page: Also, make sure to set the X-Forwarded-Proto header if your reverse proxy is accessed via HTTPS, but Jenkins itself is not.

Add Comment

[aristedes@java.net (JIRA)]

aristedes resolved as Not A Defect

My bad. Sorry for wasting your time. I read that page 5 times without seeing that line.

Jenkins / JENKINS-32024

Wrongly claims reverse proxy broken

Change By: aristedes Status: Reopened Resolved Resolution: Not A Defect

Add Comment

[rusty.carruth@smartm.com (JIRA)]

Rusty Carruth commented on JENKINS-32024

Re: Wrongly claims reverse proxy broken In my case, I'm on the actual host running Jenkins, and "foolishly" used 'localhost' in the URL!  So I think this is the "Jenkins URL" problem.  Not worth my fixing, IMHO, since this is in a virtual environment for my testing anyway, and its working fine.

Add Comment

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)