pmgcm update-finge: 401 permission denied - invalid PMG ticket

kleber.unixer

Member
Aug 3, 2020
10
1
8
46
After updating a expired certificate my cluster started to show an error.
I already tried to change the figerprint in the /etc/pmg/cluster.conf file and run pmgcm update-fingerprints but nothing seems to solve:

pmgcm update-fingerprints
401 permission denied - invalid PMG ticket

NAME (CID) -------------- IPADDRESS ---- ROLE-STATE --------- UPTIME --- LOAD ---- MEM --- DISK
mx003deb10 (2) 192.168.X.XXX node ERROR: 401 permission denied - invalid PMG ticket - - -% -%
mx002deb10 (1) 192.168.X.XXX master A 00:30 2.77 22% 61%
The journalctl -u pmgmirror output on the master node does not have an error but on node 1 it does:
Apr 30 22:15:58 XXXXXX pmgmirror [1170]: database sync 'XXXXX' failed - 401 permission denied - invalid PMG ticket
Apr 30 22:16:00 mx003deb10 pmgmirror [1170]: cluster synchronization finished (1 errors, 6.70 seconds (files 0.00, database 6.36, config 0.35))

database sync 'xxxxxxxxxx' failed - fingerprint 'B0: 2F: 98: 12: 6F: 27: AB: 92: B7: 14: A8: 20: EB: CD: 8F: 1B: 96: 1A: 94: FC: 3C : 62: 2E: 44: CE: 88: A5: CE: 50: D1: D6: 9D 'not verified, abort!

Can anyone tell me what's missing?
 
* are the clocks on both systems in sync?
* compare the api-key on both nodes (don't post it here since it is senstive data) (/etc/pmg/pmg-authkey.key and /etc/pmg/pmg-authkey.pub)

I hope this helps!
 

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!