tls_process_server_certificate: certificate verify failed (596)

[netpooyesh]

Hi
I have 4 ninety
Unfortunately, one of the nodes had a problem today and gives the following error
tls_process_server_certificate: certificate verify failed (596)
I deleted the node and wanted to add it again, but it still gives the same error

I have a proxmox server that I connected to the same server with the sftp command that has a problem, which after connecting this problem...

please help

 

[Moayad]

Hi,

Please try to restart pveproxy and pvestatd services on the node that give you error tls_process_server_certificate: certificate verify failed (596) then try again!

make sure also all nodes should be same PVE version

 

[netpooyesh]

Hi, I have restarted the services several times, but unfortunately it is a problem
Unfortunately, there are two servers in the ovh data center that I created with my template datacenter.
And I created the rest of the servers with the latest ISO on the site
And the other case I tested is multicast is not active and the connection is with Unicast

 

[Moayad]

Did you following this guide?

Please also check your syslog for any error.

 

[netpooyesh]

Hi
My problem was solved
Only I changed the corosync.conf file
The change is as follows

totem { cluster_name: net2net config_version: 1 interface { linknumber: 0 } ip_version: ipv4-6 link_mode: passive secauth: on version: 2 }

I changed as follows

totem { cluster_name: net2net config_version: 1 interface { ringnumber: 0 knet_transport: sctp } ip_version: ipv4-6 secauth: on version: 2 token: 10000 }


Wouldn't that be a problem for me in the future?

 

[Moayad]

Hi,

Wouldn't that be a problem for me in the future?

not sure, keep checking to your cluster if still healthy until tomorrow, if you got the error again please send the output of journalctl as attach:

journalctl -u corosync -u pve-cluster -b

 

[netpooyesh]

journalctl -u corosync -u pve-cluster -b

Everything works well and there are no problems
I attached the log of the above command
Is there a problem?

 

[srslol]

This ended up working for me too! Adding Token:10000!

 

[Dragoon]

Tested on the following proxmox versions

proxmox version 5.4-6 Works and provisions accounts with latest whmcs and modulegarden module.

proxmox version 5.4-15
Doesn't work same error Order Accept Encountered Problems
Tls_process_server_certificate: certificate verify failed

proxmox version 6.4-13
Doesn't work same error Order Accept Encountered Problems
Tls_process_server_certificate: certificate verify failed

Latest proxmox version 7.1-10 also fails
Doesn't work same error Order Accept Encountered Problems
Tls_process_server_certificate: certificate verify failed

Latest node


root@host-03:~# pveversion --V
proxmox-ve: 7.1-1 (running kernel: 5.13.19-5-pve)
pve-manager: 7.1-10 (running version: 7.1-10/6ddebafe)
pve-kernel-helper: 7.1-12
pve-kernel-5.13: 7.1-9
pve-kernel-5.4: 6.4-13
pve-kernel-5.13.19-6-pve: 5.13.19-14
pve-kernel-5.13.19-5-pve: 5.13.19-13
pve-kernel-5.4.166-1-pve: 5.4.166-1
pve-kernel-4.15: 5.4-19
pve-kernel-4.15.18-30-pve: 4.15.18-58
pve-kernel-4.15.18-12-pve: 4.15.18-36
ceph-fuse: 14.2.21-1
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown: 0.8.36+pve1
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.22-pve2
libproxmox-acme-perl: 1.4.1
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.1-6
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.1-3
libpve-guest-common-perl: 4.1-1
libpve-http-server-perl: 4.1-1
libpve-storage-perl: 7.1-1
libqb0: 1.0.5-1
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.11-1
lxcfs: 4.0.11-pve1
novnc-pve: 1.3.0-2
proxmox-backup-client: 2.1.5-1
proxmox-backup-file-restore: 2.1.5-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.4-7
pve-cluster: 7.1-3
pve-container: 4.1-4
pve-docs: 7.1-2
pve-edk2-firmware: 3.20210831-2
pve-firewall: 4.2-5
pve-firmware: 3.3-5
pve-ha-manager: 3.3-3
pve-i18n: 2.6-2
pve-qemu-kvm: 6.1.1-2
pve-xtermjs: 4.16.0-1
qemu-server: 7.1-4
smartmontools: 7.2-pve2
spiceterm: 3.2-2
swtpm: 0.7.1~bpo11+1
vncterm: 1.7-1
zfsutils-linux: 2.1.2-pve1


Please help resolve this issue as we are not able to provision now with the latest module and versions.

Systems are stand alone nothing is setup in clusters so no corosync.conf file to adjust.

 

[rolandkim.amaro]

I also encountered this error. What is the path to locate corosnyc.conf to edit it too, and is it for each nodes or only for the nodes has an error? Thanks for somone who help me.

 

[rolandkim.amaro]

Hi
My problem was solved
Only I changed the corosync.conf file
The change is as follows

totem { cluster_name: net2net config_version: 1 interface { linknumber: 0 } ip_version: ipv4-6 link_mode: passive secauth: on version: 2 }

I changed as follows

totem { cluster_name: net2net config_version: 1 interface { ringnumber: 0 knet_transport: sctp } ip_version: ipv4-6 secauth: on version: 2 token: 10000 }


Wouldn't that be a problem for me in the future?

I also encountered this error. What is the path to locate corosnyc.conf to edit it too, and is it for each nodes or only for the nodes has an error? Thanks for somone who help me.

 

[BitMage]

I also encountered this error. What is the path to locate corosnyc.conf to edit it too, and is it for each nodes or only for the nodes has an error? Thanks for somone who help me.

For clustered servers, there are two corosync files. See https://pve.proxmox.com/pve-docs/pve-admin-guide.html#_corosync_configuration

 

[SoporteIB]

Hi.
I have a cluster with two nodes but when I try to add a third node, to later upgrade Proxmox 6 to 7, I get this error listed here: tls_process_server_certificate: certificate verify failed (596)
I have tried this solution without success. Can you help me?

 

[Hyacin]

Got this, tried many fixes, no luck.

Reading something about addresses and hostnames and /etc/pve/nodes made a lightbulb go off in my head ...

When I installed my newest host I named it t5810-03 by accident, not paying attention (my other t5810 servers are named T5810-01 and T5810-02) - I thought I could quickly fix it by changing /etc/hostname ... nope ...

Changing the contents of /etc/hostname ... even just from a lower case t to an upper case T, gave me this error, and I couldn't talk to the node at all via the web interface. Changing it back resolved the issue!!