Hello! I'm having an odd issue with SSH between two TrueNAS Scale systems.
I'm attempting to setup Rsync via SSH between two TrueNAS Scale systems (both running TrueNAS-SCALE-22.12.3.3). This is to serve as a remote backup, with one set to pull data from the other main server (let's say TrueNAS 2 (client) is going to pull data from TrueNAS 1 (host)). I've generated a keypair and have it on both systems, and set up relevant port forwarding. TrueNAS 1 runs with a DDNS that is both pingable by the client machine and other machines (this is how I plan to connect via SSH). The permissions for SSH on both machines for now include login as Root, allow password authentication, allow TCP port forwarding. In the shell I can 'ssh root@DDNS_Service', type in the root password and access all the files necessary. The issue is setting up the connection in Backup Credentials > SSH Connections. I have tried a few things.
Trying Semi-Automatic (TrueNAS only) setup:
I plug in the following: TrueNAS URL: 'https://DDNS_Service', Admin: root, Password, Private Key and get the error:
[EFAULT] Unable to connect to remote system: [Errno 113] No route to host
Note: Specifying a port or not including https:// causes related errors to those things. I have also tried http.
Trying Manual setup:
Plugging in the same data with default settings otherwise except I do not include 'https://' in the host field (ie just 'DDNS_Service'), pressing the 'Discover Remote Host Key' populates valid data and saves without issue. The issue then arrives when attempting to setup the Rsync with the desired connection. Attempting to save the Rsync (populated in a pull configuration with root permissions) gives the error:
Disconnect Error[ error code 14 ] was generated when trying to communicate with remote host DDNS_Service and remote user root.
Note: Including 'https://' in the host field causes an error.
Any idea on what I'm doing wrong? It's highly possible I've missed something simple haha.
As a note I'm aware of the multiple security risks involved here but am currently just going for a minimal successful setup and will secure after. Thank you for the help!
I'm attempting to setup Rsync via SSH between two TrueNAS Scale systems (both running TrueNAS-SCALE-22.12.3.3). This is to serve as a remote backup, with one set to pull data from the other main server (let's say TrueNAS 2 (client) is going to pull data from TrueNAS 1 (host)). I've generated a keypair and have it on both systems, and set up relevant port forwarding. TrueNAS 1 runs with a DDNS that is both pingable by the client machine and other machines (this is how I plan to connect via SSH). The permissions for SSH on both machines for now include login as Root, allow password authentication, allow TCP port forwarding. In the shell I can 'ssh root@DDNS_Service', type in the root password and access all the files necessary. The issue is setting up the connection in Backup Credentials > SSH Connections. I have tried a few things.
Trying Semi-Automatic (TrueNAS only) setup:
I plug in the following: TrueNAS URL: 'https://DDNS_Service', Admin: root, Password, Private Key and get the error:
[EFAULT] Unable to connect to remote system: [Errno 113] No route to host
Note: Specifying a port or not including https:// causes related errors to those things. I have also tried http.
Trying Manual setup:
Plugging in the same data with default settings otherwise except I do not include 'https://' in the host field (ie just 'DDNS_Service'), pressing the 'Discover Remote Host Key' populates valid data and saves without issue. The issue then arrives when attempting to setup the Rsync with the desired connection. Attempting to save the Rsync (populated in a pull configuration with root permissions) gives the error:
Disconnect Error[ error code 14 ] was generated when trying to communicate with remote host DDNS_Service and remote user root.
Note: Including 'https://' in the host field causes an error.
Any idea on what I'm doing wrong? It's highly possible I've missed something simple haha.
As a note I'm aware of the multiple security risks involved here but am currently just going for a minimal successful setup and will secure after. Thank you for the help!
