Jenkins Agent can't Connect to server after Update to Jenkins 2.492.1

Agent and Server both on Windows

Error from Agent:
INFORMATION: https://deras180v90.de-ras.de.abatos.com:8443/login is not ready
javax.net.ssl.SSLHandshakeException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

Server is Reachable via Web, and I can Ping the Server, only one Agent is running all other Agent have the same issue
–>Could not locate server …

After going back to 2.479.3 all Agents connected again!
But I see some error in the agent.log:

Inbound agent connected from …
Remoting version: 3261.v9c670a_4748a_9
Launcher: JNLPLauncher
Communication Protocol: WebSocket
This is a Windows agent
ERROR: Unexpected error in launching an agent. This is probably a bug in Jenkins
Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to WIN10_CLX1_RAS_DE0W3X836
at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1923)…

1 Like

We have the same problem. We use a self-created certificate for https and Entra Id as Authentication Provider.

The only workaround for the unavailable node is to restart the Jenkins agent (Windows service).

My Investigations shows that the ports are changed to above 63000, but that is not all. I tried to set a fixed Port Number but it don’t helps.