java.lang.Exception: http://.../jenkins/tcpSlaveAgentListener/ i s invalid: 301 Moved Permanently

Jenkins JIRA | Ondrej Kupka | 4 years ago
  1. 0

    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): {code} $ 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) {code} 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: {code:xml} <argument>-url</argument><argument>http://ci.mydomain.com/jenkins/</argument> {code} The problem is that the slave is being told to connect via HTTP, but (thanks to our proxy) Jenkins 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 from Apache to Jenkins *is* HTTP, however the client must use HTTPS as I configured our root URL.

    Jenkins JIRA | 4 years ago | John Cook
    java.lang.Exception: http://ci.mydomain.com/jenkins/tcpSlaveAgentListener/ is invalid: 301 Moved Permanently
  2. Speed up your debug routine!

    Automated exception search integrated into your IDE

  3. 0

    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): {code} $ 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) {code} 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: {code:xml} <argument>-url</argument><argument>http://ci.mydomain.com/jenkins/</argument> {code} The problem is that the slave is being told to connect via HTTP, but (thanks to our proxy) Jenkins 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 from Apache to Jenkins *is* HTTP, however the client must use HTTPS as I configured our root URL.

    Jenkins JIRA | 4 years ago | John Cook
    java.lang.Exception: http://ci.mydomain.com/jenkins/tcpSlaveAgentListener/ is invalid: 301 Moved Permanently
  4. 0

    Showing exception while connecting slave to master using headless jnlp

    Stack Overflow | 4 years ago | varghese
    java.lang.Exception: The server rejected the connection:

    4 unregistered visitors
    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. java.lang.Exception

      http://.../jenkins/tcpSlaveAgentListener/ i s invalid: 301 Moved Permanently

      at hudson.remoting.Engine.run()
    2. Hudson :: Remoting Layer
      Engine.run
      1. hudson.remoting.Engine.run(Engine.java:168)
      1 frame