How to fix HTTPS probe failed: x509: certificate signed by unknown authority in Kubernetes

What this error means

HTTPS liveness/readiness probes fail due to invalid or self-signed certificates. Probes cannot verify the server certificate, causing health checks to fail. Kubernetes uses strict certificate validation by default and will reject unverified certificates.

Typical symptoms

• Probe events: "HTTPS probe failed: x509: certificate signed by unknown authority"
• Pod keeps restarting due to failed HTTPS probes
• HTTP probes work but HTTPS probes fail
• curl to pod shows certificate validation error
• Pod cannot serve HTTPS traffic
• Self-signed certificates rejected by probes
• Intermittent probe failures if certificate expires

Common causes

1. Application using self-signed certificate not trusted by kubelet
2. Certificate expired or invalid
3. Wrong certificate installed on pod
4. Certificate does not match service domain name
5. CA certificate not in system trust store
6. Probe configured with wrong TLS settings
7. Certificate revoked or blacklisted

How to fix "HTTPS probe failed: x509: certificate signed by unknown authority"

Advanced notes

Frequently asked questions

What does "HTTPS probe failed: x509: certificate signed by unknown authority" mean?

HTTPS liveness/readiness probes fail due to invalid or self-signed certificates. Probes cannot verify the server certificate, causing health checks to fail. Kubernetes uses strict certificate validation by default and will reject unverified certificates.

How do I fix "HTTPS probe failed: x509: certificate signed by unknown authority"?

HTTPS liveness/readiness probes fail due to invalid or self-signed certificates. Probes cannot verify the server certificate, causing health checks to fail.

What causes "HTTPS probe failed: x509: certificate signed by unknown authority"?

Application using self-signed certificate not trusted by kubelet Certificate expired or invalid Wrong certificate installed on pod

Is the "HTTPS probe failed: x509: certificate signed by unknown authority" error serious?

Yes. This is a high-severity error that usually blocks work until it is fixed, but the steps above resolve it.

Related errors

• invalid image format

  How to fix "invalid image format" in Kubernetes

  MEDIUM

• Liveness probe failed: HTTP probe: http://10.244.0.5:8080/health timed out

  How to fix "HTTP probe timeout" error in Kubernetes

  HIGH

• ErrImagePull: rpc error: code = Unknown desc = Error response from daemon: manifest not found

  How to fix "image not found" in Kubernetes

  MEDIUM

• Failed to connect to server: connection refused (HTTP/2)

  How to fix "HTTP/2 connection refused" error in Kubernetes

  HIGH

• upstream connect error or disconnect/reset before headers. reset reason: overflow

  How to fix "upstream connect error or disconnect/reset before headers" in Kubernetes

  HIGH

• Waiting for rollout to finish

  How to fix "Waiting for rollout to finish" in Kubernetes

  HIGH

Official resources & further reading

• 📚Kubernetes Official Documentation
• 📖
  Kubernetes API Reference(Official Docs)
• 📖
  Kubernetes Tasks: Run Applications(Official Docs)
• 💬
  Stack Overflow: Kubernetes https probe certificate error(Stack Overflow)
• 🐙
  Kubernetes GitHub Issues(GitHub)