![]() |
|
|
|
|
Issue Type:
|
Bug
|
|
Affects Versions:
|
current |
|
Assignee:
|
Kohsuke Kawaguchi
|
|
Components:
|
slave-setup |
|
Created:
|
03/Feb/13 9:55 PM
|
|
Description:
|
Our Jenkins is running behind Nginx over SSL, then proxy-passed to Winstone. It has been working fine, but today I upgraded from I think 1.483 to 1.500 just to discover that the Win XP slave is not able to connect. The slave-agent.jnlp was somehow not working. When I run it from the CLI I discovered that it's trying to connect to http://, although the config is set to https://, then it gets 301 Moved Permanently from Nginx, and since it is unable to handle it, it just dies with a SEVERE error.
Feb 3, 2013 1:39:24 PM hudson.remoting.jnlp.Main$CuiListener <init>
INFO: Hudson agent is running in headless mode.
Feb 3, 2013 1:39:24 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Locating server among http://.../jenkins/ # SHOULD BE HTTPS!!!
Feb 3, 2013 1:39:24 PM hudson.remoting.jnlp.Main$CuiListener error
SEVERE: http://.../jenkins/tcpSlaveAgentListener/ is invalid: 30
1 Moved Permanently
java.lang.Exception: http://.../jenkins/tcpSlaveAgentListener/ i
s invalid: 301 Moved Permanently
at hudson.remoting.Engine.run(Engine.java:168)
So
1) Why does it use http instead of https when the settings are clear?
2) Why is it unable to handle 302?
Thanks a lot!
Cheers,
Ondra Kupka
|
|
Environment:
|
Windows XP
|
|
Project:
|
Jenkins
|
|
Labels:
|
slave
|
|
Priority:
|
Major
|
|
Reporter:
|
Ondrej Kupka
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[email protected].
For more options, visit
https://groups.google.com/groups/opt_out.