September 8, 20241 yr I'm a noob at using the command line but I'm trying to setup LuckyBackup to connect my two Unraid servers (6.12.13) using the article from SPX Labs. I get to the point of transferring my SSH public key to the destination server, which it accepts as a new known host but then it won't accept the password. I've also tried using rsync in it's normal commands but likewise it seems to accept the IP of the destination machine but repeatedly asks for the password. While I've primarily been using the destination root password I've tried all others on the off chance that I was mistaken on what p/w it's looking for. Password does work logging into the destination server but I can't get there by command line. Any suggestions?
September 8, 20241 yr Author Additional info, I've just noticed that while SSH is active in Settings/Management Access, I do not have a SSH icon in Network Services on my destination server although there is one on my source server. I've been unable to find how to install it on the destination. Attached is my current Diagnostics file.defiant-diagnostics-20240908-1840.zip
September 9, 20241 yr Community Expert If I understand correctly the issue is that you cannot login via SSH? Post the output from: ssh -v server_IP
September 9, 20241 yr Author root@Intrepid:~# ssh -v 192.168.1.241 OpenSSH_9.8p1, OpenSSL 1.1.1v 1 Aug 2023 debug1: Reading configuration data /etc/ssh/ssh_config debug1: Authenticator provider $SSH_SK_PROVIDER did not resolve; disabling debug1: Connecting to 192.168.1.241 [192.168.1.241] port 22. debug1: Connection established. debug1: identity file /root/.ssh/id_rsa type -1 debug1: identity file /root/.ssh/id_rsa-cert type -1 debug1: identity file /root/.ssh/id_ecdsa type -1 debug1: identity file /root/.ssh/id_ecdsa-cert type -1 debug1: identity file /root/.ssh/id_ecdsa_sk type -1 debug1: identity file /root/.ssh/id_ecdsa_sk-cert type -1 debug1: identity file /root/.ssh/id_ed25519 type -1 debug1: identity file /root/.ssh/id_ed25519-cert type -1 debug1: identity file /root/.ssh/id_ed25519_sk type -1 debug1: identity file /root/.ssh/id_ed25519_sk-cert type -1 debug1: identity file /root/.ssh/id_xmss type -1 debug1: identity file /root/.ssh/id_xmss-cert type -1 debug1: identity file /root/.ssh/id_dsa type -1 debug1: identity file /root/.ssh/id_dsa-cert type -1 debug1: Local version string SSH-2.0-OpenSSH_9.8 debug1: Remote protocol version 2.0, remote software version OpenSSH_9.8 debug1: compat_banner: match: OpenSSH_9.8 pat OpenSSH* compat 0x04000000 debug1: Authenticating to 192.168.1.241:22 as 'root' debug1: load_hostkeys: fopen /root/.ssh/known_hosts2: No such file or directory debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts: No such file or directory debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts2: No such file or directory debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: algorithm: [email protected] debug1: kex: host key algorithm: ssh-ed25519 debug1: kex: server->client cipher: [email protected] MAC: <implicit> compression: none debug1: kex: client->server cipher: [email protected] MAC: <implicit> compression: none debug1: expecting SSH2_MSG_KEX_ECDH_REPLY debug1: SSH2_MSG_KEX_ECDH_REPLY received debug1: Server host key: ssh-ed25519 SHA256:Rk9hBEtCeYjFFYGkSxAyxl9iyHyLzSnBsCyFWeJhuDY debug1: load_hostkeys: fopen /root/.ssh/known_hosts2: No such file or directory debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts: No such file or directory debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts2: No such file or directory debug1: Host '192.168.1.241' is known and matches the ED25519 host key. debug1: Found key in /root/.ssh/known_hosts:1 debug1: ssh_packet_send2_wrapped: resetting send seqnr 3 debug1: rekey out after 134217728 blocks debug1: SSH2_MSG_NEWKEYS sent debug1: Sending SSH2_MSG_EXT_INFO debug1: expecting SSH2_MSG_NEWKEYS debug1: ssh_packet_read_poll2: resetting read seqnr 3 debug1: SSH2_MSG_NEWKEYS received debug1: rekey in after 134217728 blocks debug1: SSH2_MSG_EXT_INFO received debug1: kex_ext_info_client_parse: server-sig-algs=<ssh-ed25519,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,[email protected],[email protected],rsa-sha2-512,rsa-sha2-256> debug1: kex_ext_info_check_ver: [email protected]=<0> debug1: kex_ext_info_check_ver: [email protected]=<0> debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: SSH2_MSG_EXT_INFO received debug1: kex_ext_info_client_parse: server-sig-algs=<ssh-ed25519,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,[email protected],[email protected],rsa-sha2-512,rsa-sha2-256> debug1: Authentications that can continue: publickey,password,keyboard-interactive debug1: Next authentication method: publickey debug1: Will attempt key: /root/.ssh/id_rsa debug1: Will attempt key: /root/.ssh/id_ecdsa debug1: Will attempt key: /root/.ssh/id_ecdsa_sk debug1: Will attempt key: /root/.ssh/id_ed25519 debug1: Will attempt key: /root/.ssh/id_ed25519_sk debug1: Will attempt key: /root/.ssh/id_xmss debug1: Will attempt key: /root/.ssh/id_dsa debug1: Trying private key: /root/.ssh/id_rsa debug1: Trying private key: /root/.ssh/id_ecdsa debug1: Trying private key: /root/.ssh/id_ecdsa_sk debug1: Trying private key: /root/.ssh/id_ed25519 debug1: Trying private key: /root/.ssh/id_ed25519_sk debug1: Trying private key: /root/.ssh/id_xmss debug1: Trying private key: /root/.ssh/id_dsa debug1: Next authentication method: keyboard-interactive ([email protected]) Password:
September 10, 20241 yr Community Expert Solution Are you using a complex root password? If yes, try temporally changing it to 123 or something like that
September 10, 20241 yr Author P/W was not overly complex, 8 character, uppercase, lowercase and numbers. However changing password worked. P/W accepted, LuckyBackup set up and first backup is underway. Doesn't make a lot of sense to me as to the why but I'm very grateful. This is the second time you've bailed me out recently. Thank you
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.