Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-16613

Windows slave fails to start via JNLP (wrong URL scheme + fails to redirect)

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major Major
    • slave-setup-plugin
    • Windows XP

      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.486 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

            kohsuke Kohsuke Kawaguchi
            tchap Ondrej Kupka
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: