Error response from daemon: Get "https://registry-1.docker.io/v2/": net/http: TLS handshake timeout
The TLS handshake with the registry stalled
Seen in docker pull, docker login, docker build, Docker Desktop
The Docker daemon connected to the registry but the TLS handshake did not finish within the timeout.
Common causes
- A slow, congested or lossy connection, often on Wi-Fi or a VPN.
- An MTU problem on a VPN or tunnel: small packets pass but the larger handshake packets are dropped.
- A proxy or firewall inspecting TLS is slow or interfering.
How to fix it
- Retry, and try a wired or different network to rule out the local link.
- On a VPN, test for an MTU problem and lower the interface MTU if large packets are dropped.
- If a proxy is required, configure it for the daemon (systemd drop-in or Docker Desktop proxy settings).
Got a different message? Paste it into the error explainer.
Related errors
- error: RPC failed; HTTP 413 curl 22 The requested URL returned error: 413 · The push is larger than the server or proxy accepts
- error: RPC failed; curl 18 transfer closed with outstanding read data remaining · The connection dropped during a git transfer
- fatal: the remote end hung up unexpectedly · The Git server closed the connection
- kex_exchange_identification: Connection closed by remote host · The SSH server closed the connection before the handshake
- Permission denied (publickey) · The server rejected every SSH key you offered
- Host key verification failed. · SSH couldn't confirm the server's identity
- WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! · The server's SSH host key is different from last time
- Unable to negotiate with 203.0.113.10 port 22: no matching host key type found. Their offer: ssh-rsa · The server only offers an old host key type
- Unable to negotiate with 203.0.113.10 port 22: no matching key exchange method found. Their offer: diffie-hellman-group1-sha1 · Client and server share no key exchange algorithm
- Received disconnect from 203.0.113.10 port 22:2: Too many authentication failures · The client offered too many keys before the right one
- Connection closed by 203.0.113.10 port 22 · The SSH server ended the session
- npm ERR! code ETIMEDOUT · npm couldn't reach the registry in time