fatal: unable to access '...': Could not resolve host: github.com
Git can't resolve the remote's hostname
Seen in git over HTTPS, CI runners, Docker builds
Git could not turn the remote's hostname into an IP address, so it never reached the server.
Common causes
- No working DNS: offline, captive Wi-Fi portal, VPN that changed resolvers, or a container with a broken resolv.conf.
- A typo in the remote URL or a hostname that only resolves on an internal network.
- A proxy is required but git is not configured to use it.
How to fix it
- Check the remote URL with git remote -v and correct it with git remote set-url origin <url>.
- Test name resolution outside git, e.g. nslookup github.com.
- If you need a proxy, set it: git config --global http.proxy http://proxy.example.com:8080.
Got a different message? Paste it into the error explainer.
Related errors
- getaddrinfo EAI_AGAIN registry.npmjs.org · npm couldn't resolve the registry hostname
- Error response from daemon: Get "https://registry-1.docker.io/v2/": dial tcp: lookup registry-1.docker.io: no such host · Docker can't resolve the registry hostname
- fatal: unable to access '...': SSL certificate problem: unable to get local issuer certificate · Git can't verify the server's certificate
- 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