Bug 836203
Summary: | jenkins "It appears that your reverse proxy set up is broken." | ||
---|---|---|---|
Product: | OKD | Reporter: | Aleksandar Kostadinov <akostadi> |
Component: | Containers | Assignee: | Dan Mace <dmace> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | libra bugs <libra-bugs> |
Severity: | low | Docs Contact: | |
Priority: | medium | ||
Version: | 2.x | CC: | jhou, kasturisurya, lmeyer, mpatel, pmorie, xtian |
Target Milestone: | --- | Keywords: | Triaged |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-11-06 18:48:49 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1192753 |
Description
Aleksandar Kostadinov
2012-06-28 10:56:58 UTC
Created a new Jenkins-enabled jbossas-7 app in dev (ami-9bcb67f2 - devenv_1870) with the following command: rhc-create-app -a jbossapp -t jbossas-7 --enable-jenkins -p none And had no issues with the resulting Jenkins instance. Please provide precise steps to reproduce in a dev environment. Disregard comment 1, I see the error now in the "Manage Jenkins" page. I am even facing this error. I created a DIY application running Python 2.7, Django using uWsgi 1.2.4 So do a Jenkins Server as another app. Now, whenever, I open jenkins/manage, I find the following error. "It appears that your reverse proxy set up is broken" Experiencing this on my public instance. I created the Jenkins instance independently rather than as part of another app. Looking at the network traffic in Chrome, what looks to be happening is that from https://jenkins-sosiouxme.rhcloud.com/manage (note, httpS) the test query it is performing is http://jenkins-sosiouxme.rhcloud.com/administrativeMonitor/hudson.diagnosis.ReverseProxySetupMonitor/test-for-reverse-proxy-setup ... so, possibly the instance is confused about the scheme for self-reference. This might be specific to Jenkins. I'll spin up a dev instance and see if the same thing happens. The problem was as Luke commented - the redirect from https url is to an http one. Fix was to add a rule to httpd vhost configuration rewriting http urls to https. Pull request: https://github.com/openshift/crankcase/pull/515 (In reply to comment #5) > The problem was as Luke commented - the redirect from https url is to an > http one. Fix was to add a rule to httpd vhost configuration rewriting http > urls to https. > > Pull request: https://github.com/openshift/crankcase/pull/515 Above pull request is merged, move it to ON_QA to verify. Verified on devenv_2250 Steps: 1. Create a jenkins server app 2. Open jenkins webconsole -> Jekins -> Manage Jenkins Result: Error message is remove now. |