How to fix Failed to connect to server: connection refused (HTTP/2) in Kubernetes

What this error means

gRPC or HTTP/2 services fail when pods refuse connections on the expected port. Network policies, service configuration, or application setup blocks HTTP/2 traffic. The pod either is not listening or is actively rejecting connections.

Typical symptoms

• gRPC client errors: "connection refused"
• HTTP/2 frame errors or connection resets
• Service shows unhealthy endpoints
• kubectl port-forward works but client connections fail
• Different behavior between HTTP and HTTP/2 traffic
• Intermittent connection refusal depending on load
• Application logs show socket binding errors

Common causes

1. Pod not listening on expected port
2. Port number mismatch in Service configuration
3. Network policy blocking gRPC traffic
4. Application using HTTP/1.1 but service expects HTTP/2
5. Firewall blocking connection to pod port
6. Service endpoint port misconfigured
7. Load balancer protocol mismatch

How to fix "Failed to connect to server: connection refused (HTTP/2)"

Advanced notes

Frequently asked questions

What does "Failed to connect to server: connection refused (HTTP/2)" mean?

gRPC or HTTP/2 services fail when pods refuse connections on the expected port. Network policies, service configuration, or application setup blocks HTTP/2 traffic. The pod either is not listening or is actively rejecting connections.

How do I fix "Failed to connect to server: connection refused (HTTP/2)"?

gRPC or HTTP/2 services fail when pods refuse connections on the expected port. Network policies, service configuration, or application setup blocks HTTP/2 traffic.

What causes "Failed to connect to server: connection refused (HTTP/2)"?

Pod not listening on expected port Port number mismatch in Service configuration Network policy blocking gRPC traffic

Is the "Failed to connect to server: connection refused (HTTP/2)" 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

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

  How to fix "HTTP probe timeout" error in Kubernetes

  HIGH

• unable to get metrics for resource cpu: no metrics returned from resource metrics API

  How to fix "HorizontalPodAutoscaler unable to scale" in Kubernetes

  MEDIUM

• HTTPS probe failed: x509: certificate signed by unknown authority

  How to fix "HTTPS probe certificate error" in Kubernetes

  HIGH

• unable to compute new replica count for HPA: missing request metric

  How to fix "HPA unable to compute replicas" 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 Docs: Services(Official Docs)
• 📖
  Kubernetes Docs: Debugging Services(Official Docs)
• 💬
  Stack Overflow: Kubernetes HTTP/2 issues(Stack Overflow)