I am trying to set git up with http://danielmiessler.com/study/git/#website to manage my site.
I have gotten to the last step in the instructions: git push website +master:refs/heads/master
I am working using the git ming32 command line in win7
$ git push website +master:refs/heads/master [email protected]***.com's password: Connection closed by 18.104.22.168 fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists.
One problem here may be that the program is looking for [email protected]***.com. when I connect via ssh to my site I have a different username( lets say ‘abc’). so maybe this should be [email protected]***.com. If so I don’t know how to change this or if I can push under an alias
You can specify the username that SSH should send to the remote system as part of your remote’s URL. Put the username, followed by an
@, before the remote hostname.
git remote set-url website [email protected]***.com:path/to/repo
Your ssh key most likely had been removed from ssh agent
where id_rsa is a ssh key associated with git repo
I was facing same issue a while ago…
my .git/config had
url = [email protected]:manishnakar/polymer-demo.git
I replaced it with
url = https://github.com/manishnakar/polymer-demo.git
and it works now:)
Make sure you have correct url in
url = [email protected]:username/repo.git
If it’s your first push, you’ll need to set up correct upstream
$ git push -u origin master
You can check which key is used by:
$ ssh -vvv [email protected]
The reply should contain something like this:
debug1: Next authentication method: publickey debug1: Offering RSA public key: ~/.ssh/id_rsa ... You've successfully authenticated, but GitHub does not provide shell access.
Also it’s possible to define rules for ssh in
~/.ssh/config, e.g. based on aliases:
Host github HostName github.com User git IdentityFile "~/.ssh/id_rsa" Host git HostName github.com User git IdentityFile "~/.ssh/some_other_id"
You can set connect to different ports, use different username etc. for each alias.
Try removing the GIT_SSH environment variable with
unset GIT_SSH. This was the cause of my problem.
Make sure ssh-agent is running by executing the following command on your terminal:
eval $(ssh-agent -s)
Source: Github documentation
This is usually caused due to the SSH key is not matching with the remote.
Go to terminal and type the following command (Mac, Linux) replace with your email id.
ssh-keygen -t rsa -C “[email protected]”
Copy the generated key using following command starting from word ssh.
- Paste it in github, bitbucket or gitlab respective of your remote.
- Save it.
I had the same problem.
This error means that you have not specified your remote URL location upon which your code will push.
You can set remote URL by 2 (mainly) ways:
Specify remote URL via executing command on Git Bash.
Navigate to your project directory
Open Git Bash
git remote set-url origin <https://abc.xyz/USERNAME/REPOSITORY.git>
Mention remote URL direct in config file
Navigate to your project directory
Move to .git folder
Open config file in text editor
Copy and paste below lines
[remote "origin"] url = https://abc.xyz/USERNAME/REPOSITORY.git fetch = +refs/heads/*:refs/remotes/origin/*
For more detailed info visit this link.
I had a wrong ssh private key for Bitbucket along with the right one in ssh agent.
Deleted all keys first
Then added just the right key.
After doing some research I’ve finally got solution for this, you have declared a environment variable to plink.exe path. So if you remove that path, reopen the git bash and try cloning through SSH it will work.
Refer to this link
I had the same error.
The solution was following:
I’ve corrected my url in
Just copied that from HTTPS clone URL. That would be something like that:
url = https://github.com/*your*git*name*/*your*git*app*.git
Sometimes this happens to me because of network problems. I don’t understand the root problem fully, but switching to a different sub-network or using VPN solves it
If after”git push origin master” command u see the error “could not read from remote repository” then try this out
1.ssh-keygen -t rsa -b 4096 -C "youremail" 2.eval $(ssh-agent -s) 3.ssh-add ~/.ssh/id_rsa 4.clip < ~/.ssh/id_rsa.pub(it copies the ssh key that has got generated) 5.then go to your remote repository on github and goto settings-> SSH and GPG keys ->new SSH key ->enter any title and paste the copied SSH key and save it 6. now give git push origin master
In your .git/config file
[remote "YOUR_APP_NAME"] url = [email protected]:YOUR_APP_NAME.git fetch = +refs/heads/*:refs/remotes/YOUR_APP_NAME/*
git push YOUR_APP_NAME master:master
If you use Gitlab than you might need to log in and accept Gitlab new terms, before you try to pull or push.
In my case I was using an ssh key with a password to authenticate with github. I hadn’t set up pageant properly in Windows (only in cygwin). The missing steps were to point the git_ssh environment variable to plink.exe. Also, you need to get github.com into the plink known_hosts.
plink github.com y <then ctrl-c>
Hope this helps!
I sure wish intellij would have given me a more useful error, or better yet asked me to type in the ssh key password.
For my case, I am using Corporate network (without internet connection) in office. In order to pull code from github, I set https proxy in gitbash and then use https instead of ssh to pull code,it works fine. However when comes to push code, the https proxy won’t work. So either switch to Internet network (with internet connection) or set ssh proxy can solve the problem.
Actually I tried a lot of things to make it work on Win7, since changing the SSH exectun fron native to build-it and backwards and the same error. By chance, i change it to HTTPS in the “.git/config” file as:
[remote "origin"] url = https://github.com/user_name/repository_name.git fetch = +refs/heads/*:refs/remotes/origin/*
and it finally worked. So maybe it could work for you as well.
I had the same issue and after a while I saw I’m under root user (with sudo -s). May this help for someone.
I had a perfectly fine working git and suddenly I got that error when I tried to push to the master. As I found out, it was because the repository host had problems.
If you using GitHub or Bitbucket you can easily check the status at
I solved this issue by restarting the terminal (open a new window/tab).
So if you don’t really want/need to understand the underlying problem, test method is worth a try before digging deeper 🙂
In my case it was the postBuffer..
git config --global http.postBuffer 524288000
For reference read: https://gist.github.com/marcusoftnet/1177936
I had the same error, which brought me to this answer that didn’t help me. I was trying to create a new “bare” repository for the first time using the commands below to track to an NTFS location:
cd myrepository git init --bare \myserver.mycompany.localmyrepository.git git init git status git add . git status git commit -m "Initial Commit" git remote add origin \myserver.mycompany.localmyrepository.git git push -u origin master git status
My problem turned out to be using the back slashes instead of forward slashes in the NTFS location when trying to add origin to set the (new) tracked upstream branch.
I had to remove the origin using:
git remote rm origin
Then add the origin again using the expected forward slashes
git remote add origin //myserver.mycompany.local/myrepository.git
Hope this helps someone in the future.
I’ve got this error after changing computers. I’m using SourceTree with Bitbucket.
So I had to add the SSH key generated by SourceTree, on the new computer, in Bitbucket Settings > Security > SSH keys, while connected to my Bitbucket account on the web.
[email protected]:/etc/nginx$ cat .git/config ... [remote "origin"] url = [email protected]:user/.git fetch = +refs/heads/*:refs/remotes/origin/* ...
- Use ssh instead of https.
- To use ssh key in git (add ssh key).
- If you are root, use the ssh key.
$ sudo ssh-keygen $ cat /root/.ssh/id_rsa.pub $ git init $ git add file $ git commit -m "add first file" $ git remote add origin [email protected]:user/example.git $ git push -u origin master
I was getting this problem intermittently, where most of the time it would not give the error message. The solution for me was to configure LDAP correctly after my LDAP server’s IP address had changed.
/etc/gitlab/gitlab.rb configuration for LDAP was pointing to a non-existent IP address, and so changing the host to point to the proper hostname for the LDAP server fixed the issue.
To diagnose the issue, use the
gitlab-ctl tail command to help you find stacktraces. For me, I found this stacktrace:
==> /var/log/gitlab/gitlab-rails/production.log <== Net::LDAP::Error (No route to host - connect(2) for 10.10.10.12:389): /opt/gitlab/embedded/lib/ruby/gems/2.3.0/gems/net-ldap-0.16.0/lib/net/ldap/connection.rb:72:in `open_connection' ...
Make the changes to the host value in
gitlab_rails['ldap_servers'] = YAML.load <<-'EOS' main: label: 'My LDAP' # this was an IP address # host: '10.10.10.12' host: 'internal-ldap-server' # this is the fix port: 389
After changing the config file above, be sure to reconfigure gitlab
I had this problem using gitbash on windows 10. I tried several things to solve this problem, the major ones being these:
- Recreated my ssh keys and updated to bitbucket. Didn’t help
- Turned on debugging using this and found out that I was getting “shell request failed on channel 0” as asked here
- Rebooted my windows PC
None of the above helped. I ended up re-installing Git for windows This took only a few minutes as compared to other things I did and it solved the problem!
It could be a Network issue.
Try doing the
ssh -vvvT [email protected]. If the server hangs unexpectedly it could be a dodgy network connection.
Put the following in your ~/.ssh/config
IPQoS lowdelay throughput
In my case, I was trying to clone with
sudo. As per Github’s doc, you shouldn’t use sudo with git clone:
What I did is give the currrent user permission to edit the directory (Debian 9):
chown myuser:root .
Then cloned without
sudo and it worked.
I meet the problem just now and fix it by:
git config user.email "youremail".
update: I found the root cause maybe my poor network and poor proxy.