npm ERR! code ETIMEDOUT
npm couldn't reach the registry in time
Seen in npm install, npx, CI pipelines, Docker builds
npm tried to open a connection to the registry and got no reply before the timeout.
Common causes
- A proxy is required on this network but npm is not configured to use it.
- A firewall blocks outbound HTTPS to the registry.
- The configured registry is a mirror or private registry that is down or unreachable.
How to fix it
- Set the proxy: npm config set proxy http://proxy:8080 and npm config set https-proxy http://proxy:8080.
- Check which registry npm uses: npm config get registry, then test it with npm ping.
- Remove stale proxy settings from ~/.npmrc if you are no longer behind a proxy.
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 ERR_SOCKET_TIMEOUT · The registry connection went silent