Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Unable to connect to git remote repository

Tags:

git

github

After performing git push -u origin master, I got:

fatal: unable to access 'https://github.com/xxxx/xxxx.git': Failed to connect to 127.0.0.1 port 8087: Connection refused 

Same error occurred, when I tried to clone other repositories, too.

The Port 8087 doesn't seem to be busy. What could go wrong?

Edit: when I do clone from git:// instead of https://, it works just fine.

like image 437
LoveProgramming Avatar asked Jul 03 '14 00:07

LoveProgramming


People also ask

How do you fix fatal could not read from remote repository please make sure you have the correct access rights and the repository exists?

The Git “fatal: Could not read from remote repository” error occurs when there is an issue authenticating with a Git repository. This is common if you have incorrectly set up SSH authentication. To solve this error, make sure your SSH key is in your keychain and you connecting to a repository using the correct URL.

How do I fix git GitHub Permission denied Publickey fatal could not read from remote repository?

The “Permission denied (publickey). fatal: Could not read from remote repository” error is caused by an issue with the way in which you authenticate with a Git repository. To solve this error, make sure your key is being used on your Git account. If it is not, add your key to Git.

Why my git clone is not working?

If you have a problem cloning a repository, or using it once it has been created, check the following: Ensure that the user has gone through initial GitCentric login and has the correct username, email, and ssh. This should return a usage message that refers to the config-branch, config-repo, and ls-repo commands.


1 Answers

This happens because a proxy is configured in git.

Since it's https proxy (and not http) git config http.proxy and git config --global http.proxy can't help.

1 : take a look at your git configuration

git config --global -l 

If you have nothing related to https proxy like https_proxy=... the problem is not here.

If you have something related to https proxy then remove it from the file ~/.gitconfig and try again

2 : if it still doesn't work, unset environment variables

Check your environment variables :

env|grep -i proxy   

You should have one or several lines with https_proxy=...

Unset one by one with : unset https_proxy (or HTTPS_PROXY depending of the name of the variable)

3 : check environment variables again

env|grep -i proxy

If it shows nothing you should be good.

Note : This solution can applies to http and https proxy problems. just the variables name changes from https to http

like image 66
Laurent Avatar answered Sep 21 '22 20:09

Laurent