dedicated agents are not able to connect Bee Bot July 13, 2022 11:44 Updated The content of this article has moved to the new documentation site. Related articles Dedicated JNLP agents Troubleshooting guide How to access webSockets for Jenkins inbound agents? How to Connect to Remote SSH Agents? How to curl the CloudBees Jenkins websocket endpoint Launching Jenkins Inbound Agents with Java Comments 4 comments Sort by Date Votes John Mellor November 23, 2017 14:28 Ok, what is a "CJOC_URL"? Gobbledegook phrase meaning "Canadian Joint Operations Command"? If the slave.jar has a different md5, how do I interpret that? What API versions are compatible, and how do I determine that compatibility? I have a JNLP connection issue in K8S, and this document falls far short of what is required to debug this. -1 Denys Digtiar November 24, 2017 00:01 CJOC stands for CloudBees Jenkins Enterprise. For the purposes of this article, it should have just been JENKINS_URL. If the hash sum is different it means the versions are different between master and agent. The backward compatibility is maintained but the recommendation is to keep the slave.jar at the same version on both sides. Therefore if md5 is different, replace agent's slave.jar with the one downloaded from the master. 1 Byron Kim March 06, 2018 23:20 In the Load balancer or ha-proxy section, there should be a comment about Idle Timeouts if you're Jenkins node is running through a LB/proxy. This can cause JNLP connection timeout errors The default for ELB for instance is 60s and was causing some builds on slave nodes to fail on certain steps that took a long time to respond. 0 mark.kenneally Kenneally October 04, 2019 08:00 CLI authentication format has changed, it should be: java -jar jenkins-cli.jar -s http://<JENKINS_URL>/ -auth <username>:<APItoken> help 0 Please sign in to leave a comment.