Fingerprint not verified - Abort

C

cmurrayis

Member
Apr 13, 2021
10
1
8
39
Hi Everyone,

We've been running a pair of clustered PMG for a couple years now and it's always had issues with the fingerprints becoming invalid every few weeks.

Is there a fix or known cause to this as usually I just edit the cluster configuration file and put the new fingerprints in and off it goes again for a few more weeks

1698730718403.png
 
cmurrayis said:
We've been running a pair of clustered PMG for a couple years now and it's always had issues with the fingerprints becoming invalid every few weeks.

Is there a fix or known cause to this as usually I just edit the cluster configuration file and put the new fingerprints in and off it goes again for a few more weeks
Click to expand...
Do you change your certificates that often?! - If yes - why?
If you have deployed some ACME certificate script (certbot, acme.sh,..) - this is expected - and you would just need to run
`pmgcm update-fingerprints` after getting the new certificate (or switch over to using the ACME implementation in the GUI/API, which does this for you):
https://pmg.proxmox.com/pmg-docs/pmg-admin-guide.html#sysadmin_certificate_management (section 4.6.8)

I hope this helps!
 
Stoiko Ivanov said:
Do you change your certificates that often?! - If yes - why?
If you have deployed some ACME certificate script (certbot, acme.sh,..) - this is expected - and you would just need to run
`pmgcm update-fingerprints` after getting the new certificate (or switch over to using the ACME implementation in the GUI/API, which does this for you):
https://pmg.proxmox.com/pmg-docs/pmg-admin-guide.html#sysadmin_certificate_management (section 4.6.8)

I hope this helps!
Click to expand...
We do use the ACME built in management - This happens more frequently than the 3 Month SSL renewal.
 
cmurrayis said:
This happens more frequently than the 3 Month SSL renewal.
Click to expand...
The renewal happens when the current certificate is expiring in less than 30 days, which means it will be renewed every 2 months roughly

can you share the logs of the last time you ran into the issue - from both nodes, for at least one day (24h before, and 3h after the error occurs)?
 
Hi, we got the very same issue - after manually forcing update-fingerprints it works again, yet we too see this issue basically every two months.
Which logs would be required to get to you?
 
You must log in or register to reply here.
Top Bottom