[PBS - Let's Encrypt] Cannot remove Fingerprint from storage object in PVE

[Reifide]

Hi,

I have a working Proxmox Backup Server which is connected to a PVE server. Backups have been running great!

Tonight I created a Let's Encrypt certificate on my Proxmox Backup Server. Now that PBS is serving a legitimate certificate I'm under the impression that I can remove the "Fingerprint" value from the "Proxmox Backup Server" storage object in PVE.

However when i remove the fingerprint and click save the same fingerprint is still there when i click on edit again.

If I put in the PBS fingerprint everything works fine, but the fingerprint will change when the Let's Encrypt certificate renews in a few months.

Any idea why I can't remove the fingerprint? (See attached dialog window)

 

[dcsapak]

what is the output of 'pveversion -v' ?

 

[Reifide]

what is the output of 'pveversion -v' ?

Here is the output:

Linux p-sn-pve-01 5.11.22-5-pve #1 SMP PVE 5.11.22-10 (Tue, 28 Sep 2021 08:15:41 +0200) x86_64

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Thu Oct  7 11:45:10 CEST 2021 on pts/0
root@p-sn-pve-01:~# pveversion -v
proxmox-ve: 7.0-2 (running kernel: 5.11.22-5-pve)
pve-manager: 7.0-11 (running version: 7.0-11/63d82f4e)
pve-kernel-helper: 7.1-2
pve-kernel-5.11: 7.0-8
pve-kernel-5.11.22-5-pve: 5.11.22-10
pve-kernel-5.11.22-4-pve: 5.11.22-9
pve-kernel-5.11.22-1-pve: 5.11.22-2
ceph-fuse: 15.2.13-pve1
corosync: 3.1.5-pve1
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.22-pve1
libproxmox-acme-perl: 1.3.0
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.0-4
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.0-9
libpve-guest-common-perl: 4.0-2
libpve-http-server-perl: 4.0-2
libpve-storage-perl: 7.0-11
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.9-4
lxcfs: 4.0.8-pve2
novnc-pve: 1.2.0-3
proxmox-backup-client: 2.0.9-2
proxmox-backup-file-restore: 2.0.9-2
proxmox-mini-journalreader: 1.2-1
proxmox-widget-toolkit: 3.3-6
pve-cluster: 7.0-3
pve-container: 4.0-10
pve-docs: 7.0-5
pve-edk2-firmware: 3.20200531-1
pve-firewall: 4.2-3
pve-firmware: 3.3-2
pve-ha-manager: 3.3-1
pve-i18n: 2.5-1
pve-qemu-kvm: 6.0.0-4
pve-xtermjs: 4.12.0-1
qemu-server: 7.0-14
smartmontools: 7.2-1
spiceterm: 3.2-2
vncterm: 1.7-1
zfsutils-linux: 2.0.5-pve1

 

[dcsapak]

pve-manager: 7.0-11 (running version: 7.0-11/63d82f4e)

siehe https://bugzilla.proxmox.com/show_bug.cgi?id=3620

sollte gefixt sein seit pve-manager version 7.0-12

 

[Reifide]

siehe https://bugzilla.proxmox.com/show_bug.cgi?id=3620

sollte gefixt sein seit pve-manager version 7.0-12

Ok perfect, takk!