Search results

the password is only handled when creating a new container, but this could also be extended to work when restoring. could you file an issue in our bugzilla? https://bugzilla.proxmox.com/show_bug.cgi?id=7158 is tangentially related..

understood. if you do run into this issue more often, I would recommend switching to 6.14 - please report back if the problem goes away then! so far we've only had reports of the issue triggering with PBS connections.

das ist ja schonmal gut! die fehlermeldung klingt tatsaechlich nach einem einfachen verbindungsabbruch.. wieviel platz hast du denn auf PBS seite? eventuell kannst du dort lokal restoren und anderweitig transferieren, falls das netzwerk problem sich nicht loesen laesst..

qemu-server 9.1.3 available on pve-test now should fix this issue. affected VMs do need to be stopped and started (or live-migrated *outside of a node reboot/shutdown!) for the fix to take affect.

die fehlermeldung besagt nur dass das enterprise repository konfiguriert ist, aber keine subscription aktiv. siehe doku ;)

qemu-server 9.1.3 available on pve-test now should fix this issue. affected VMs do need to be stopped and started (or live-migrated *outside of a node reboot/shutdown!) for the fix to take affect.

qemu-server 9.1.3 available on pve-test now should fix this issue. affected VMs do need to be stopped and started (or live-migrated *outside of a node reboot/shutdown!) for the fix to take affect.

qemu-server 9.1.3 available on pve-test now should fix this issue. affected VMs do need to be stopped and started (or live-migrated *outside of a node reboot/shutdown!) for the fix to take affect.

qemu-server 9.1.3 available on pve-test now should fix this issue. affected VMs do need to be stopped and started (or live-migrated *outside of a node reboot/shutdown!) for the fix to take affect.

bitte repositories einschalten, "apt update" machen und den output hier posten (in code tags)

wie vermutet - du hast die Debian repositories disabled.. bitte die doku lesen!

I think originally the reasoning was that it's not useful for the client to store that information. that it doesn't render correctly for you seems strange and likely a bug, for me it does render correctly. what does "pvesh get /cluster/acme/account/test-LEv2 --output-format json-pretty" print?

bitte mal "grep '.*' /etc/apt/sources.list /etc/apt/sources.list.d/*" machen

the information is stripped when storing, yes. the contact field is not used by the ACME client, but by the CA. you can always get the account info from the CA using the key, which is stored.

@LKo could you try to trigger the issue with "proxmox-backup-client benchmark --repository ..." ? that will (after doing a little exercise for your CPU) upload a stream of fake chunks for 5s and wait until they are all processed. if you can reproduce it using that (e.g., in a loop until it...

bitte kontrollier deine repository einstellungen, vermutlich fehlt da was.

ist der snapshot auf PBS seite verified? ist irgendwas im PBS seitigen "reader" task log oder journal zu sehen?

does your migration network use MTU 9000? are you on the (default) 6.17 kernel? if the answer to both is yes, could you try booting into the 6.14 kernel and see if the problem goes away in that case?

@fseeseink do you also use ZFS?

should be fixed in pve-manager 9.1.3