Skip to content

Commit ff5141a

Browse files
authored
Update troubleshooting-runners.md
Adding instructions on how to fix SSL Handshake error on the Runner startup.
1 parent 6146185 commit ff5141a

File tree

1 file changed

+44
-0
lines changed

1 file changed

+44
-0
lines changed

docs/administration/runner/runner-troubleshooting/troubleshooting-runners.md

Lines changed: 44 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -3,3 +3,47 @@
33
## Runner Logs
44

55
Runner Logs are located in the `./runner/logs` folder under the folder where the jar was executed from. The `runner.log` file contains operational and important messages about the runner. `operations.log` tracks an operation starts and if it succeeds or fails. [Read more about logging and setting up custom logging](/administration/runner/runner-management/runner-logging.md).
6+
7+
## SSL Handshake error on the Runner startup
8+
9+
### **Error message**
10+
```
11+
08-06-2025 14:23:47.445 [main] ERROR io.micronaut.retry.intercept.RecoveryInterceptor - Type [com.rundeck.sidecar.agent.server.RESClient$Intercepted] executed with error: javax.net.ssl.SSLHandshakeException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target reactor.core.Exceptions$ReactiveException: javax.net.ssl.SSLHandshakeException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
12+
```
13+
14+
### Why does this happen?
15+
16+
- The RBA-SH cluster is using a certificate that is **not trusted** by the default Java truststore (e.g., self-signed, or signed by a private/internal CA). In other words, the certificate chain can’t be validated using the Java truststore.
17+
18+
- The Runner (Java process) doesn’t have the CA certificate in its truststore.
19+
20+
- This is super common with **internal CAs** or **self-signed certs**—admins often add these to the OS trust store, but forget about Java’s.
21+
22+
23+
### How to fix it
24+
25+
1. Download the certificate chain from your Rundeck cluster
26+
27+
2. Transfer this file to your Runner VM
28+
29+
3. Import the CA cert into the Java truststore
30+
31+
32+
The default truststore is usually at:
33+
`$JAVA_HOME/lib/security/cacerts`
34+
The default password is `changeit`.
35+
36+
**Please confirm that** `$JAVA_HOME` **is correctly configured in your VM!**
37+
38+
Example command:
39+
40+
```
41+
keytool -import -alias rundeck-ca -file /path/to/ca.crt -keystore $JAVA_HOME/lib/security/cacerts
42+
```
43+
44+
- It will prompt for the password (`changeit` by default).
45+
46+
- Say “yes” to trust the certificate.
47+
48+
49+
4. Restart the Runner service.

0 commit comments

Comments
 (0)