Git: Could not resolve host github.com error while cloning remote repository in git

Question

What I did: I have created a remote repository on Github and I am trying to clone the remote repository on my local machine. While cloning I am providing the clone URL & target folder.

But every time I try to clone, I am getting this error:

Error: "fatal: unable to access 'https://github.com/hyperion057/spring-repo.git/': Could not resolve host: github.com"

What do I need to do to connect to GitHub ?

What command are you using? Are you cloning by https or ssh? I just tried to clone your project and it worked. — Raul Rene
– Raul Rene, Commented Dec 4, 2013 at 8:21
Open a terminal and execute git clone [email protected]:hyperion057/spring-repo.git — Raul Rene
– Raul Rene, Commented Dec 4, 2013 at 8:57
do i need to configure proxy settings? because my office has got proxy servers. — HyperioN
– HyperioN, Commented Dec 4, 2013 at 9:22
The errors you are getting are basically telling you it cannot connect. You have probably set your proxy to the browser, but not on the entire machine. Try to set the proxy accordingly and try again. — Raul Rene
– Raul Rene, Commented Dec 4, 2013 at 9:24

mfaani · Accepted Answer · 2025-08-27 11:03:17Z

441

I got a similar error, and it's caused by incorrect proxy setting. This command saved me:

git config --global --unset http.proxy

https version:

git config --global --unset https.proxy

After doing the above, you may need to turn off and then turn on your WiFi or quit and relaunch terminal.

edited Aug 27 at 11:03

mfaani

37.2k20 gold badges195 silver badges329 bronze badges

answered Feb 3, 2015 at 16:05

Brian

31.5k15 gold badges91 silver badges88 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

Shawn Erquhart Over a year ago

This is worth trying even if you never touched the proxy setting and aren't behind one currently. I think this was somehow set automatically during a past hotel stay (or when using in-flight wifi) where a proxy was in place.

degs Over a year ago

Note that this will only unset the HTTP proxy. If you're having difficulty connecting to HTTPS locations, use the sister command 'git config --global --unset https.proxy'

Chris Fremgen · Accepted Answer · 2016-01-13 22:02:31Z

278

Spent a couple hours trying to fix this.

Re-connecting my wifi did the trick.

answered Jan 13, 2016 at 22:02

Chris Fremgen

5,5371 gold badge28 silver badges28 bronze badges

4 Comments

Ekown Over a year ago

This fixed my problem. What is the reason why this fixes it?

Uchenna Adubasim Over a year ago

Also fixed mine. It's simply poor network connection.

Sakiboy Over a year ago

Restarting my computer fixed this... something must've gotten weird with the network connection?

Selvaraj Balakrishnan Apr 20 at 11:35

Simple wifi reconnect fixed mine

VonC · Accepted Answer · 2020-08-07 15:26:51Z

do i need to configure proxy settings? because my office has got proxy servers.

Yes, you can do so by setting HTTP_PROXY, and HTTPS_PROXY environment variables.

See "Syncing with github":

set HTTPS_PROXY=http://<login_internet>:<password_internet>@aproxy:aport
set HTTP_PROXY=http://<login_internet>:<password_internet>@aproxy:aport
set NO_PROXY=localhost,my.company

(To avoid putting your credentials -- username/password -- in clear in the proxy URL, see below)

Note the NO_PROXY, to allow to access internal site to your company

You also can register that in your git config:

git config --global http.proxy http://<login_internet>:<password_internet>@aproxy:aport

But if you have incorrect proxy Git settings, remove them:

cd /path/to/repo
git config --unset http.proxy
git config --global --unset http.proxy
git config --system --unset http.proxy

git config --unset https.proxy
git config --global --unset https.proxy
git config --system --unset https.proxy

# double-check with:
git config -l --show-origin | grep -i proxy

No credentials needed: use genotrance/px.
If you are, as I am, in a company behind a NTLM proxy, all you need to do is:

unzip px-v0.4.0.zip anywhere you want

change the px.ini config file (put it in %USERPROFILE%), chaging the server line:

[proxy]
server = proxy.my.company:8080  <= use your company proxy:port
listen = 127.0.0.1
port = 3128

use HTTP(S) proxy variable without your credentials! (the px proxy will reuse the ones from the current Widows session, either through Microsoft SSPI or Microsoft Kerberos)

That will give you:

set HTTPS_PROXY=http://127.0.0.1:3128
set HTTP_PROXY=http://127.0.0.1:3128
set NO_PROXY=localhost,my.company

@Sara The login/password of your Windows session when you are using an enterprise proxy.

Chadams · Accepted Answer · 2014-01-19 19:47:32Z

66

another possibility, I ran into this problem myself. But it was after I had installed a VPN (which was unrelated and running)

turning off the VPN, fixed the issue.

for the record, I was running "Viscosity" VPN on my MacBookPro

answered Jan 19, 2014 at 19:47

Chadams

1,9631 gold badge18 silver badges15 bronze badges

1 Comment

Surpher Over a year ago

heh, for me it's the other way around. github.com resolves only when I'm on VPN. :|

Ruli · Accepted Answer · 2021-11-24 11:22:14Z

55

Would like to note, when I did Brian's solution:

git config --global --unset http.proxy

Make sure to quit and restart terminal. Mine didn't resolve until I did that.

edited Nov 24, 2021 at 11:22

Ruli

2,82113 gold badges35 silver badges48 bronze badges

answered Jan 26, 2017 at 22:58

agrippa

90910 silver badges8 bronze badges

Comments

scosman · Accepted Answer · 2019-01-10 17:34:34Z

43

I've had the same issue after running out of disk space. Closing and reopening terminal fixed it one time. Restarting my Mac the next.

Some easy things to try before jumping to random commands:

restart terminal tab
restart terminal app
If disk is full (or close to it) free up some disk space then restart terminal app
restart machine/OS

edited Jan 10, 2019 at 17:34

answered Oct 21, 2016 at 12:29

scosman

2,60323 silver badges41 bronze badges

1 Comment

mwil.me Over a year ago

Just closing a terminal tab is sufficient as well.

Developer · Accepted Answer · 2014-12-29 19:37:24Z

24

192.30.252.128 is the current IP of github.com which can be set in your local DNS (/etc/hosts in Linux and C:\Windows\System32\drivers\etc\hosts)

answered Dec 29, 2014 at 19:37

Developer

2412 silver badges2 bronze badges

1 Comment

Ashutosh Jindal Over a year ago

Current IP Addresses are listed here: api.github.com/meta (from help.github.com/articles/about-github-s-ip-addresses) and here is a tool to convert CIDR to ip range : ipaddressguide.com/cidr

d-man · Accepted Answer · 2021-08-07 11:02:45Z

From the answer here -> my solution is specific for Windows Subsystem for Linux (WSL) users. None of the answers relating to proxies are relevant to my solution.

If you are unable to run a ping command e.g.

# WSL
ping google.com

Then it is likely your file at /etc/resolve.conf is corrupt. To fix this run the following in a WSL window:

# WSL
sudo rm /etc/resolve.conf

Then open a Powershell terminal in Administrator mode and run

# Powershell
wsl --shutdown
Get-Service LxssManager | Restart-Service

This should fix the problem, which can be tested by running the ping command again.

Simply deleting the /etc/resolve.conf file fixed the issue for me, I didn't needed to restart WSL

Ruli · Accepted Answer · 2021-11-24 11:32:58Z

13

I solved it by using this command

$git config --global http.proxy http://enter_your_proxy:enter_port

edited Nov 24, 2021 at 11:32

Ruli

2,82113 gold badges35 silver badges48 bronze badges

answered May 10, 2016 at 6:54

Ankit Bhardwaj

1511 silver badge3 bronze badges

Comments

yasi · Accepted Answer · 2021-01-06 15:13:12Z

10

Maybe it is because of your internet access, You can try:

ping google.com

If you get this error again, there was problem in your network configuration.

answered Jan 6, 2021 at 15:13

yasi

5671 gold badge5 silver badges16 bronze badges

Comments

Kushagra Kumar · Accepted Answer · 2023-05-09 02:17:08Z

5

Restarting my EC2 instance fixed the issue.

answered May 9, 2023 at 2:17

Kushagra Kumar

3013 silver badges4 bronze badges

Comments

johnwbyrd · Accepted Answer · 2015-07-22 18:06:16Z

4

In my case, on a Windows box, my TCP/IP stack seems to have needed to be reset. Resetting the TCP/IP stack of the client PC caused git to start behaving properly again. Run this command in Administrator mode at a command prompt and retry the git command:

netsh int ip reset

Manually disabling and re-enabling the network adapter via the Control Panel produces a similar result.

I suspect DNS resolution problems inside the TCP stack on my Windows box.

edited Jul 22, 2015 at 18:06

answered Apr 25, 2015 at 2:48

johnwbyrd

3,8082 gold badges31 silver badges25 bronze badges

Comments

Chris Yim · Accepted Answer · 2015-11-28 04:02:16Z

3

When you tried above solutions and nothing helps, you may need to checkout your local network settings and try to add 8.8.8.8 and your local router ip to the DNS filed.

edited Nov 28, 2015 at 4:02

answered Nov 13, 2015 at 4:37

Chris Yim

1,39211 silver badges12 bronze badges

Comments

John Yin · Accepted Answer · 2016-01-27 00:01:31Z

I had this very similar error as following.

C:\wamp\www\myrepository [master]> git push
fatal: unable to access 'https://github.com/myaccount/myrepository.git/': Couldn't resolve host 'github.com'

Actually, the prompt message has told us where's wrong.

https://github.com/myaccount/myrepository.git/

When I check my github, I found my github repository's HTTPS url is

https://github.com/myaccount/myrepository.git

I don't know how this happened. The wrong url has been set up by installed Git Shell automatically.

Once I remove the '/' at the end, I can push successfully.

git remote -v to see the remotes. git remote set-url origin https://github.com/USERNAME/REPOSITORY.git to set the remote.

saylestyler · Accepted Answer · 2017-03-07 02:20:37Z

3

Edge case here but I tried (almost) all of the above answers above on VirtualBox and nothing was doing it but then closing not only the VirtualBoxVM but good ole VirtualBox itself and restarting the program itself did the trick without 0 complaint.

Hope that can help ~0.1% of queriers : )

answered Mar 7, 2017 at 2:20

saylestyler

4791 gold badge6 silver badges23 bronze badges

Comments

M.Yessir · Accepted Answer · 2021-07-29 12:51:01Z

3

I ran command on terminal, then restarted terminal.

git config --global --unset https.proxy

But it din't work. Then I turned Off and On my wifi on Mac.

git push

It worked.

answered Jul 29, 2021 at 12:51

M.Yessir

2223 silver badges11 bronze badges

Comments

James Z · Accepted Answer · 2022-03-01 09:11:33Z

3

After restart git bash below works fine for me:

git push -f origin master

edited Mar 1, 2022 at 9:11

James Z

12.3k10 gold badges27 silver badges48 bronze badges

answered Sep 29, 2021 at 4:57

Nazmul Hoque

98011 silver badges10 bronze badges

Comments

Community · Accepted Answer · 2017-05-23 12:34:53Z

2

All, I want to let you all know that I was having this same issue. I solve it by resetting my remote URL git remote set-url origin https://new.url.here I found how to do this from this answer but I had to change hit to https: Change the URI (URL) for a remote Git repository

edited May 23, 2017 at 12:34

CommunityBot

11 silver badge

answered May 16, 2014 at 22:19

Lucy

292 bronze badges

Comments

Wenderson Fernandes · Accepted Answer · 2016-02-03 04:59:25Z

2

Just in case future generations stuck in this too: For me what worked (on mac OSX) was to set my DNS with opendns 208.67.222.222 , 208.67.220.220. I get this numbers here: https://www.opendns.com. For some reason, my dns configuration reseted to the default numbers (my local ip I guess), and I was not able to connect to neither github, brew or rubygems. Sorry for the misspelling.

answered Feb 3, 2016 at 4:59

Wenderson Fernandes

214 bronze badges

Comments

tig · Accepted Answer · 2017-07-04 09:47:55Z

2

One reason for this issue could be wrong/empty /etc/resolv.conf file.

The way I resolved this issue in my centos 7 minimal is as follows: my /etc/resolv.conf was empty and I added the following lines:

nameserver 192.168.1.1
nameserver 0.0.0.0

where 192.168.1.1 is my gateway, in your case it can be different.

edited Jul 4, 2017 at 9:47

answered Apr 23, 2017 at 13:01

tig

1671 gold badge1 silver badge11 bronze badges

1 Comment

Rajesh Over a year ago

after adding nameserver 8.8.8.8, it working for me and able to clone git repo

user3814933 · Accepted Answer · 2019-12-18 14:12:37Z

2

Restarting terminal in Mac worked.

answered Dec 18, 2019 at 14:12

user3814933

414 bronze badges

Comments

Zack117 · Accepted Answer · 2020-08-07 14:46:30Z

2

If you have a VPN needed to connect to your enterprise account and do a "git pull" this error will occur, just switch on your VPN and it will work.

answered Aug 7, 2020 at 14:46

Zack117

1,0851 gold badge15 silver badges30 bronze badges

Comments

Egorrishe · Accepted Answer · 2023-04-27 13:25:59Z

In my case problem was due to "Transfer ownership" of project to another Git user. When you do it, project URL changes from:

https://github.com/USER_1/repository.git to: https://github.com/USER_2/repository.git

Nevertheless it, project still accessible via old URL - so you can pull/push commits, without changing config. But, after ~1 year this URL become unreachable.

Solution:

git remote -v - to see remotes
git remote set-url origin https://github.com/USER_2/repository.git

next time change config immediately, and on ALL your computers 🤦‍♂️😁

Lalith Yagnavalkya · Accepted Answer · 2023-10-09 11:30:27Z

2

I fixed this issue by using this command

git init

answered Oct 9, 2023 at 11:30

Lalith Yagnavalkya

1791 silver badge6 bronze badges

Comments

Yusril Maulidan Raji · Accepted Answer · 2024-07-10 06:09:10Z

2

In my case, restarting my PC solved it immediately.

answered Jul 10, 2024 at 6:09

Yusril Maulidan Raji

2,0122 gold badges23 silver badges50 bronze badges

Comments

muhammed safa yaşar · Accepted Answer · 2016-12-09 18:12:45Z

As a suggestion for Ubuntu servers, you can write down essid and password of router in your /etc/network/interfaces file:

iface [en0 || your wireless driver no necessarily en0] inet static
    address 192.168.1.100 / (something for your static ip between 1-255)
    netmask 255.255.255.0
    gateway 192.168.1.1 / (this is the ip of your router)
    dns-nameservers 8.8.8.8 / (you can use whatever you want)
    wpa-ssid qwertyuio / (this is router id)
    wpa-psk qwertyuio / (this is router password for wireless connection)

When I got this error while pulling a repository to my server, I wrote wpa-ssid and wpa-psk and restarted. Then it worked.

EDIT: I faced the same issue again and this time it was because of the inconsistency in router signal levels. My connection was not strong, that was the problem. However, the solution above is a real solution for static ip

artronics · Accepted Answer · 2018-02-07 19:58:03Z

1

In my case I open a new terminal and problem solved. I don't know exactly what caused the problem in the first place though.

answered Feb 7, 2018 at 19:58

artronics

1,5132 gold badges21 silver badges30 bronze badges

Comments

Piyush · Accepted Answer · 2021-10-27 03:13:29Z

1

In case your proxy server doesn't have username and password -

Change it like this-

192.168.49.1:8282 - <your-proxy-ip>:<port>

git config ---global http.proxy 192.168.49.1:8282
git config ---global https.proxy 192.168.49.1:8282

answered Oct 27, 2021 at 3:13

Piyush

8231 gold badge9 silver badges14 bronze badges

Comments

Ruli · Accepted Answer · 2021-11-24 11:29:18Z

1

If all the above answers failed to solve your problem, try rebooting the router.

edited Nov 24, 2021 at 11:29

Ruli

2,82113 gold badges35 silver badges48 bronze badges

answered Mar 7, 2020 at 21:05

Lone Ronin

2,9501 gold badge22 silver badges33 bronze badges

Comments

The Kraken · Accepted Answer · 2021-12-30 00:39:32Z

1

Simply enter this command in your kali linux terminal before cloning repository:-

service NetworkManager start

edited Dec 30, 2021 at 0:39

The Kraken

3,1785 gold badges32 silver badges68 bronze badges

answered Dec 27, 2021 at 8:22

Hacker--Rohan Raj

797 bronze badges

Collectives™ on Stack Overflow

Git: Could not resolve host github.com error while cloning remote repository in git

47 Answers 47

2 Comments

4 Comments

2 Comments

1 Comment

Comments

1 Comment

1 Comment

1 Comment

Comments

Comments

Comments

Comments

Comments

1 Comment

Comments

Comments

Comments

Comments

Comments

1 Comment

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Linked

Hot Network Questions

Collectives™ on Stack Overflow

47 Answers 47

2 Comments

4 Comments

2 Comments

1 Comment

Comments

1 Comment

1 Comment

1 Comment

Comments

Comments

Comments

Comments

Comments

1 Comment

Comments

Comments

Comments

Comments

Comments

1 Comment

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Linked

Related