Unable to fetch from 'origin' - ERROR: Repository not found.

[cakemonitor]

I created a repository at the command line yesterday and then, via Gittyup, I made my initial commit and pushed to github via SSH. Today - from a different PC - I cloned the repo, made some changes, committed to a new branch, and pushed these changes back to github.

When I got home I went back to the original PC and tried to fetch the changes, but Gittyup reported Unable to fetch from 'origin' - ERROR: Repository not found. I deleted the local copy of the repo and cloned it again, also via SSH, from the command line - this worked fine. I opened the local repo in Gittyup and it showed the new commits, but when I tried to fetch it just gave the same error.

I have tried supplying the path to my SSH config file and default SSH key file via Tools -> Options... Misc, but the error persists. I have also double-checked that the origin remote is set correctly via Repository -> Configure Repository... -> Remotes.

If I delete my local copy of the repository and try to clone it directly from Gittyup it says: Failed to clone into <path_to_repo> - ERROR: Repository not found. I double checked that the URL field contains the correct SSH URL as copied-and-pasted from github.

Why am I unable to clone or fetch while using Gittyup when I can do so without issue from the command line? And what can I do to fix the issue, please?

[Murmele]

Hi @cakemonitor Which system do you use and which version of Gittyup are you using?

[cakemonitor]

Hi, I'm running Ubuntu 22.04.2 and using Gittyup v1.3.0

[Murmele]

Can you try with the development version? https://github.com/Murmele/Gittyup/releases/tag/development

[cakemonitor]

Thanks for the suggestion. I reinstalled Gittyup from the link that you provided, and the Help -> About Gittyup menu now reports: Gittyup v1.3.0 - Monday, 19 June 2023 - d3acf74. But unfortunately the issue persists.

Could it be because my SSH key type is RSA 4096-bit?

[cakemonitor]

To follow up, I don't think it's due to my SSH key. I just deleted all files in ~/.ssh and ran ssh-add -D to remove all identities. I then created a new SSH key using ssh-keygen -t ed25519 -C "<my-email>", added the key to the ssh agent with ssh-add ~/.ssh/id_ed25519, and finally at github.com I deleted the old public key and created a new one with the contents of the id_ed25519.pub public key file.

At the command line git fetch still works fine, but but clicking the fetch button within Gittyup continues to report Unable to fetch from 'origin' - ERROR: Repository not found. I also tried navigating to Tools -> Options... -> Misc and setting the path to default SSH key to /home/<user>/.ssh/id_ed25519 but this did not help.

[Murmele]

Thanks for trying also with ed25519. I will check it today in the evening

[cakemonitor]

Thanks!

A bit further info since my last message: it started working fine the next day - but I'm pretty sure I didn't change anything! All I did was clone a different repo from the same github account, just as a test, and that worked. So I switched back to trying to fetch for the original repo and suddenly it was behaving correctly!

Also, FYI, I tried Gittyup about two or three months ago but stopped using it soon after becasue this exact issue cropped up then as well. So I reverted back to using git on the command line. I've never has issues using git that way, but I'd like to use a GUI and Gittyup seems to nicely meet all my requirements.

Feel free to let me know if there is anything further I can test to help resolve the issue.

[thalesmaoanz]

I'm facing the same problem.

flatpak version v1.4.0 - 2024-05-14

It was working fine for v1.3.0

I can't push with ERROR: Repository not found.

It does work fine for CLI. It also work if I open the terminal window inside gitty.

[cakemonitor]

@thalesmaoanz do you have multiple hosts and keys configured in ~/.ssh/config ?

I think gittyup might not match the right one, when from the cli it does. So you could try commenting out ones that you're not likely to use for a while or move more specialised ones lower in the list, e.g.

github.com work-github.com # put this lower to avoid wrongly matching 'github.com' as a substring.

[thalesmaoanz]

Hi, @cakemonitor, I appreciate your suggestion.

I thought so and tried already before searching for it.

cat ~/.ssh/config

Host github.com
  HostName github.com
  User git
  IdentityFile ~/.ssh/id_rsa
  IdentitiesOnly yes

What is bugging me is the emulated terminal inside Gitty. It does work from there as well.

Any other ideas or tips? Can I verbose it?

[thalesmaoanz]

Latest update fixed it.