I have two PBS 3.2-2 VMs running in my 3-node cluster; pbs01 and pbs02, with three datastores; pbs01_0, pbs02_0 and pbs02_1.
Nearly all my CTs and VMs back up using various schedules to pbs02, with a sync from pbs02_1 to pbs02_0, moving the data from SSD to HDD without issues.
I back up pbs02 (VM only, not the datastores) to pbs01_0 and would like to sync that to pbs02_0, where the problem occurs.
When I try to add the sync job, I can choose pbs01, but when I try to select the datastore, there is text stating "Internal Server Error (500)..."
From the syslog:
pbs01 has recently been added, replacing another VM with the same name that was junked a few months ago. Could pbs02 hold the old fingerprint from the previous incarnation of pbs01 somewhere in its config?
A search for the error text led me to bug 5248 - I don't have the technical expertise to determine if this affects my installation so any help would be appreciated.
Nearly all my CTs and VMs back up using various schedules to pbs02, with a sync from pbs02_1 to pbs02_0, moving the data from SSD to HDD without issues.
I back up pbs02 (VM only, not the datastores) to pbs01_0 and would like to sync that to pbs02_0, where the problem occurs.
When I try to add the sync job, I can choose pbs01, but when I try to select the datastore, there is text stating "Internal Server Error (500)..."
From the syslog:
Code:
May 04 11:29:41 pbs02 proxmox-backup-proxy[650]: WARNING: certificate fingerprint does not match expected fingerprint!
May 04 11:29:41 pbs02 proxmox-backup-proxy[650]: expected: 51:5f:f6:30:e9:74:5a:63:bb:41:39:ae:b1:c4:18:f4:47:d4:83:e3:c2:91:b4:5e:4f:5b:32:65:ba:96:18:57
May 04 11:29:41 pbs02 proxmox-backup-proxy[650]: certificate validation failed - Certificate fingerprint was not confirmed.
May 04 11:29:41 pbs02 proxmox-backup-proxy[650]: GET /api2/json/config/remote/pbs01/scan: 500 Internal Server Error: [client [::ffff:re.da.ct.ed]:49313] failed to scan remote 'pbs01' - remote connection to 'pbs01.redacted' failed - error trying to connect: error:0A000086:SSL routines:tls_post_process_server_certificate:certificate verify failed:../ssl/statem/statem_clnt.c:1889:pbs01 has recently been added, replacing another VM with the same name that was junked a few months ago. Could pbs02 hold the old fingerprint from the previous incarnation of pbs01 somewhere in its config?
A search for the error text led me to bug 5248 - I don't have the technical expertise to determine if this affects my installation so any help would be appreciated.
