github - Git Push ERROR: Repository not found - Stack Overflow
to customize your list.
This site uses cookies to deliver our services and to show you relevant ads and job listings.
By using our site, you acknowledge that you have read and understand our , , and our .
Your use of Stack Overflow’s Products and Services, including the Stack Overflow Network, is subject to these policies and terms.
Join Stack Overflow to learn, share knowledge, and build your career.
or sign in with
I am having a very strange problem with git and github. When I try and push, I am getting:
git push -u origin master
ERROR: Repository not found.
fatal: The remote end hung up unexpectedly
I added the remote:
git remote add origin :account-name/repo-name.git
Any ideas?
12.6k51132213
Check to see if you have read-write access.
The Git error message is misleading. I had a similar issue. I had been added to an existing project. I cloned it and committed a local change. I went to push and got the ERROR: Repository not found. error message.
The person who added me to the project gave me read-only access to the repository. A change by them and I was able to push.
24.5k2189147
I ran into the same issue and I solved it by including my username and password in the repo url:
git clone https://myusername:/path_to/myRepo.git
1,87433143
I was getting the same error
ERROR: Repository not found.
fatal: The remote end hung up unexpectedly
and I had created the repository on Github and cloned it locally.
I was able to solve by opening .git/config and removing the [remote "origin"] section.
[remote "origin"]
url = :alexagui/my_project.git
fetch = +refs/heads/*:refs/remotes/origin/*
then I ran the following (again)
git remote add origin :alexagui/my_project.git
git push -u origin master
and this time I was able to push to the repository.
I got this error (but before was working). My problem was the missing ssh key binded with the Github account. You can check you current ssh keys with ssh-add -l.
If your key is missing, you can add it with
ssh-add ~/.ssh/your_key
8,74043154
I had a similar problem.
The incorrect credentials were cached in OS X's key-chain.
Check out:
git remote rm origin
git remote add origin &remote url&
I had the same problem, with a private repo.
do the following:
remove the remote origin
`git remote rm origin`
re-add the origin but with your username and pwd with writing privileges on this pvt repo
git remote add origin
https://USERNAME:/username/reponame.git
Had similar issue. The root of the problem was that I followed some online tutorial about adding a new repository to Github.
Just go to Github, create a new repo, it will ask you to add a README, don't add it. Create it, and you'll get instructions on how to push.
It's similar to the next two lines:
git remote add origin https://github.com/YOUR_USER/your-repo.git
git push -u origin master
4,615104364
If you belong to a group in Github check that you have Write Access.
This Solved my problem.
git pull https://myusername:/path_to/myRepo.git
3,99111623
If anybody faced the issue at github.com check if you have accepted an invitation after repo owner allowed commits to you. Until you accept invitation repo will be invisible for you. So you'll get ERROR: Repository not found.
1,28811422
That's what worked for me:
1. The Remotes
$ git remote rm origin
$ git remote add origin :&USER&/&REPO&.git
If your SSH key is already in use on another github rep, you can generate a new one.
2. Generating a new SSH key
$ ssh-keygen -t rsa -b 4096 -C ""
3. Addition of the key at the SSH agent level
$ eval "$(ssh-agent -s)"
$ ssh-add ~/.ssh/id_rsa_github
4. Add the new key to the Github repo.
One problem, that may be obvious to some that I don't see mentioned here, could be that you have access with ssh keys, but you are trying to connect your local repo to a remote via https.
If this is the case then the following commands should fix the issue for you:
$ git remote -v
https://github.com/private-repo.git (fetch)
https://github.com/private-repo.git (push)
$ git remote rm origin
$ git remote add origin :private-repo.git
$ git remote -v
:private-repo.git (fetch)
:private-repo.git (push)
Note that the above works assuming that:
your current remote is named origin and that you do already have a
generated ssh key connected with your github account
you already have an ssh key associated with your github account (and connected locally)
you have the correct permissions (read/write) set on github for this repo's settings.
You need to check your SSH access as the following:
this issue was because i don't add the person response on SSH in repository, read more about SSH , .
The following solved the problem for me.
First I used this command to figure what was the github account used:
This gave me an answer like this:
Hi &github_account_name&! You've successfully authenticated, but GitHub does not provide shell access. I just had to give the access to fix the problem.
Then I understood that the Github user described in the answer (github_account_name) wasn't authorized on the Github repository I was trying to pull.
Changing the content of the .git/config file helps as Alex said above. I experienced the same problem and I think it was because I changed my Github username. The local files could not be updated with the changes. So perhaps anytime you change your username you might consider running
git remote add origin your_ssh_link_from_github
7,66411122
I'm using Mac and I struggled to find the solution.
My remote address was right and as said, it was a credentials problem.
Apparently, in the past I used another Git Account on my computer and the mac's Keychain remembered the credentials of the previous account, so I really wasn't authorised to push.
How to fix?
Open Keychain Access on your mac, choose "All Items" category and search for git.
Delete all results found.
Now go to the terminal and try to push again. The terminal will ask for username and password. Enter the new relevant credentials and that's it!
Hope it'll help someone. I struggled it for few hours.
If you include your username and the repo name we can reasonably help you, at the moment we have no reason to think the repo does actually exist.
Additionally, if the repo is private and you don't have access to it, github returns "Does not exist" to avoid disclosing the existance of private repos.
EDIT: If you're not able to clone it because it's saying it doesn't exist and it's private, it's because you're not sending authentication. Ensure that your public key is added to your keyring, or use HTTP basic auth for the time being.
5,97412247
I had this issue and realized I was using a different account from the one whose repo it was. Logging in as the original user resolved the issue.
1,62153047
If you use private repository check you connection user, it must have permission for use repository.
I had the same problem. My issue was misunderstanding that I had to first create the empty repo on github before pushing to it. Doh! Including this here for anyone else who doesn't realize.
3,32821821
go to your project folder then search for the .git folder, then open the config file with notepad and check if there is your link to the github repo under: [remote "origin"], if it is different then the repo in your github then just edit it, or open a new repo with the name in the in config file
6,17262137
Have experienced the same problem. Everything was working fine for years and then suddenly this error.
The problem turns out was that I added a deploy key for another repo to my SSH agent before my user's github SSH key (which I always used to access the repo in question). SSH agent tried the deploy key for another repo first, and GitHub for some totally unexplainable reason was saying
ERROR: Repository not found.
Once I've removed the deploy key from SSH agent, everything was back to normal.
My solution may be useful to some of you.
I got the same error after updating my macbook's OS to Yosemite. My problem got fixed by recreating my ssh key. You can do this by following step 2 of this page:
Create a Fork
If don't have write access to that repository, you don't need it. Create a fork by following
-- it's your own clone of the repository which you can modify freely.
After creating the fork, you can then clone that repo to your computer.
git clone :&your-git-handle&/&repository&.git
// It will be cloned to your machine where you run the command
// under a &repository& folder that it will create.
Checkout a new branch and make changes.
git checkout -b my-new-feature
To submit your changes to the original repository, you'll need to make sure that they're pushed
/* make changes */
git commit -am "New Feature: Made a new feature!"
git push origin my-new-feature
To get these changes into the original repository that you forked from, you can submit a Pull Requests by following . A Pull Request basically, you request that the user with write access to a repository pull down the changes you've made. Think of it like "I request that you pull my changes into your repo."
Note: Your fork will not stay up-to-date with all of the changes going on in the original repository, though. You'll have to pull down those changes periodically -- but this is easy.
After creating the fork, you can link to repo that you've forked from so that you can pull in it's changes and keep stay current.
git remote add upstream :&git-user-handle&/&repository&.git
Once you've done that, keeping in sync with the changes made on the original repo is quite easy.
git checkout master
// checkout your local master
git pull upstream master
// fetch changes from the master branch of the repo you forked from.. which is linked to your fork under the alias "upstream" (common naming convention)
git push origin master
// push the pulled changes onto your local master
git checkout -b new-branch
// create a new branch and start making changes
9,36722939
Here is how to solve my issue
#check current github account
#ensure the correct ssh key used with github
ssh-agent -s
ssh-add ~/.ssh/YOUR-GITHUB-KEY
#re-add the origin
git remote add origin :YOUR-USER/YOUR-REPO.GIT
git push -u origin master
12.8k48149271
I had the same problem. Try the following:
1. Modifying the Keychain Access in Mac for git credentials solved the problem for me.
2. Resetting origin url
git remote rm origin
git remote add origin :account-name/repo-name.git
I needed to kill credential-helper processes (were multiple) and it solved the issue after providing credentials once again.
killall git-credential-cache--daemon
If you use Git on Windows, please try to clear your credentials:
Locate "credential manager" (should be in your Control Panel)
Remove all credentials related to GitHub
I faced same error after updating my ubuntu to next version
I just deleted my sshkey on github account and then re added an sshkey to that account.
5,10213239
protected by ♦
Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10
on this site (the ).
Would you like to answer one of these
Not the answer you're looking for?
Browse other questions tagged
Stack Overflow works best with JavaScript enabledBy Joe Fylan
Joe uses WordPress almost every day and enjoys writing about his experiences for a number of different blogs.
If you need help with your next project, or you want some cracking content for your blog, you know where to look.
Categories}