error fetching datastores - fingerprint '82:01...:BE:C0' not verified after adding SSDs

U

ultima

Member
Apr 9, 2021
13
4
8
74
I have added an SSD mirror as boot volume to my Proxmox server. Unfortunately I was forced to do a fresh install but the previous rpool, now renamed to lpool, is still available and is the backup target. I succeeded in resurrecting all CTs and VMs.

There's a problem with PBS that I can't solve: the PVE GUI shows a question mark next to the PBS storage called PBS-1. When I click on it, I get the following error:
Code: 
error fetching datastores - fingerprint '82:01:37:C7:18:53:44:F7:98:1A:94:92:66:83:F2:3C:E1:09:A2:C4:60:7D:9F:29:97:78:34:3A:DF:BA:BE:C0' not verified, abort! (500)
I have carefully checked that the fingerprint shown in the PBS server is identical to the one shown in /etc/pve/storage.cfg on the host. Additional info: I have 2 servers, ultima & nea. Each have a PBS server running on a VM. PBS-0 is a VM on nea and backs up nea to ultima while PBS-1 is a VM on ultima and backs up ultima to nea.

Ultima is the system that had the SSDs added. The backup of ultima to nea is running fine but not the other way around. Any help will be appreciated as I'm completely stuck.
 
Hi,
did you perform any changes to the certificates recently? Try to disable the PBS storage in the PVE web ui and re-enabling it. Also double check the configured fingerprint once again with the output you get from proxmox-backup-manager cert info executed on the PBS.
 
Chris said:
Hi,
did you perform any changes to the certificates recently? Try to disable the PBS storage in the PVE web ui and re-enabling it. Also double check the configured fingerprint once again with the output you get from proxmox-backup-manager cert info executed on the PBS.
Click to expand...
Thanks for replying. I'm using a strictly standard PBS install and am not using my own certificate. I did perform a fresh install on newly installed SSDs. How do I disable the PBS storage in the PVE web ui and re-enable it? Do you mean remove the storage and add it again? Will that not impact my data?
 
What version of proxmox-backup-server are you running, there was this issue related to certificates, which has been fixed with v3.2.0-1.
 
ultima said:
How do I disable the PBS storage in the PVE web ui and re-enable it? Do you mean remove the storage and add it again? Will that not impact my data?
Click to expand...
You can do so by going to Datacenter > Storage > <select-your-storage> > Edit.

Also please try to restart the PBS services by running systemctl restart proxmox-backup-proxy.service proxmox-backup.service on the PBS host. Other users with similar issues have reported that their issue disappeared after a reboot, so somewhere there might be a not up to data fingerprint floating around. Is this host part of a cluster or a standalone node? What is the current output of proxmox-backup-manager cert info?
 
Chris said:
You can do so by going to Datacenter > Storage > <select-your-storage> > Edit.

Also please try to restart the PBS services by running systemctl restart proxmox-backup-proxy.service proxmox-backup.service on the PBS host. Other users with similar issues have reported that their issue disappeared after a reboot, so somewhere there might be a not up to data fingerprint floating around. Is this host part of a cluster or a standalone node? What is the current output of proxmox-backup-manager cert info?
Click to expand...
Before addressing your questions I'd like to note that I've tried everything I could think of to assign a new fingerprint to the PBS server and always had to conclude that for unknown reasons the system insisted to verify the wrong fingerprint, i.e. the fingerprint of my other PBS instance on another host.

The PBS instance is no longer available to me so I can't execute new commands but here are a few snippets of commands I did execute:
Code: 
1. root@nea[~] pvesm add pbs PBS-1 --server PBS-1 --datastore nea --fingerprint 7c:59:00:7a:82:b4:97:f1:92:45:88:fe:ed:b6:e0:f1:69:05:6c:95:84:00:2b:6d:71:03:93:33:32:90:2f:30 --username root@pam
create storage failed: PBS-1: error fetching datastores - fingerprint '82:01:37:C7:18:53:44:F7:98:1A:94:92:66:83:F2:3C:E1:09:A2:C4:60:7D:9F:29:97:78:34:3A:DF:BA:BE:C0' not verified, abort!
2. Here's a snippet from the nea log:
root@nea[~] journalctl -u pvestatd|tail -200
Oct 31 19:37:43 nea pvestatd[1726533]: status update time (6.453 seconds)
Oct 31 19:37:46 nea pvestatd[1726533]: mount error: mount.nfs: access denied by server while mounting nea:/lpool/backup/ultima/pve
Oct 31 19:37:52 nea pvestatd[1726533]: PBS-1: error fetching datastores - fingerprint '82:01:37:C7:18:53:44:F7:98:1A:94:92:66:83:F2:3C:E1:09:A2:C4:60:7D:9F:29:97:78:34:3A:DF:BA:BE:C0' not verified, abort!
3. and for PBS-1:
Oct 31 19:46:32 PBS-1 proxmox-backup-proxy[952]: authentication failure; rhost=[::ffff:192.168.178.200]:57122 msg=no authentication credentials provided.
Oct 31 19:46:35 PBS-1 proxmox-backup-proxy[952]: GET /api2/json/admin/datastore: 401 Unauthorized: [client [::ffff:192.168.178.200]:57122] authentication failed - no authentication credentials provided.

I can provide more if required.
 
ultima said:
Before addressing your questions I'd like to note that I've tried everything I could think of to assign a new fingerprint to the PBS server and always had to conclude that for unknown reasons the system insisted to verify the wrong fingerprint, i.e. the fingerprint of my other PBS instance on another host.
Click to expand...
Are you sure your storage is trying to connect to the correct PBS instance?
 
You must log in or register to reply here.
Top Bottom