SSH parameters for a given replication task

mpfusion

Contributor
Joined
Jan 6, 2014
Messages
198
I have two systems, one running TrueNAS-12.0-U8 and one recently upgraded to TrueNAS-13.0-U2. This upgrade broke the PULL replication from the 12.0-U8 system (and maybe more, I don't know yet). It shows “Authentication failed.” in the GUI. SSH on the console works but the GUI seems to use different keys (TrueNAS has auto-generated dozens of connections in System/SSH Connection, so maybe there's a mixup somewhere. Strange since it has worked for years.

How I obtain the exact SSH command line the GUI uses for a given SSH replication task? This would enable me to debug this on the console.
 

Alecmascot

Guru
Joined
Mar 18, 2014
Messages
1,177
The fix is in the release notes for U2
 

mpfusion

Contributor
Joined
Jan 6, 2014
Messages
198
Ok that's why, I overlooked that. I now added

Code:
PubkeyAcceptedAlgorithms +ssh-rsa


Am I supposed to remove that line once all servers are updated to 13.0-U2? Do I need to regenerate any keys?

I'm still getting “Authentication failed”. Even after restarting the SSH server (not sure if that was necessary). So the initial question still stands.
 

Samuel Tai

Never underestimate your own stupidity
Moderator
Joined
Apr 24, 2020
Messages
5,399
This is clearly stated in the documentation. For replication, you set up:
  1. SSH Keypairs, which are the private/public keys of the server originating the replication connection. You would then need to manually add the public key to the SSH Public Key field of the destination server's root account.
  2. SSH Connections, which bind an SSH Keypair to a specific destination server.
  3. Replication Task, which then references the SSH Connection.
 

Samuel Tai

Never underestimate your own stupidity
Moderator
Joined
Apr 24, 2020
Messages
5,399
You may want to clean up all the auto-generated SSH Connections for your own sanity. Likewise any auto-generated SSH Keypairs.
 

mpfusion

Contributor
Joined
Jan 6, 2014
Messages
198
You may want to clean up all the auto-generated SSH Connections for your own sanity. Likewise any auto-generated SSH Keypairs.
Ok, I'll do that. It seems the system went haywire generating all those entries. I'll purge the list then.
 

mpfusion

Contributor
Joined
Jan 6, 2014
Messages
198
This is clearly stated in the documentation.
Is it? My questions were:

- How I obtain the exact SSH command line the GUI uses for a given SSH replication task?
- Am I supposed to remove that line (… +ssh-rsa) once all servers are updated to 13.0-U2?
- Do I need to regenerate any keys?

I don't see any of that explained in the documentation. A pointer to the doc where those questions are answered would be much appreciated.
 
Top