Issue Type: Bug Bug
Affects Versions: current
Assignee: Unassigned
Attachments: http-dump.txt
Components: master-slave
Created: 28/Jan/13 7:14 PM
Description:

Once I upgraded to Jenkins 1.5, my slave agent ("mac-mini") could no longer connect. Here's an example session (I changed the hostname and credentials to protect the guilty):
$ java -jar ./slave.jar -jnlpCredentials myuser:mypassword -jnlpUrl https://ci.mydomain.com/jenkins/computer/mac-mini/slave-agent.jnlp -noCertificateCheck
Skipping HTTPS certificate checks altoghether. Note that this is not secure at all.
Jan 28, 2013 1:45:43 PM hudson.remoting.jnlp.Main$CuiListener <init>
INFO: Hudson agent is running in headless mode.
Jan 28, 2013 1:45:43 PM hudson.remoting.jnlp.Main$CuiListener status
INFO: Locating server among http://ci.mydomain.com/jenkins/, http://127.0.0.1:8080/jenkins/
Jan 28, 2013 1:45:43 PM hudson.remoting.jnlp.Main$CuiListener error
SEVERE: http://ci.mydomain.com/jenkins/tcpSlaveAgentListener/ is invalid: 301 Moved Permanently
java.lang.Exception: http://ci.mydomain.com/jenkins/tcpSlaveAgentListener/ is invalid: 301 Moved Permanently
at hudson.remoting.Engine.run(Engine.java:168)

I then used Charles Proxy to capture the HTTP traffic to see what was going on. I've attached a file of that capture, but the relevant problem is here:
<argument>-url</argument><argument>http://ci.mydomain.com/jenkins/</argument>

The problem is that the slave is being told to connect via HTTP, but (thanks to our proxy) it is only available via HTTPS. I checked my configuration and it is correct. I believe the issue is caused by this change on January 15th: https://github.com/jenkinsci/jenkins/commit/460e508155187918e8c0f4fd0bb66a99cfe78527#L0R1877 . The protocol of the request as far as Jenkins knows is HTTP. However the client needs to use the HTTPS protocol I configured for our root URL.

Environment: Jenkins on port 8080, Apache proxy for SSL connections.
Project: Jenkins
Labels: slave proxy url
Priority: Blocker Blocker
Reporter: John Cook
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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Reply via email to