Recent content by sterzy

Thanks for the notice, I'll see if I can take another look there. Sorry for the inconvenience.

Thanks for the updates! I'll see if I can give you a more concrete answer once I found out a little about what's going on here.

Well not quite, but you can probably use pvesh to script something usable. What you'd need to do is use first get the current setting for efidisk0, you can do that via something like qm config <vmid>| grep efidisk0. Then append ms-cert=2023k to the old setting there and update the config like...

Can you post the configuration of the container? Simply run pct config <CT-ID> (replace <CT-ID> with the container's ID of course), then post the result here, ideally between tags. Thank you!

If you reboot through the UI, yes the changes should be applied. Otherwise, you will need to turn off the VM and turn it back on again. Note that this only works if you enroll the keys through the UI, the CLI command to enroll the keys requires the VM to be turned off.

The certificate expires on June 27, 2026. After that, Microsoft will no longer be able to sign shims with that certificate. Then it'll depend on how quickly Debian (and other distributions) will release new shims. However, you can simply enroll the keys for your Debian machines as soon as...

If the shim is only signed with the 2023 cert, which will be case eventually, and you did not enroll the 2023 certificate yet, yes they will likely fail to boot if secure boot is enabled. See the docs for more information and on how to enroll the new certificate [1]. [1]...

Do you use some kind of Proxy between your PBS host and Backblaze? If not, that seems unlikely. Looking at the docs for Backblaze [1] the error message here should be different. It should respond with 503 error, not a 500 one. So I doubt that this is the case. However, in theory there could be...

Hm, these look like errors that occur on Backblaze's end. Not sure if they expose this information to you, but if so can you see any errors reported in your Backblaze account? Or was there some kind of outage during the upload? Looking at the code it seems that the s3 client has tried to upload...

Please open a ticket in our shop system for further inquiries [1]. This is the community support forum and requests for partner status cannot be handled here. [1]: https://shop.proxmox.com/submitticket.php?step=2&deptid=1

The forum is a progressive web app, you can in theory add it to your phone's home screen through its browser [1]. However, in my experience such apps tend to be somewhat lacking compared to proper native apps. [1]: https://xenforo.com/community/threads/progressive-web-app.181448/

What are you looking for here? What do you want to post, but can't?

Hey, there is our official Proxmox VE app: - https://pve.proxmox.com/wiki/Proxmox_VE_Mobile - https://play.google.com/store/apps/details?id=com.proxmox.app.pve_flutter_frontend Is that what you are looking for?

Since you've already went ahead and did it, I'll add this for posterity’s sake: Yes it's exactly the same :) Please mark this thread as “Solved” by clicking “Edit thread” above and adding the “Solved” prefix, this will help other users find this solution if they are in the same position! Thanks!

Can you run pmg8to9 and post the output here? My suspicion is that this is related to systemd-boot not having been removed yet.