Vfrdtyky

I was stuck in this problem until i noticed that i was not logged into my VPN.

Explanation:

1) If you have configured your proxy for a VPN, you need to login to your VPN to use the proxy.

2) to use it outside the VPN use the unset command:

git config --global --unset http.proxy

and remember to set the proxy when within the VPN.

Hope this comment saves someone the 3 hours I was pointlessly trying to read workarounds

On Windows:

Go to Win -> Control Panel -> Credential Manager -> Windows Credentials

Search for github address and remove it.

Then try to execute:

git push -u origin master

Windows will ask for your git credentials again, put the right ones and that's it.

I tried a few of the tricks listed here without any luck. Looks like something was getting cached by my terminal emulator (iTerm2) or session. The issue went away when I ran the command from a fresh terminal tab.

I solved such a problem by replacing https part of my remote origin with http. It is also a workaround. I think it may help someone in the future.

I had tried most of the answers here but didn't manage to resolve the issue (on Windows 10).

What resolved the problem was simply to upgrade version from git version 2.8.1.windows.1 to the latest version git version 2.10.1.windows.1

If unsetting using

`git config --global --unset-all https.proxy`

doesn't work for you .

Then check if the environment variable http_proxy and https_proxy are set . Check using this command : -

`env | grep -i proxy`

If this variable is set to something , then you can just unset it using :-

`https_proxy=""`

I had the same problem however, with a Jenkins installation. The response back from trying to clone was always:

stderr: fatal: unable to access 'https://my.gitlab.server/group/repo.git/': Empty reply from server

Unfortunately switching to http wasn't an option, so I needed the root cause. Turns out there was a http setting in the global config for the Jenkins user (likely added when we were running a self-signed cert on out gitlab instance). Taking look at the global config:

$ git config --global -l

http.sslverify=false

Removing this did the trick

$ git config --global --unset http.sslverify

(It also looks like this is a typo, with the correct key http.sslVerify)

I received the same error in pushing files to my private bitbucket repository. For some odd reasons, the request couldn't be sent and an empty reply was the result! I tried again with a proxy tunnel (you can use any other VPN applications) and it has been solved till now.

You can try for following solutions step by step one of them should work for you.

I have tried all three steps but STEP 4 worked for me.Because I was using two different git accounts

STEP 1:

• git init


• git add README.md


• git commit -m "first commit"


• git remote add origin https://github.com/XXXX/YYYY.git
  


• git push -u origin master

STEP 2

• Check your current branch git branch if you are not on branch git
checkout branch_name.




• To create new branch use git checkout -b "new branch name" to
  switch on new branch use above command

STEP 3

• 
  

  In the special case that you are creating a new repository starting from an old repository that you used as template (Don't do this if this is not your case). Completely erase the git files of the old repository so you can start a new one:

  
  
  

  rm -rf .git and repeat STEP 1

  
  

STEP 4

• 
  

  On windows you can try putting write credentials or remove git credentials from control panel by following way and repeat STEP 1

  
  
  

  Go to Win -> Control Panel -> Credential Manager -> Windows Credentials

  
  

I solved, replacing 'http..' git url with 'ssh..'
simple open .git/config file and copy it there