Hi Michael,
Thanks for the detailed explanation — what you’re seeing is actually normal behavior.
The Minarca client automatically generates its own SSH identity the first time it tries to connect to the server. Each connection attempt can result in a new key being uploaded if the previous attempt didn’t complete successfully. That’s why you’re seeing “mystery” SSH keys appear in the user admin page — they’re coming from the client itself, not from keys you manually added.
If you’d like, you can safely revoke or delete all of those SSH keys and start fresh. Minarca will simply generate a new one on the next connection attempt.
That said, if the connection is still failing and you’d like help troubleshooting, we’ll need a bit more technical detail about your setup, along with the relevant logs:
server.log and shell.logminarca.logThe exact locations of these files are documented in the Minarca documentation.
Once you can share those details, it should be much easier to pinpoint what’s preventing the SSH connection from completing successfully.
Best regards,
--
You received this message because you are subscribed to the Google Groups "Minarca Data Backup" group.
To unsubscribe from this group and stop receiving emails from it, send an email to minarca+u...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/minarca/bf6792f9-f94f-4760-838c-4d252554fcc9n%40googlegroups.com.
Minarca cannot find the executable named "ssh". It seams your Mac doesn't ship "ssh". Could you tell me which version of MacOS you are running ?
You might need to install ssh manually to get it working.
To make sure the server is working as expected. Could you test with a Windows Client ?
To view this discussion visit https://groups.google.com/d/msgid/minarca/8c92ba06-628b-4d1b-bff2-40cccaf55facn%40googlegroups.com.
Hello Michael,
The error below indicates that the client is unable to locate the
ssh executable, which is unexpected. Could you please
verify where ssh is located on your system? Running
which ssh in a terminal should return its full path.
I'm expecting the path to be: /usr/bin/ssh.
2026-01-04 10:40:34,185 [25024][ERROR][MainThread ] unknown exception
Traceback (most recent call last):
File "minarca_client/ui/backup_connection_remote.py", line 272, in _create_remote
File "minarca_client/core/exceptions.py", line 62, in wrapper
File "minarca_client/core/backup.py", line 314, in configure_remote
File "minarca_client/core/instance.py", line 533, in test_connection
File "minarca_client/core/instance.py", line 626, in _remote_schema
File "minarca_client/core/compat.py", line 206, in get_ssh
FileNotFoundError: ssh
Regarding testing on Windows, the goal would simply be to confirm whether the issue is client-specific or related to the server configuration.
To view this discussion visit https://groups.google.com/d/msgid/minarca/8e5eb869-de64-4591-aecd-f81365283ad8n%40googlegroups.com.
Would you be willing to test with the beta version of Minarca
client ? here: https://minarca.org/en_CA/beta
If it's not working, I might create a special version to help us
debug why Minarca cannot find the "ssh" executable in your
context.
To view this discussion visit https://groups.google.com/d/msgid/minarca/2b794776-9121-4e97-a75b-70f54fbe1bf4n%40googlegroups.com.