github "Repository not found fatal: Could not read from remote repository" error, troubleshooting and fix

Yesterday I'm suddenly unable to access repos I work with on a daily basis. When I rebase or try to clone I get this error

ERROR: Repository not found.
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

Nothing changed. My github credentials un-chanaged. My ssh keys unchanged.

I was able to fix by regenerating my ssh keys but read on for tips on troubleshooting

  • there's a good troubleshooting page on github with help on common issues
  • first, test your ssh connection and identity using `ssh -vT git@github.com`
    • see more here
    • when I ran this command I noticed it's response "Hi <id>, .." was not the id I expected and clearly a problem

  • check your `~/.gitconfig` (does it looks correct?)
  • check the email and userid used in your repo, they should be as expected and be associated with the ssh key locally and also in github
    • you can unset 
    • git config --global --unset user.name
git config --global --unset user.email
git config --global --unset credential.helper
In my case I don't know why this problem started, but the fix was to regenerate my ssh keys AND edit my `~/.ssh/config` file IdentityFile property value which was wrong (no longer matched the latest ssh key generation steps). Need to be: `IdentityFile ~/.ssh/id_ed25519` 
Then add the ssh key to github

Then when I re-ran `ssh -vT git@github.com` it was correct. Pain in the butt problem solved.






Comments

Post a Comment

Popular posts from this blog

deep dive into Material UI TextField built by mui

Image
The Material Design system is a design system used to create consistent digital experiences across platforms such as android, web and ios. Includes: a color system a typography system a shape system a grid system it addresses motion and lots more Also includes Material Theming which makes it easy to customize Material Design to match your brand. Material Design is not just a set of guidelines it is a whole ecosystem. Material itself stopped maintaining it's react implementation and recommends opensource versions.  A very popular open source implementation is  MUI ,  a react component library  built to implement Material Design . Bills itself as the "worlds most popular React UI framework" and at this time has 1.2M weekly downloads on npm and used by over 750k projects on github (did I mention it's very popular?).  Note: there are other react component libraries implementing bootstrap and ant design for example, so up to you and your design team on what you choose. 
Read more

angular js protractor e2e cheatsheet

Many from the protractor test suite category detailed task syntax example load page load a page browser.get('yoururl') browser btn actions browser back/forward browser.navigate().back() OR browser.navigate().forward() access elements on page See Protractor API list and examples from Protractors test suite access by angular ngmodel name (must match ngmodel in the html) this is the preferred approach element(by.model('person.name')); access by the css id on the page e.g, #user_name (but this can be brittle) element(by.id('user_name')) access angular binding to get generated value i.e. for {{}} element(by.binding('person.concatName')); access angular repeat list data (must match repeat stmt in the html) See Protractor test suit l
Read more

react-router v6.4+ loaders, actions, forms and more

react-router  react-router is used for in app single page app navigation, we configure routes for pages in the app to map to components react-router has over 1bn downloads, its an industry standard (but there are others e.g. Nextjs router) many apps use react-router, many on v5.x the new react-router 6.4.x the newest major version of react router v6.4 is a significant enhancement which adds a lot of new features. react-router v6.4 offers new features to load data (loaders) and handle actions (actions).  It's done gone all Remix-y which makes sense because the same guys wrote both. eliminates a lot of boilerplate code to fetch data in useEffect() and set various loading states put your data load and update logic in react-route components instead of custom code unlike Remix, react-router v6.4 is still just all on the client (not server like Remix) paradigm shifts Lets start with a couple of high level ideas; "back to the future" so to speak OR "what's old is new ag
Read more