Trying to connect PC as Jenkins slave to master using Java Web Start. Fails throwing the following error as can be seen in the attachment.

      Tried the command line approach and got the same result.

      Jenkins and the PC are behind the same proxy.

      Used a different PC and everything connected fine.

          [JENKINS-42263] Jenkins slave tcpSlaveAgentListener 404 Error

          Robb R added a comment -

          Same here. Upgraded from 2.7.4 to 2.32.2 and the Windows slave, using TCP JNLP agent on a fixed port failed to connect on manually startup. Agent seems to fail on

          SEVERE: http://10.0.2.17:8080/tcpSlaveAgentListener/ is invalid: 404 null

          When I switch to random port and restarted the agent manually, it worked.

          To cause it to fail again I switched to fixed port. Port is not blocked and not not being used by another app.Changing the fixed port number does not help. Jenkins master is running on Tomcat.

          When the below is executed fixed port:
          curl http://10.0.2.17:8080/tcpSlaveAgentListener
          when server returns a 404.
          When the same curl is executed with a variable port it succeeds.

          I am required to use a fixed port and any recommendations would be apprciated.

          Thanks

          Robb R added a comment - Same here. Upgraded from 2.7.4 to 2.32.2 and the Windows slave, using TCP JNLP agent on a fixed port failed to connect on manually startup. Agent seems to fail on SEVERE: http://10.0.2.17:8080/tcpSlaveAgentListener/ is invalid: 404 null When I switch to random port and restarted the agent manually, it worked. To cause it to fail again I switched to fixed port. Port is not blocked and not not being used by another app.Changing the fixed port number does not help. Jenkins master is running on Tomcat. When the below is executed fixed port: curl http://10.0.2.17:8080/tcpSlaveAgentListener when server returns a 404. When the same curl is executed with a variable port it succeeds. I am required to use a fixed port and any recommendations would be apprciated. Thanks

          Lucas Brendel added a comment -

          So i found that someone had sneakily set the HTTP_PROXY env var on the system such that Jenkins could be accessed through Chrome/IE but then anything on the PC was using that proxy to leave the proxy and not be able to find the server which was behind the proxy. So i removed that and all is well now.

          Lucas Brendel added a comment - So i found that someone had sneakily set the HTTP_PROXY env var on the system such that Jenkins could be accessed through Chrome/IE but then anything on the PC was using that proxy to leave the proxy and not be able to find the server which was behind the proxy. So i removed that and all is well now.

          Lucas Brendel added a comment -

          HTTP_PROXY on system was not allowing java to access server since it was leaving the proxy.

          Lucas Brendel added a comment - HTTP_PROXY on system was not allowing java to access server since it was leaving the proxy.

          After an hour of trying to resolve this issue, removing HTTP_PROXY on the slave and rebooting the system it fixed the issue on the machine.

          Shashank Mankotia added a comment - After an hour of trying to resolve this issue, removing HTTP_PROXY on the slave and rebooting the system it fixed the issue on the machine.

            Unassigned Unassigned
            lbrendel Lucas Brendel
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: