Thanks for jumping in.
So checking in the Host machine (admin@red.machine.yh)
The user does exist both in the /home/ directory, and in the /etc/shadow
sudo su borg-user (“queen” to follow the same example) does not prompt for a password and results in a CLI prompt like this (no prepending username@host):
$
The borg-user (aka ‘queen’) is not in visible in the admin panel of the Host machine.
Also, before you posted your response, I noticed the Borg service on the Blue client machine failed. Checking the service logs I noticed the user was apparently “borg”, maybe because that was my initial username try the first time I attempted to install?
So I uninstalled the Borg app on the Blue client machine, and installed it again.
The same error remains on the borg service logs:
Could not start the service ‘borg’
Recent service logs:-- Logs begin at Tue 2022-01-04 02:52:30 WET, end at Tue 2022-01-04 19:51:16 WET. – Jan 04 19:28:26 systemd[1]: Starting Run backup borg… Jan 04 19:28:26 sudo[10795]: borg : /etc/sudoers.d/borg is owned by uid 994, should be 0 ; TTY=unknown ; PWD=/ ; USER=root ; Jan 04 19:28:26 sudo[10795]: sudo: /etc/sudoers.d/borg is owned by uid 994, should be 0 Jan 04 19:28:26 sudo[10795]: We trust you have received the usual lecture from the local System Jan 04 19:28:26 sudo[10795]: Administrator. It usually boils down to these three things: Jan 04 19:28:26 sudo[10795]: #1) Respect the privacy of others. Jan 04 19:28:26 sudo[10795]: #2) Think before you type. Jan 04 19:28:26 sudo[10795]: #3) With great power comes great responsibility. Jan 04 19:28:26 sudo[10795]: sudo: no tty present and no askpass program specified Jan 04 19:28:26 sudo[10795]: pam_unix(sudo:auth): conversation failed Jan 04 19:28:26 sudo[10795]: pam_unix(sudo:auth): auth could not identify password for [borg] Jan 04 19:28:26 sudo[10795]: borg : user NOT authorized on host ; TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/local/bin/backup-with-borg borg Jan 04 19:28:26 systemd[1]: borg.service: Main process exited, code=exited, status=1/FAILURE Jan 04 19:28:26 systemd[1]: borg.service: Failed with result ‘exit-code’. Jan 04 19:28:26 systemd[1]: Failed to start Run backup borg. Jan 04 19:51:16 systemd[1]: Starting Run backup borg… Jan 04 19:51:16 sudo[16943]: borg : /etc/sudoers.d/borg is owned by uid 994, should be 0 ; TTY=unknown ; PWD=/ ; USER=root ; Jan 04 19:51:16 sudo[16943]: sudo: /etc/sudoers.d/borg is owned by uid 994, should be 0 Jan 04 19:51:16 sudo[16943]: We trust you have received the usual lecture from the local System Jan 04 19:51:16 sudo[16943]: Administrator. It usually boils down to these three things: Jan 04 19:51:16 sudo[16943]: #1) Respect the privacy of others. Jan 04 19:51:16 sudo[16943]: #2) Think before you type. Jan 04 19:51:16 sudo[16943]: #3) With great power comes great responsibility. Jan 04 19:51:16 sudo[16943]: sudo: no tty present and no askpass program specified Jan 04 19:51:16 sudo[16943]: pam_unix(sudo:auth): conversation failed Jan 04 19:51:16 sudo[16943]: pam_unix(sudo:auth): auth could not identify password for [borg] Jan 04 19:51:16 sudo[16943]: borg : user NOT authorized on host ; TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/local/bin/backup-with-borg borg Jan 04 19:51:16 systemd[1]: borg.service: Main process exited, code=exited, status=1/FAILURE Jan 04 19:51:16 systemd[1]: borg.service: Failed with result ‘exit-code’. Jan 04 19:51:16 systemd[1]: Failed to start Run backup borg.