fatal: unable to access 'https://github.com/…': Could not resolve host: github.com
DNS lookup for the Git host failed from this machine.
Exact message you may see
Could not resolve host: github.comCould not resolve host
Seen on:
Git
Meaning
No internet, broken DNS, VPN/proxy settings or a typo. Proxy environments need http.proxy configured.
Common causes
- Offline / DNS issue
- Proxy required but not configured
- Typo in the URL
⚡ Quick fix
- Check DNS: nslookup github.com
- Configure proxy: git config --global http.proxy http://proxy:8080
- Fix the URL
Detailed fix by platform
Git
git config --global http.proxy http://proxy.corp:8080
How to diagnose
- DNS — Resolves?
- Proxy — Required?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
Most viewed in Git
- Git SSL certificate problem fatal: unable to access 'https://…': SSL certificate problem: unable to get local issuer certificate
- unfinished merge fatal: You have not concluded your merge (MERGE_HEAD exists). Please, commit your changes before you merge.
- rebase in progress fatal: It seems that there is already a rebase-merge directory, and I wonder if you are in the middle of another rebase.
Other ways to find it
Where this error sits
Origin: Build & delivery. Errors that are often confused with or caused by this one (click to open):
🧠 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.
Did this fix work for you?
Report a correction or suggest an improvement
Last updated 13 Oct 2026