unable to add node to cluster after update

Frosty1

New Member
Nov 23, 2025
2
0
1
Hello,
I have searched forums for resolution, but haven't found solution.

Problem: unable to add node to cluster after update.

Situation: update to one of the nodes in cluster changed kernel to 6.17 and network services no longer functioned on node (node 2 in cluster); node 1 on cluster functioning fine. Node 2 is older hardware with legacy BIOS. Searched forums and found issue with 6.17 and recommendation to pin to different kernel. RESOLVED the network issue using proxmox-boot-tool and pinning to kernel 6.14. Node functions in standalone mode.

However, when trying to join cluster, get eroor that host can't be resolved.
Prior to joining:
- cleared node2 of all VM/LXC (clean build /w updates and kernel pinned).
- both nodes running pve 9.1.1 manager
- both nodes can ping eachother and router
- can ssh into both nodes
- verified /etc/pve/nodes only has "local" node
- corosync.conf file doesn't have duplicate nodes and is created when cluster is started.
- verified /etc/hosts file has correct local host entry on each node (pve1 xxx.xxx.xx.5 or pve2 xxx.xxx.xx.6):
127.0.0.1 localhost.localdomain localhost
192.168.86.5 pve1.lan pve1

Both nodes will function in standalone, but can't add node 2 to node 1 without getting error.
TASK ERROR: 500 Can't connect to xx.xx.xx.xxx:8006
'/etc/pve/nodes/pve-c2/pve-ssl.pem' does not exist! (500)

Have tried 'pvecm updatecerts' on both nodes, but that hasn't worked.


Have been testing a 2 node cluster for a few months. Was able to update both nodes to pve9 (with some hiccups). Have been through failed to join cluster errors before, but can't resolve this one.

any help is approcieated
Thank you
 
so add/ change your network-interface-name on this server, to the right one and restart the network service.
 
so add/ change your network-interface-name on this server, to the right one and restart the network service.
Thanks, but not sure what you are suggesting I change. The interfaces look correct. Here is output from network config on the two "standalone" servers:
Code:
root@lilo:~# cat /etc/network/interfaces
auto lo
iface lo inet loopback

iface enp3s0 inet manual

auto vmbr0
iface vmbr0 inet static
    address 192.168.86.5/24
    gateway 192.168.86.1
    bridge-ports enp3s0
    bridge-stp off
    bridge-fd 0

source /etc/network/interfaces.d/*

root@lilo:~# cat /etc/hosts
127.0.0.1 localhost.localdomain localhost
192.168.86.5 lilo.lan lilo

Code:
root@stitch:~# cat /etc/network/interfaces
auto lo
iface lo inet loopback

iface enp0s10 inet manual

auto vmbr0
iface vmbr0 inet static
    address 192.168.86.7/24
    gateway 192.168.86.1
    bridge-ports enp0s10
    bridge-stp off
    bridge-fd 0

source /etc/network/interfaces.d/*

root@stitch:~# cat /etc/hosts
127.0.0.1 localhost.localdomain localhost
192.168.86.7 stitch.lan stitch