Bruno Verachten added a comment - 2023-10-04 12:58 - edited Hi there, As a reminder, the term "slave" to refer to an agent has been deprecated since 2016. Please refer to https://www.jenkins.io/blog/2020/06/18/terminology-update/ for more details. We request you update your issue. The error message you're encountering, java.net.BindException: Address already in use (Bind failed) , typically indicates that the port you are trying to bind to is already in use by another process. In this case, it appears to be affecting your Jenkins agent. Here are some steps you can take to diagnose and resolve this issue: Identify the Port : Determine which port is causing the conflict. In your error message, you can see that the port in question is 10.82.165.81:16339 . This is the port that the Jenkins agent is trying to bind to. Check for Running Processes : On the machine where the Jenkins agent is running, check if there are any other processes or applications using the same port. You can use the netstat command (or ss on some systems) to list open network connections and the processes using them. For example, on Linux, you can run: netstat -tuln | grep 16339 This should show you if any other process is using port 16339 . You can then decide whether to stop that process or configure the Jenkins agent to use a different port. Configure Jenkins Agent Port : If the port conflict is due to another process, you can configure the Jenkins agent to use a different port. In your Jenkins controller, go to the Jenkins agent configuration and specify a different port in the "Fixed port" field. Restart Jenkins Agent : After making changes, restart the Jenkins agent to apply the new configuration. Firewall and Security Groups : If your Jenkins controller and agent are running on different machines, ensure that there are no firewall rules or security group restrictions blocking the port 16339 . Both machines should be able to communicate on this port. Check for Zombie Processes : Occasionally, a previous Jenkins agent process might not have terminated correctly and could still be holding onto the port. Check for any zombie processes and terminate them if necessary. Check for Other Services : Sometimes, other services or applications running on the same machine might be configured to use the same port. Ensure there are no conflicts with other software. Check Jenkins Configuration : Double-check the Jenkins agent configuration in your Jenkins controller to ensure that the correct port is specified and there are no typos or errors in the configuration. Java Version : While you mentioned that both the controller and agent are using the same Java version, verify that there are no issues related to Java version compatibility. Ensure that both are using a supported Java version for your Jenkins version. Jenkins JNLP Version : Ensure that you are using a compatible version of JNLP for your Jenkins setup. Sometimes, issues like this can be resolved by updating the JNLP version. If the issue persists after trying these steps, please provide more details about your Jenkins setup, including any recent changes or configurations, which might help in diagnosing the problem further.