PVE 9.0.6 failed to join the cluster

[Sh_Cby]

proxmox-ve: 9.0.0 (running kernel: 6.14.11-1-pve)
pve-manager: 9.0.6 (running version: 9.0.6/49c767b70aeb6648)
proxmox-kernel-helper: 9.0.4
proxmox-kernel-6.14.11-1-pve-signed: 6.14.11-1
proxmox-kernel-6.14: 6.14.11-1
proxmox-kernel-6.14.8-2-pve-signed: 6.14.8-2
proxmox-kernel-6.8.12-13-pve-signed: 6.8.12-13
proxmox-kernel-6.8: 6.8.12-13
proxmox-kernel-6.8.12-11-pve-signed: 6.8.12-11
proxmox-kernel-6.8.12-10-pve-signed: 6.8.12-10
proxmox-kernel-6.8.4-2-pve-signed: 6.8.4-2
ceph-fuse: 19.2.3-pve1
corosync: 3.1.9-pve2
criu: 4.1.1-1
frr-pythontools: 10.3.1-1+pve4
ifupdown2: 3.3.0-1+pmx10
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-5
libproxmox-acme-perl: 1.7.0
libproxmox-backup-qemu0: 2.0.1
libproxmox-rs-perl: 0.4.1
libpve-access-control: 9.0.3
libpve-apiclient-perl: 3.4.0
libpve-cluster-api-perl: 9.0.6
libpve-cluster-perl: 9.0.6
libpve-common-perl: 9.0.9
libpve-guest-common-perl: 6.0.2
libpve-http-server-perl: 6.0.4
libpve-network-perl: 1.1.6
libpve-rs-perl: 0.10.10
libpve-storage-perl: 9.0.13
libspice-server1: 0.15.2-1+b1
lvm2: 2.03.31-2+pmx1
lxc-pve: 6.0.4-2
lxcfs: 6.0.4-pve1
novnc-pve: 1.6.0-3
proxmox-backup-client: 4.0.14-1
proxmox-backup-file-restore: 4.0.14-1
proxmox-backup-restore-image: 1.0.0
proxmox-firewall: 1.1.2
proxmox-kernel-helper: 9.0.4
proxmox-mail-forward: 1.0.2
proxmox-mini-journalreader: 1.6
proxmox-offline-mirror-helper: 0.7.1
proxmox-widget-toolkit: 5.0.5
pve-cluster: 9.0.6
pve-container: 6.0.9
pve-docs: 9.0.8
pve-edk2-firmware: 4.2025.02-4
pve-esxi-import-tools: 1.0.1
pve-firewall: 6.0.3
pve-firmware: 3.16-4
pve-ha-manager: 5.0.4
pve-i18n: 3.5.2
pve-qemu-kvm: 10.0.2-4
pve-xtermjs: 5.5.0-2
qemu-server: 9.0.19
smartmontools: 7.4-pve1
spiceterm: 3.4.0
swtpm: 0.8.0+pve2
vncterm: 1.9.0
zfsutils-linux: 2.3.4-pve1

Prompted during cluster joining


Establishing API connection with host '10.10.10.1'
TASK ERROR: 500 Can't connect to 10.10.10.1:8006 (SSL connect attempt failed error:0A000126:SSL routines::unexpected eof while reading)

 

[bbgeek17]

Hi @Sh_Cby ,
This is usually a network problem and you have not provided enough details to advise you further.

Is the 10.10.10.1 actually accessible from new node? What is the new nodes IP? Can you ssh between the nodes? Are MTU's consistent? Are the nodes on the same network? Are there any firewalls/routers in the middle.
In short - you need to start with basic Linux network troubleshooting.

Cheers

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

 

[Sh_Cby]

Hi @Sh_Cby ,
This is usually a network problem and you have not provided enough details to advise you further.

Is the 10.10.10.1 actually accessible from new node? What is the new nodes IP? Can you ssh between the nodes? Are MTU's consistent? Are the nodes on the same network? Are there any firewalls/routers in the middle.
In short - you need to start with basic Linux network troubleshooting.

Cheers

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

Hello bbgeek17! 10.10.10.1 has joined a large cluster, and I’ve set 10.10.10.1 as the cluster host. The new node’s IP is 10.10.10.5. I can’t SSH from 10.10.10.5 to 10.10.10.1, but there’s no firewall between them, only a core switch for connection. The MTU is 9014 for both. I’m considering switching the network card or switch and reinstalling the system to try and resolve it.

 

[bbgeek17]

If you can’t SSH between the hosts, you won’t be able to perform a Join either. Whether replacing the network card or switch will help, I can’t say. I also don’t think reinstalling the OS would be tremendously useful.

Personally, I’d start with less drastic troubleshooting steps: try ICMP pings of various sizes, run traceroutes, and double-check the configuration (MTU, switch settings, etc.).

Good luck.

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox