Hi Pim,
The reason for this had nothing to do with any "remote host", it was that the "backuppc" user had no shell configured!# grep backuppc /etc/passwd backuppc:x:994:990::/var/lib/BackupPC:/sbin/nologin After changing the shell to /bin/bash for backuppc, all errors disappeared. Running backups automatically and from the web application succeeded with the jump host.
Glad you got it to work.
Apparently a shell is required to use a jump host from the ssh command in this situation?
There's an analysis about apparently same problem: https://unix.stackexchange.com/questions/457692/does-ssh-proxyjump-require-local-shell-access They mention, that setting the "SHELL" variable is sufficient ..
I will further investigate if this is really required and will report back in this list. @Falko: since you got it working without changes, is a shell set for the "backuppc" user?
Yes, it's /bin/sh or /bin/bash. Greetings, Falko _______________________________________________ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List: https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki: http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
