problems

[OptimusGREEN]

Hi,

I like the concept of this tool so kudos, but unfortunately I cant get it to work with an ssh key.

so when i add the ssh key under my server config either by upload or paste it says unknown key below

I've tried this with ed and rsa, now with the ed, the test connection button failed but it passes with the rsa.

I've can also ssh from the container to my node with the key no problem.

When I try to install one of the scripts I get an error.

[6:45:17 PM] [START] Starting SSH execution of scripts/ct/teamspeak-server.sh on Monzter PVE (192.168.1.210)
[6:45:17 PM] [ERROR] Warning: Permanently added '192.168.1.210' (ED25519) to the list of known hosts.

[6:45:18 PM] [ERROR] Load key "/tmp/ssh-key-OEE5H3/private_key": error in libcrypto
[email protected]: Permission denied (publickey).

[6:45:18 PM] [ERROR] rsync: connection unexpectedly closed (0 bytes received so far) [sender]

[6:45:18 PM] [ERROR] rsync error: unexplained error (code 255) at io.c(232) [sender=3.4.1]

[6:45:18 PM] [ERROR] SSH execution failed: rsync failed with code 255
[6:45:18 PM] [ERROR] Failed to start SSH execution: rsync failed with code 255

Another issue I am seeing is that when I scan for existing containers with the community-scripts tag it doesn't find any, even though I have a few.

I've just updated to the latest version so any help would be appreciated.

[michelroegl-brunner]

Can you try and connect to your host with a password? It worked for me to just upload the private key file.

The other issues are related to the ssh issue. neither the Script detection nor execution will work without ssh.

[OptimusGREEN]

Thanks for the reply.

it all works fine with password but as soon as i switch back to key only, the same issue returns.

[OptimusGREEN]

heres pve auth log while trying to connect with the key

Oct 13 20:57:52 monzter-pve sshd[3842509]: Server listening on 0.0.0.0 port 22.
Oct 13 20:57:52 monzter-pve sshd[3842509]: debug1: Bind to port 22 on ::.
Oct 13 20:57:52 monzter-pve sshd[3842509]: Server listening on :: port 22.
Oct 13 20:58:04 monzter-pve sshd[3842509]: debug1: Forked child 3887649.
Oct 13 20:58:04 monzter-pve sshd[3887649]: debug1: Set /proc/self/oom_score_adj to 0
Oct 13 20:58:04 monzter-pve sshd[3887649]: debug1: rexec start in 5 out 5 newsock 5 pipe 7 sock 8
Oct 13 20:58:04 monzter-pve sshd[3887649]: debug1: inetd sockets after dupping: 4, 4
Oct 13 20:58:04 monzter-pve sshd[3887649]: Connection from 192.168.1.122 port 44924 on 192.168.1.210 port 22 rdomain ""
Oct 13 20:58:04 monzter-pve sshd[3887649]: debug1: Local version string SSH-2.0-OpenSSH_9.2p1 Debian-2+deb12u7
Oct 13 20:58:04 monzter-pve sshd[3887649]: debug1: Remote protocol version 2.0, remote software version OpenSSH_10.0p2 Debian-7
Oct 13 20:58:04 monzter-pve sshd[3887649]: debug1: compat_banner: match: OpenSSH_10.0p2 Debian-7 pat OpenSSH* compat 0x04000000
Oct 13 20:58:04 monzter-pve sshd[3887649]: debug1: permanently_set_uid: 102/65534 [preauth]
Oct 13 20:58:04 monzter-pve sshd[3887649]: debug1: list_hostkey_types: rsa-sha2-512,rsa-sha2-256,ecdsa-sha2-nistp256,ssh-ed25519 [preauth]
Oct 13 20:58:04 monzter-pve sshd[3887649]: debug1: SSH2_MSG_KEXINIT sent [preauth]
Oct 13 20:58:04 monzter-pve sshd[3887649]: debug1: SSH2_MSG_KEXINIT received [preauth]
Oct 13 20:58:04 monzter-pve sshd[3887649]: debug1: kex: algorithm: sntrup761x25519-sha512 [preauth]
Oct 13 20:58:04 monzter-pve sshd[3887649]: debug1: kex: host key algorithm: ssh-ed25519 [preauth]
Oct 13 20:58:04 monzter-pve sshd[3887649]: debug1: kex: client->server cipher: [email protected] MAC: <implicit> compression: none [preauth]
Oct 13 20:58:04 monzter-pve sshd[3887649]: debug1: kex: server->client cipher: [email protected] MAC: <implicit> compression: none [preauth]
Oct 13 20:58:04 monzter-pve sshd[3887649]: debug1: expecting SSH2_MSG_KEX_ECDH_INIT [preauth]
Oct 13 20:58:04 monzter-pve sshd[3887649]: debug1: SSH2_MSG_KEX_ECDH_INIT received [preauth]
Oct 13 20:58:04 monzter-pve sshd[3887649]: debug1: ssh_packet_send2_wrapped: resetting send seqnr 3 [preauth]
Oct 13 20:58:04 monzter-pve sshd[3887649]: debug1: rekey out after 134217728 blocks [preauth]
Oct 13 20:58:04 monzter-pve sshd[3887649]: debug1: SSH2_MSG_NEWKEYS sent [preauth]
Oct 13 20:58:04 monzter-pve sshd[3887649]: debug1: Sending SSH2_MSG_EXT_INFO [preauth]
Oct 13 20:58:04 monzter-pve sshd[3887649]: debug1: expecting SSH2_MSG_NEWKEYS [preauth]
Oct 13 20:58:04 monzter-pve sshd[3887649]: debug1: ssh_packet_read_poll2: resetting read seqnr 3 [preauth]
Oct 13 20:58:04 monzter-pve sshd[3887649]: debug1: SSH2_MSG_NEWKEYS received [preauth]
Oct 13 20:58:04 monzter-pve sshd[3887649]: debug1: rekey in after 134217728 blocks [preauth]
Oct 13 20:58:04 monzter-pve sshd[3887649]: debug1: KEX done [preauth]
Oct 13 20:58:04 monzter-pve sshd[3887649]: debug1: userauth-request for user root service ssh-connection method none [preauth]
Oct 13 20:58:04 monzter-pve sshd[3887649]: debug1: attempt 0 failures 0 [preauth]
Oct 13 20:58:04 monzter-pve sshd[3887649]: debug1: PAM: initializing for "root"
Oct 13 20:58:04 monzter-pve sshd[3887649]: debug1: PAM: setting PAM_RHOST to "192.168.1.122"
Oct 13 20:58:04 monzter-pve sshd[3887649]: debug1: PAM: setting PAM_TTY to "ssh"
Oct 13 20:58:04 monzter-pve sshd[3887649]: Connection closed by authenticating user root 192.168.1.122 port 44924 [preauth]
Oct 13 20:58:04 monzter-pve sshd[3887649]: debug1: do_cleanup [preauth]
Oct 13 20:58:04 monzter-pve sshd[3887649]: debug1: monitor_read_log: child log fd closed
Oct 13 20:58:04 monzter-pve sshd[3887649]: debug1: do_cleanup
Oct 13 20:58:04 monzter-pve sshd[3887649]: debug1: PAM: cleanup
Oct 13 20:58:04 monzter-pve sshd[3887649]: debug1: Killing privsep child 3887650
Oct 13 20:58:04 monzter-pve sshd[3887649]: debug1: audit_event: unhandled event 12

here is warp agents take on it.

Found the Problem!

Based on the debug logs I captured, here's exactly what's happening:

The Issue: Client Disconnects After "method none"

Looking at the logs, the SSH handshake progresses normally through:
1. ✅ Connection established
2. ✅ Protocol version exchange 
3. ✅ Key exchange (KEX) completed successfully
4. ✅ Encryption established

But then:
•  Client sends: userauth-request for user root service ssh-connection method none
•  Immediately after: Connection closed by authenticating user root 192.168.1.122

Root Cause: SSH Client Configuration Issue

The client is using method none for authentication instead of publickey. This suggests:

1. BatchMode Issue: You used -o BatchMode=yes which prevents interactive authentication, but the client can't find or use the SSH key properly.
2. No Valid SSH Key Available: The SSH client on 192.168.1.122 either:
◦  Can't find any SSH private keys
◦  The available private keys don't match any public keys in the server's authorized_keys
◦  SSH agent isn't running or doesn't have the key loaded

the public key has defo been added to pve authorized_keys file.

hope this helps.

[michelroegl-brunner]

Thank you for the verbose logs, i look at it tommorow.

[michelroegl-brunner]

There was a issue with how i store copied ssh keys, this should be fixed in 0.4.1 (releases later today)

[OptimusGREEN]

super. thanks.

[OptimusGREEN]

Hi,

Unfortunately 0.4.1 has the same behaviour. can't log in using a key.

[michelroegl-brunner]

ok, thank you. I try to break it on my system tomorow to find that bug.

[michelroegl-brunner]

yes, no passphrase for the private key

one last question. wich option did you choose? Ssh key or ssh key combiend with password?

[OptimusGREEN]

ive tried both but obly the password ever works when I enable it on my node. as soon as I turn password off on the node then it can't connect.

[michelroegl-brunner]

I guess i found the error. Please update and try again with your keys. I also added the option to add a key pair directly, please try that as well when you key dose not work. Delete your existing servers and create them new please.

[OptimusGREEN]

Well done mate, problem solved. thank you