Has @aceofwings added you as a collaborator on that repository? Since it is private, if they haven’t done that, you won’t be able to access the repository. Beyond that, since it is a private repository you should probably contact private support at https://github.com/contact. They will have the access to take a look at what might be going wrong.

Thanks for your reply.

OK, I’ll try that.  But with several days downtime, a couple of hours trying to fix the issue github appears to be too expensive as far as lost time goes to be worth using.  Unless your suggestion saves the day.

thanks

This can be closed.  Since we cant use Github we have decided to use an alternate.

I have a similar issue to Marvelous-Software.  I created/initialized a local repo (“testrepo”) in Bash/Git, added a file and did an initial commit.  I tried running this command:

git remote add origin https://github.com/<my-github-username>testrepo.git

as well as one similar to what you suggested:

git remote set-url origin https://github.com /<my-github-username>testrepo.git

In both cases, the command git remote --verbose returned results that the above url (minus the .git at the end) existed for fetch and pull.

However, when I go to my github account, the aforementioned repo doesn’t exist.

Any suggestions?

@skipstevenson when you create a repo locally, GitHub has no way of knowing you did that. So you have to tell GitHub to create a repo on GitHub for you. You can do this in a few different ways, the simplest one is to go to https://github.com/new and follow the instructions. Once you’ve done that, then the remote connection you’ve defined already will work.

I hope that helps!

go to this url. It worked for me.

Thank you, this worked! Trying to set up GitHub for the first time, and I kept getting the fatal : repository not found error, despite the repository being public in GitHub. 

Used the command you provided, followed by push, and success.

I put together a list of five different reasons why this error might happen over on TSS. You might find this helpful.

https://www.theserverside.com/blog/Coffee-Talk-Java-News-Stories-and-Opinions/Five-ways-to-fix-Gits-fatal-repository-not-found-error

This worked for me, thank you! I have been using Source Control on VS Code for ages and it suddenly stopped working but this fixed it… cheers

I just tried 

git remote set-url origin https://YOUR_GITHUB_USER@github.com/aceofwings/RotairERP.git

and it didn’t work 

Works great!

Then create a Personal Access Token with repo & read/write permissions (or whatever your use case is) as the password.

Thanks @skipstevenson  for this solution. It work for me

Trying to push my the very first commit into my private repo:

C:\TMP\New folder>git remote add origin https://github.com/glestwid/tcc.git
fatal: remote origin already exists.

C:\TMP\New folder>git remote --verbose set-url origin https://github.com/glestwid/tcc.git

C:\TMP\New folder>git push origin master
remote: Repository not found.
fatal: repository ‘https://github.com/glestwid/tcc.git/’ not found

C:\TMP\New folder>

I do see the repo on my page at Github but at the same time git nither asks me regarding credentials nor gives me an access. What did i do wrong?

Is the name of the repo tcc? Or tcc.git? If it is tcc.git then the remote you listed could be ambiguous.

Just to add. If you use the old password/token for the new private repo, you need to create a new token.
Also, git credential-manager uninstall before push may help

In my case, this error was caused by authenticating with an SSH key which was uploaded to my GitHub account through the GitKraken client. I will let the GitHub support response explain the issue:

Thank you for contacting GitHub support. It looks like the only SSH key that is associated with your user account was generated by the GitKraken OAuth application. In order to use this SSH key in the organization, you would need to request organization approval for GitKraken and have it be granted. Otherwise, you can create a new SSH key that is not associated with an OAuth application so no organization approval is required.

I generated a new key and added it to github according to their documentation, then configured my GitKraken client to use the local ssh-agent. From then it worked.

They further explained that right now, there is no good way to learn this information yourself. Best of luck, developer from the future!