() Error: wrong signature in manifest

M

MG_100

Active Member
Oct 31, 2020
43
3
28
24
Hallo,
Ich wollte heute eine VM zurückspielen von einem Backup und bekam folgende Meldung:

Code: 
Error: wrong signature in manifest
TASK ERROR: command '/usr/bin/proxmox-backup-client restore '--crypt-mode=encrypt' '--keyfd=12' vm/1111/2020-11-14T04:00:02Z index.json /var/tmp/vzdumptmp2738998/index.json --repository backups@pbs@45.135.149.91:atomic' failed: exit code 255

pveversion -v on the vm host:

Code: 
proxmox-ve: 6.2-2 (running kernel: 5.4.60-1-pve)
pve-manager: 6.2-15 (running version: 6.2-15/48bd51b6)
pve-kernel-5.4: 6.3-1
pve-kernel-helper: 6.3-1
pve-kernel-5.4.73-1-pve: 5.4.73-1
pve-kernel-5.4.65-1-pve: 5.4.65-1
pve-kernel-5.4.60-1-pve: 5.4.60-2
ceph: 14.2.11-pve1
ceph-fuse: 14.2.11-pve1
corosync: 3.0.4-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35+pve1
libjs-extjs: 6.0.1-10
libknet1: 1.16-pve1
libproxmox-acme-perl: 1.0.5
libpve-access-control: 6.1-3
libpve-apiclient-perl: 3.0-3
libpve-common-perl: 6.2-4
libpve-guest-common-perl: 3.1-3
libpve-http-server-perl: 3.0-6
libpve-storage-perl: 6.2-10
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.3-1
lxcfs: 4.0.3-pve3
novnc-pve: 1.1.0-1
proxmox-backup-client: 1.0.1-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.3-10
pve-cluster: 6.2-1
pve-container: 3.2-3
pve-docs: 6.2-6
pve-edk2-firmware: 2.20200531-1
pve-firewall: 4.1-3
pve-firmware: 3.1-3
pve-ha-manager: 3.1-1
pve-i18n: 2.2-2
pve-qemu-kvm: 5.1.0-6
pve-xtermjs: 4.7.0-2
qemu-server: 6.2-20
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-2
zfsutils-linux: 0.8.5-pve1
 
i would guess that it is one of the following things:

* the backup is corrupt (specifically the index)
* you're using a wrong or broken key to check the signature

did you change the key in the past? if yes, there is a mismatch and the signature check will not work
 
did you change the key in the past? if yes, there is a mismatch and the signature check will not work
Click to expand...
Is there a option to skip the signature verfication?
 
no. and if the key is the wrong one, that would not help anyway since you couldn't decrypt any of the chunks..
 
but in my fall is the right key, why i have changed nothing.
How can that happen?
 
was this backup done using a very very old version of PBS? there has been one breaking change w.r.t. signature calculcation way back in the beta. you can build the client with disabled signature checks for the manifest and try restoring with that:

https://git.proxmox.com/?p=proxmox-...43485f850ee9076e1c14f4c95847b08c;hb=HEAD#l241

but like I said, it's very likely you got your keys mixed up. the parts of the manifest that are covered by the signature are only ever written once - during the backup.
 
You must log in or register to reply here.
Top Bottom