Join cluster fails for 4th PC (ssh?)

thomasjbs

New Member
Jan 3, 2025
5
0
1
I installed a host using a usb stick (version 8.0.x?) Then I installed 2 more with the same USB stick. Fumbled around with clusters (I support a VMware environment at work - so I have the basic idea). I installed several disk sources (Cifs, NFS) - basic resources, migrated a VM to one of the other hosts in the cluster (maybe I cloned it) - it's been a short while since I did it (the clone works too).

Then I went to install a new PC from Dell - big mistake - which doesn't support Legacy boot mode. So I downloaded the newest proxmox iso and installed it (8.3.1). It installed the host (web gui and ssh work fine) - but it will not connect to the cluster. It turns out it appears to be an SSH CLIENT issue where the new host/version will NOT ssh into the older hosts. (ALL have been upgraded to recent version - no more updates available - but it will not connect via ssh.) I can't install using the Legacy ISO - because the Dell PC won't allow it to boot - ALTHOUGH IT DID ONE TIME - the FIRST TIME. Now the Dell PC will not boot to the proxmox os it installed - nor will it boot the original USB stick - but it does boot the Newer Proxmox ISO and sinstalls without error - which is what I'm using now - Until I try to join the 4th PC to the cluster.

MY Windows PC can ssh into all 4 hosts. The older hosts can ssh into the newer host - but the newer host CANNOT ssh into any host in the cluster. I thought it might be an iptables issue but it seems like the new host is being blocked (dropped) by the older hosts. tcpdump shows NO traffic after this:

root@myhost:~# ssh -vvv root@x.y.80.150
OpenSSH_9.2p1 Debian-2+deb12u3, OpenSSL 3.0.15 3 Sep 2024
debug1: Reading configuration data /root/.ssh/config
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: include /etc/ssh/ssh_config.d/*.conf matched no files
debug1: /etc/ssh/ssh_config line 21: Applying options for *
debug2: resolve_canonicalize: hostname x.y.80.150 is address
debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts' -> '/root/.ssh/known_hosts'
debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts2' -> '/root/.ssh/known_hosts2'
debug3: ssh_connect_direct: entering
debug1: Connecting to x.y.80.150 [x.y.80.150] port 22.
debug3: set_sock_tos: set socket 3 IP_TOS 0x10
... LONG WAIT...
debug1: connect to address x.y.80.150 port 22: Connection timed out
ssh: connect to host x.y.80.150 port 22: Connection timed out

Is there a log file for proxmox/ssh? I enabled DEBUG logging - listed as AUTH - but don't see a log file for SSH on the target proxmox server.

Do All hosts use IPTABLES?
Does the newer host (8.3.1) use some other firewall?
 
Last edited:
SSH works TO the 4th server - not a cable/network connection.
It can ping google.com
Perhaps an SSH CONFIG problem?
SSH server on cluster blocking ssh on 4th PC?
IPTables dropping packets from 4th server?
SSH Key on 4th server blocked?

The specific problem is 4th Server SSH *CLIENT* is getting packets dropped - or OTHER servers - ignoring 4th PC SSH packets.
 
4th PC SSH SERVER (inbound ssh) - working perfectly fine - all PCs can connect.
4th PC SSH CLIENT (outbound ssh) - packets dropped or ignored - see sample tcpdump above
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!