vorta
vorta copied to clipboard
Vorta not listing my ssh key
Describe the bug Using Vorta 0.8.4 on Fedora 36 I can no longer select the proper ssh key in the GUI, leaving SSH Key on "Automatically choose SSH Key (default)" seems to work correctly, and I can see 4 otther keys that are stored in ~/.ssh and permissions are the same for all (600 fir the private key, 644 for the pub key).
To Reproduce Steps to reproduce the behavior:
- Go to 'Repository'
- Click on 'SSH Key'
- Search for missing key
Environment (please complete the following information):
- OS: Fedora 36
- Vorta version: 0.8.4
- Installed from: Flathub
Vorta and Borg versions can be found in Main Window > Misc Tab.
Additional context If appropriate include logs. Can be found in Main Window > Misc Tab > Log.
You will have to elaborate. It isn't clear what kind of key your missing and which keys you see instead as well what is working when selecting auto mode.
I'm talking about ssh keys listed in ~/.ssh:
[redacted@gigabyte-x570-aorus-ultra ~]$ ls -a .ssh/
. config id_rsa_8k.pub ramnode_rsa
.. id_ed25519_redacted id_rsa.pub ramnode_rsa.pub
authorized_keys id_ed25519_redacted.pub id_rsa_yubikey.pub
borgbase id_rsa known_hosts
borgbase.pub id_rsa_8k known_hosts.old
As you can see, there are multiple keys here but for some reason I can not see 'borgbase' in the SSH key in the 'repository' tab on the main screen, however, leaving it to 'Automatically choose SSH Key (default)' seems to work fine.
I can see the other keys though
Is the key format of the borgbase
key one of RSA, ECDSA or Ed25519?
I have the same problem on Mac. It only lists "Default" and one in ed25519 format. The other ones in RSA/ECDSA format are not shown.
This might also affect linux (initial post). More details are needed here.
I have a similar issue.
Ubuntu 20.04.4 LTS Vorta Verstion 0.8.7 installed from flathub
in .ssh directory there are two ssh keys (id_rsa, id_ed25519). in the dropdown menu in Vorta, only id_rsa is showing, I cannot select id_ed25519. I am using the non-showing ssh key in other use cases, so it is no issue with the key itself.
I hope this doesn't get into your way to taking over the world @wurstbrotfan.
I dont think I can take over the world without a decent backup structure
I am sorry to hear that. You can get more debug information by running the current master branch which you can install with
pip install git+https://github.com/borgbase/vorta#egg=vorta
thank you for your support!! :) so, it's weird, after I installed the master branch I could connect to the repo by keeping "Automatically choose ssh key" setting. I think I tried exactly this yesterday and it didn't work. I am 100% certain that the ssh key configured for the repo is the one which is not showing in the dropdown. btw it is still not showing, no ssh log entries in vorta.log If I can do any more debugging for you let me know. and thanks again of course
thank you for your support!! :) so, it's weird, after I installed the master branch I could connect to the repo by keeping "Automatically choose ssh key" setting. I think I tried exactly this yesterday and it didn't work.
That is very weird since that feature outsources choosing the key to ssh
itself. It is therefore also independent of the key list in vorta.
btw it is still not showing, no ssh log entries in vorta.log If I can do any more debugging for you let me know. and thanks again of course
After installing, quit vorta from the tray menu and restart it. Post the logs from the start time to the line containing borg --version
here.
I am not all that sure if I carried this out correctly so I will tell it step by step
- uninstalled vorta
- reinstalled vorta through
flatpak install flathub com.borgbase.Vorta
- installed latest master
pip install git+https://github.com/borgbase/vorta#egg=vorta
- started vorta (will it automatically run the latest master branch I pulled, or do I have to start it "differently"?. Log file reads 2022-08-30 21:53:38,642 - vorta.i18n - DEBUG - Loading translation succeeded for ['en', 'en-US', 'en-Latn-US']. 2022-08-30 21:53:39,148 - root - INFO - Using NetworkManagerMonitor NetworkStatusMonitor implementation. 2022-08-30 21:53:39,500 - vorta.borg.jobs_manager - DEBUG - Add job for site default 2022-08-30 21:53:39,500 - vorta.borg.jobs_manager - DEBUG - Start job on site: default 2022-08-30 21:53:39,526 - vorta.borg.borg_job - INFO - Running command /app/bin/borg --version
Let me know if I should try anything else or differently.
Dont know if any of this is useful, let me know if I should try anything else
edit: I should add that everything is working and the correct ssh key is added when using "Automatically choose ssh key" setting. Thus it's a rather cosmetic bug in my case.
Vorta can be installed as a flatpak which will show up in your application menu automatically. Alternatively it can be installed as a python package (since it is coded using Python). Currently you are starting the flatpak application. To start the python package installed using pip, open a console and enter vorta
. This should start the non-flatpak version. However you might have to install borg with apt.