Yep, that's covered, but still not making progress
El viernes, 13 de marzo de 2015, 11:38:44 (UTC+1), Daniel Beck escribió:
>
>
> On 13.03.2015, at 10:34, Marcos Rey >
> wrote:
>
> > The only difference is that apache also servers in port 80 while in the
> new installation only serves on 443 (h
On 13.03.2015, at 10:34, Marcos Rey wrote:
> The only difference is that apache also servers in port 80 while in the new
> installation only serves on 443 (https).
Make sure the Jenkins URL in the global config is configured to point to HTTPS
(and is identical to how you access Jenkins with y
Yeah, that's my thought too. What buggers me is that my prod deployment
passes the curl test and (in theory) I have the same configuration. The
only difference is that apache also servers in port 80 while in the new
installation only serves on 443 (https). Anyway, for the meanwhile all is
wor
I get the 404, but I don't get any errors on the management pages.
I don't think that referring to mod_jk as a proxy is strictly correct. See
the following for a detailed explanation.
http://tomcat.apache.org/connectors-doc/generic_howto/proxy.html
As an aside - mod_proxy_ajp is basically mod_j
Forgot to append the output:
HTTP/1.1 302 Found
Date: Thu, 12 Mar 2015 08:57:51 GMT
Server: Apache/2.2.15 (CentOS)
Cache-Control: private
Expires: Thu, 01 Jan 1970 01:00:00 CET
Location:
https://hostname/jenkins/administrativeMonitor/hudson.diagnosis.ReverseProxySetupMonitor/testForReverseProxyS
You are totally right, my bad. If I try the curl test, I get a 404 (as
expected).
El jueves, 12 de marzo de 2015, 9:47:08 (UTC+1), Daniel Beck escribió:
>
> That's why the curl command specifies a referer, something you don't have
> if you just open that URL.
>
> On 12.03.2015, at 09:16, Marco
That's why the curl command specifies a referer, something you don't have if
you just open that URL.
On 12.03.2015, at 09:16, Marcos Rey wrote:
> If it helps, if i manually try the url: https://hostname/jenkins/manage
> https://hostname/jenkins/administrativeMonitor/hudson.diagnosis.ReversePro
If it helps, if i manually try the url: https://hostname/jenkins/manage
https://hostname/jenkins/administrativeMonitor/hudson.diagnosis.ReverseProxySetupMonitor/test,
tomcat returns this:
HTTP 404 - https://hostname/jenkins/manage vs. NO-REFERER
El jueves, 12 de marzo de 2015, 9:14:49 (UTC+1),
Thanks Rui, i would consider mod_ajp. The weird thing is that i have a
similar production deployment that does not have this issue.
Mark, thanks for sharing your config, mine is quite similar, but I still
get the proxy reverse broken error. The weird thing is that everything
seems to be working
I've not seen this.
For my Jenkins URL:
http://[hostname]/jenkins/
In my uriworker.properties file:
/jenkins|/*=[workername]
Then in the Apache HTTPD host that manages Jenkins:
JkMountFile conf.d/uriworkermap.properties
There's a good base workers.properties configuration example in conf
su
I've managed to solve that using mod_proxy_ajp.
On Wed, Mar 11, 2015 at 7:37 AM, Marcos Rey wrote:
> Hello!
>
> I've been reading the messages around the list and I see that more people
> see this message on 'Manage Jenkins' when running apache+mod_jk with
> Jenkins. Any input would be greatly a
Hello!
I've been reading the messages around the list and I see that more people
see this message on 'Manage Jenkins' when running apache+mod_jk with
Jenkins. Any input would be greatly appreciated.
Regards,
--
You received this message because you are subscribed to the Google Groups
"Jenk
12 matches
Mail list logo
