On Tue, Mar 25, 2014 at 03:46:41PM -0700, Dennis Jacobfeuerborn wrote:
> Never mind. It looks like this is actually a bug in Jenkins:
>
> https://issues.jenkins-ci.org/browse/JENKINS-21989
That's not a bug. If I set up Apache properly[1], I get a 200 Ok from
the curl test.
[1]
https://issues.j
Never mind. It looks like this is actually a bug in Jenkins:
https://issues.jenkins-ci.org/browse/JENKINS-21989
Regards,
Dennis
On Thursday, March 20, 2014 5:05:47 PM UTC+1, Dennis Jacobfeuerborn wrote:
>
> Hi,
> I just installed a fresh Jenkins behind Apache httpd and while Jenkins is
> avai
Unfortunately none of this changes anything. I also tried the diagnostic
curl command from the help page:
[dennis@nexusm ~]$ curl -iL
http://jenkins.local/jenkins/administrativeMonitor/hudson.diagnosis.ReverseProxySetupMonitor/test
HTTP/1.1 302 Found
Date: Tue, 25 Mar 2014 22:28:12 GMT
Location
Can you try replacing 127.0.0.1 with actual ip of the box or change it
to localhost. I remember a problem sometimes back where definition of
localhost was different for java and c code. Don't remember the exact
details, but changing it localhost did make it work.
On 03/20/2014 09:05 AM, Dennis
Hi,
On 20/03/2014 16:05, Dennis Jacobfeuerborn wrote:
Hi,
I just installed a fresh Jenkins behind Apache httpd and while Jenkins
is available it tells me "It appears that your reverse proxy set up is
broken." but I don't know why.
I came across the same problem earlier today. My setup had been
On 20.03.2014, at 17:05, Dennis Jacobfeuerborn
wrote:
> I just installed a fresh Jenkins behind Apache httpd and while Jenkins is
> available it tells me "It appears that your reverse proxy set up is broken."
> but I don't know why.
Does the error message show up after you access 'Manage Jen
On Thu, Mar 20, 2014 at 09:05:47AM -0700, Dennis Jacobfeuerborn wrote:
> I just installed a fresh Jenkins behind Apache httpd and while Jenkins is
> available it tells me "It appears that your reverse proxy set up is
> broken." but I don't know why.
https://wiki.jenkins-ci.org/display/JENKINS/Je
On Thu, Mar 20, 2014 at 11:28 AM, wrote:
> If you are on Linux, It's much easier to use iptables instead of standing up
> httpd just to proxy.
>
>
>
> iptables -t nat -I PREROUTING --src 0.0.0.0/0 --dst 0.0.0.0/0 -p tcp --dport
> 80 -j REDIRECT --to-ports 8080
>
But both of those approaches forc
If you are on Linux, It’s much easier to use iptables instead of standing up
httpd just to proxy.
iptables -t nat -I PREROUTING --src 0.0.0.0/0 --dst 0.0.0.0/0 -p tcp --dport 80
-j REDIRECT --to-ports 8080
From: jenkinsci-users@googlegroups.com
[mailto:jenkinsci-users@googlegroups.com] On Beha
