Git clone not working - error 443

Question

I am working from home and am trying to clone a repo from Github and am getting the following error:

git clone https://github.com/account/repo.git

Also tried

git clone git://github.com/account/repo.git

Error: Failed connect to github.com:443; No error while accessing https://github.com/account/repo/info/refs?service=git-upload-pac
fatal: HTTP request failed

I even tried to use SSH and this is what I get:

ssh: connect to host github.com port 22: Bad file number fatal: could not read from remote repository.

I was just able to clone it on my laptop so I know that I have the correct permissions, I just need help trying to figure out why this is happening on my desktop and it seems that all of the other suggestions don't seem to be working.

I am not using a proxy.
I cannot do pulls on other repos that already exist either.

EDIT Ok I ran the command suggested, here are the results:

$ ssh -i ~/.ssh/id_rsa -vvv git@github.com
OpenSSH_4.6p1, OpenSSL 0.9.8e 23 Feb 2007
debug2: ssh_connect: needpriv 0
debug1: Connecting to github.com [204.232.175.90] port 22.
debug1: connect to address 204.232.175.90 port 22: Not owner
ssh: connect to host github.com port 22: Bad file number

Any suggestions?

The actual command or what client? The client I was the git bash for windows, and then I installed just the vanilla git - neither worked. Same command client on laptop worked. — gregwhitworth, Apr 09 '13 at 18:04
443 is not an error number, it's the port number for the https protocol. — Keith Thompson, Apr 09 '13 at 18:38
Please post the output of following: `ssh -i ~/.ssh/id_rsa -vvv git@github.com`. Replace `id_rsa` with a valid github key if needed. — Andrejs Cainikovs, Apr 09 '13 at 18:42
possible duplicate of [Git SSH error: "Connect to host: Bad file number"](http://stackoverflow.com/questions/7144811/git-ssh-error-connect-to-host-bad-file-number) — Andrejs Cainikovs, Apr 09 '13 at 18:44
What happens if you try `git clone git@github.com/account/repo.git` ? — vtacreative, Apr 09 '13 at 20:48
It comes back with an error of: fatal: repository does not exist. Although I know it does. Again I can deal with github fine on my laptop and at work. Do you think this means something? — gregwhitworth, Apr 09 '13 at 21:30
I'm not on a proxy - that I'm aware of at least. Any help on where to check this would be appreciated. — gregwhitworth, Apr 09 '13 at 22:10
possible duplicate of [GitHub - HTTPS access](http://stackoverflow.com/questions/3512202/github-https-access) — Praveen, Sep 03 '14 at 04:23

score 4 · Accepted Answer · answered Apr 13 '13 at 16:57

4

I know this may be general but I decided I wanted to get this answered, so here is what I did and it is now working correctly:

Uninstalled ALL git clients through windows (I had a couple initially for testing)
Installed the basic git bash from git
Turned off smart screen and ensured firewall and defender were off (they were)

Tried it again and it now works. My best guess is there was a mis-configuration somewhere - probably a wrong key (not sure how that happened since I updated it). At any rate it is working. It's probably the nuclear option but I hope this helps someone else that runs into this.

answered Apr 13 '13 at 16:57

gregwhitworth

2,136
4
22
33

Were firewall and denfender turned off when you originally encountered the problem >? It seems as if port 443 and port 22 were both blocked. See also http://stackoverflow.com/questions/7144811/git-ssh-error-connect-to-host-bad-file-number – Wade Williams Apr 20 '13 at 03:08
No, I wish though, it's the weirdest thing. even when checking with netstat the ports are not being used, no matter what I did. It's just a very finicky type of problem. I actually just had it happen again, changed nothing and restarted and it ended up working again. I'm thinking I may need to do a good cleaning. – gregwhitworth Apr 21 '13 at 03:16
when in doubt, throw it out... and restart from a fresh system/install. – Wade Williams May 28 '13 at 23:04
1

Too technical! Is there another alternative way to resolve this? Your answer might not be effective for everyone. Too long process when uninstalling. – David Dimalanta Jul 09 '13 at 03:03

score 3 · Answer 2 · edited Jun 18 '15 at 17:45

3

I could resolve the 443 error by issuing this command :

git config --global http.proxy <proxyname:port>

edited Jun 18 '15 at 17:45

sjas

18,644
14
87
92

answered Jun 18 '15 at 16:50

dghadge

39
1

1

Please explain the idea behind this and why it may have helped so that people can fully understand your answer. – SuperBiasedMan Jun 18 '15 at 17:10

score 3 · Answer 3 · answered Jan 18 '16 at 07:37

3

Usually this means that your network is protected by a proxy server. To config git to use proxy, use this command:

git config --global http.proxy <http[s]://userName:password@proxyaddress:port>

if the proxy server doesn't have username and passeord, use this command

git config --global http.proxy <proxyaddress:port>

answered Jan 18 '16 at 07:37

Mahmood Dehghan

7,761
5
54
71

git config --global http.proxy Works like a charm to me – Yuri Jan 08 '18 at 19:10
how do you find the proxy address. Is the username your github username? – Josh Zwiebel Feb 10 '23 at 20:49

Git clone not working - error 443

3 Answers3