Unable to connect to the server: dial tcp i/o timeout Kubernetes Origin: Platform & cloud OSI layer 4 · Transport Last updated 13 Oct 2026

Unable to connect to the server: dial tcp <ip>:443: i/o timeout

kubectl can’t reach the API server at all — network path, VPN, firewall or a private endpoint you’re outside of.

Exact message you may see Unable to connect to the server: dial tcpUnable to connect to the server: net/http: TLS handshake timeoutcontext deadline exceeded
Seen on: Kubernetes

Meaning

i/o timeout means packets go unanswered: private EKS/AKS/GKE endpoints reachable only from the VPC, authorized-IP lists that don’t include you, a disconnected VPN, or a stopped local cluster.

Common causes

  • Private API endpoint and you’re outside the network/VPN
  • Your IP not in the authorized networks list
  • Cluster stopped/deleted (minikube, kind, cloud)
  • Stale kubeconfig pointing to an old IP

⚡ Quick fix

  1. Connect the VPN/bastion or enable the public endpoint for your IP
  2. Check the cluster is running
  3. Regenerate kubeconfig

Detailed fix by platform

Shell

  1. bash
    kubectl config view --minify -o jsonpath='{.clusters[0].cluster.server}'
    nc -vz <api-host> 443

How to diagnose

  1. Endpoint — Server URL in kubeconfig
  2. Reach — nc/curl to it
  3. Cluster — Running?

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

Where this error sits

Origin: Platform & cloud. Errors that are often confused with or caused by this one (click to open):

0x80070035 — 0x80070035: The network path was not found (System error 53) (Windows)0x800700350x80072EE7 — Error 0x80072EE7 (Windows Update / Microsoft Store: server name could not be resolved) (Windows)0x80072EE70x8024402C — Windows Update error 0x8024402C (cannot connect to update server) (Windows)0x8024402C14 UNAVAILABLE — gRPC Error: 14 UNAVAILABLE: No connection established / failed to connect to all addresses (API)14 UNAVAILABLEAlreadyExists — Error from server (AlreadyExists): ... already exists (Kubernetes)AlreadyExistsauth/network-request-failed — Firebase Auth: auth/network-request-failed — A network AuthError (such as timeout, interrupted connection or unreachable host) has occurred (Authentication)auth/network-request-…CDN: trunk URL couldn't be downloaded — [!] CDN: trunk URL couldn't be downloaded: https://cdn.cocoapods.org/... (iOS)CDN: trunk URL couldn…Dataflow — Dataflow job failed to start: workers can't be created (service account, network or quota issue) (Google Cloud / Firebase)DataflowUnable to…

Explore the map of this error Full error map →

🧠 Still stuck? Analyze your error

Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.

💬 What worked for others

No tips yet — did something else fix this for you?

Share what worked for you

Tips are checked by an editor before they appear. Links are removed.