Windows slave offline or unable to connect


  • Jenkins slave offline
  • Jenkins slave unable to connect


  • CloudBees Jenkins Enterprise (CloudBees Jenkins Platform)
  • Windows Agent (Slave)


Re-create agent by doing the following:

1) Remove $JENKINS_HOME/nodes/{slavename}/config.xml

2) Restart both the agent (slave process) and the Jenkins master (the instance running CloudBees Jenkins Enterprise)

Note: The 2.50 (and newer) versions of remoting (slave.jar) adds support for connecting through a proxy. If you have the http_proxy environment variable or the http.proxyHost system property defined for the slave process, it won’t be able to connect to the master. If needed, please remove these and restart the Windows slave, then attempt to re-connect. If you are running CloudBees Jenkins Enterprise 1.609.1.1 or newer, you should have 2.50 or newer…unless you upgraded from a previous release and the Windows slaves didn’t get updated.

Updating The Windows Slave

If necessary, use this procedure to update the Windows slave to the version bundled with your CloudBees Jenkins Enterprise release…

1) Retrieve the version from {Jenkins_Master_URL}/jnlpJars/slave.jar

2) Stop the slave process (service) on the Windows slave

3) Delete the existing slave.jar on each Windows slave and replace it with the newly retrieved version.

4) Start the slave process (service) on the Windows slave

Have more questions? Submit a request


Please sign in to leave a comment.