mod_jk v proxying

[Maureen Barger]

Hi  - working on implementing the latest LTS update, we are encountering the reverse proxy error when going to Jenkins admin page. Is it possible to resolve this issue using mod_jk configuration we currently use or is the only option to move to a proxy server setup? I am not finding much in terms of solutions in my searches.
Thanks.

[Mark Eggers]

On Friday, December 19, 2014 8:55:43 AM UTC-8, MoBarger wrote:

Hi  - working on implementing the latest LTS update, we are encountering the reverse proxy error when going to Jenkins admin page. Is it possible to resolve this issue using mod_jk configuration we currently use or is the only option to move to a proxy server setup? I am not finding much in terms of solutions in my searches.
Thanks.

I don't know what issue you're having (we run leading edge, not LTS).

That being said, our set up is as follows:

1. Apache HTTPD on CentOS 6.6 (2.2.15-39)
2. mod_jk 1.2.40
3. Tomcat 7.0.57
4. JRE 1.7.0_72

We use a uriworkermap.properties file with:

/jenkins|/*=[worker-name]

Seems to work fine. We can reach the admin page with no problem, the REST 
API works as expected, and interaction with the Nexus server running on a 
different host (same architecture as above, /nexus|/*=[worker-name]) works 
as expected.

I've long been a fan of mod_jk since I'm not as fluent in the rewrite 
rules necessary to make proxy configurations work all of the time.

. . . just my two cents 

/mde/ 

[Maureen Barger]

Thanks Mark, We've been running Jenkins with pretty much the same setup you describe. We are currently at LTS 1.532.1. When we attempted the update to LTS1.580.2 with the same setup, we would get the error, "Jenkins says my reverse proxy is broken" when going to Manage Jenkins. It is described here: https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+says+my+reverse+proxy+setup+is+broken

Now using mod_jk is not necessarily as using a  proxy server, in many ways I like it better. So I am wondering if folks have updated to latest LTS using a setup with Apache and mod_jk and have avoided this issue.

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/d5b0ec41-ac47-4e3a-931b-43dbd8ab046e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.