Vorta is trying to run Borg from wrong path, how to fix it ?

[razorree]

Vorta logs:

2025-11-05 16:34:44,930 - vorta.borg.borg_job - INFO - Running command /usr/bin/borg init --info --log-json --encryption=repokey-blake2 ssh://borgbackup@nas.local/volume1/borgbackup/mypc
2025-11-05 16:34:45,507 - vorta.borg.borg_job - WARNING - Remote: Detected locale "C" with character encoding "ANSI_X3.4-1968", which is not UTF-8.
2025-11-05 16:34:45,509 - vorta.borg.borg_job - WARNING - Remote: Qt depends on a UTF-8 locale, and has switched to "C.UTF-8" instead.
2025-11-05 16:34:45,510 - vorta.borg.borg_job - WARNING - Remote: If this causes problems, reconfigure your locale. See the locale(1) manual
2025-11-05 16:34:45,510 - vorta.borg.borg_job - WARNING - Remote: for more information.
2025-11-05 16:34:51,358 - vorta.borg.borg_job - WARNING - Remote: sh: borg: command not found
2025-11-05 16:34:51,366 - vorta.borg.borg_job - ERROR - Connection closed by remote host. Is borg working on the server?

when I SSH to my nas with borgbackup user, I can run borg but it also resides in: /usr/local/bin/borg
How to change that path in Vorta ? or tell Vorta just to use 'borg' (it's in a PATH)

When i try to log that command locally;
borg init --info --log-json --encryption=repokey-blake2 ssh://borgbackup@nas.local/volume1/BorgBackup/mypc
I got:
{"type": "log_message", "time": 1762362382.0936718, "message": "Connection closed by remote host. Is borg working on the server?", "levelname": "ERROR", "name": "borg.archiver", "msgid": "ConnectionClosedWithHint"}

above command works if I set export BORG_REMOTE_PATH=/usr/local/bin/borg before.

Strange.... so is it my borgbackup user problem? from remote shell I can access borg
and even I put export PATH=$PATH:/usr/local/bin in ~/.profile file in borgbackup user home dir (where .ssh dir is too)

[goebbe]

When you create a new repository, using Vorta, you can add additional borg Arguments.
In the "Advanced" tab, you can add "Extra borg Arguments". This is the place where you can specify e.g. the
full remote path for borg:
--remote-path='/usr/local/bin/borg'

Once the new repository is created, there is currently no easy way to see or change these Arguments.
The following issue is related: #1963

[razorree]

thx. all 3 methods work:

1. --remote-path='/usr/local/bin/borg' parameter
2. BORG_REMOTE_PATH=... env variable on a client machine

For the remote server You can prefix the clients public key on the server in ~/.ssh/authorized_keys.
command="/usr/local/bin/borg serve --debug --show-rc --show-version --verbose --info"

[goebbe]

@razorree Thanks - also for adding the third method, which was new, to me. :-)
I tried to focus on how this could be solved, using the Vorta GUI.
But it's nice to have several options, and to have them documented, here.

[razorree]

Sure, that was my idea.
At the end it's not Vorta problem, but server configuration. (So it's needed for Borg from shell too on every client)