Warning Unhealthy 4m44s (x6684 over 114m) kubelet Readiness probe failed: Get http://10.200.36.81:8080/: dial tcp 10.200.36.81:8080: connect: connection refused

0
when app is deployed in Prod environmeny it gives error as Warning Unhealthy 4m44s (x6684 over 114m) kubelet Readiness probe failed: Get "http://10.200.36.81:8080/": dial tcp 10.200.36.81:8080: connect: connection refusedwe checked pods its working, ingress is fine, 2026-07-02 13:49:04.308 ERROR - ConnectionBus: Opening JDBC connection to jdbc:sqlserver://10.200.18.17:1433 failed with SQLState: 08S01 Error code: 0 Message: ""encrypt" property is set to "true" and "trustServerCertificate" property is set to "false" but the driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption: Error: (certificate_unknown) PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target. ClientConnectionId:72d5ee20-c236-4f0d-93e9-e2dace921bb5", retrying...(1/4)for this above error we added encrypt = false and deployed app again still same.
asked
1 answers
0

The readiness probe failure looks more like a symptom than the actual root cause.

Based on the logs you shared, the Mendix runtime is unable to establish a JDBC connection to SQL Server:

PKIX path building failed
unable to find valid certification path to requested target

If the runtime cannot connect to the database during startup, it will never finish initializing and start listening on port 8080. As a result, Kubernetes readiness checks will fail with:

connect: connection refused

I would focus on the SQL Server SSL/certificate configuration rather than the ingress or readiness probe.

A few things worth checking:

  • Whether SQL Server is enforcing encrypted connections.
  • Whether the SQL Server certificate chain is trusted by the runtime.
  • Whether the new encrypt=false setting is actually being picked up by the deployed pod.
  • Differences between Prod and non-Prod database connection settings.

Since the pod itself is running but the application never becomes ready, the JDBC SSL error is the strongest lead here. The readiness probe is most likely failing because the Mendix runtime has not completed startup successfully.


answered