starred/ProxmoxVE

Fork 0

mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-04-26 17:56:06 +03:00

[GH-ISSUE #6623] Upgrade scripts to work with PBS 4 #1408

New issue

Closed

opened 2026-02-26 12:48:48 +03:00 by kerem · 11 comments

kerem commented

2026-02-26 12:48:48 +03:00

Owner

Originally created by @yodaphone on GitHub (Aug 7, 2025).
Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/6623

🌟 Briefly describe the feature

Add support for Post Install Script to work with PBS 4

📝 Detailed description

Add support for Post Install Script to work with PBS 4

💡 Why is this useful?

Proxmox Backup Server 4 also uses Debian 13 (trixie) and updating this script will be helpful to run the post install script that worked great with Ver 3

Originally created by @yodaphone on GitHub (Aug 7, 2025). Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/6623 ### 🌟 Briefly describe the feature Add support for Post Install Script to work with PBS 4 ### 📝 Detailed description Add support for Post Install Script to work with PBS 4 ### 💡 Why is this useful? Proxmox Backup Server 4 also uses Debian 13 (trixie) and updating this script will be helpful to run the post install script that worked great with Ver 3

kerem

2026-02-26 12:48:48 +03:00

closed this issue
added the
enhancement
label

kerem commented

2026-02-26 12:48:48 +03:00

Author

Owner

@fkrauthan commented on GitHub (Aug 7, 2025):

Not sure if this should be a separate issue but it would be great if the update script for the PBS LXC container could also perform the PBS4 upgrade (not sure if that is something in scope of that script)

@fkrauthan commented on GitHub (Aug 7, 2025): Not sure if this should be a separate issue but it would be great if the update script for the PBS LXC container could also perform the PBS4 upgrade (not sure if that is something in scope of that script)

kerem commented

2026-02-26 12:48:49 +03:00

Author

Owner

@MickLesk commented on GitHub (Aug 7, 2025):

Debian 13 itself is not yet available as a template, so support is not possible. Only the old script continues to work and must be upgraded manually.

@MickLesk commented on GitHub (Aug 7, 2025): Debian 13 itself is not yet available as a template, so support is not possible. Only the old script continues to work and must be upgraded manually. <img width="438" height="214" alt="Image" src="https://github.com/user-attachments/assets/4f3664de-5e9f-48da-bf22-ce30e3755c9f" />

kerem commented

2026-02-26 12:48:49 +03:00

Author

Owner

@flo-m commented on GitHub (Aug 8, 2025):

Not sure if this should be a separate issue but it would be great if the update script for the PBS LXC container could also perform the PBS4 upgrade (not sure if that is something in scope of that script)

that would be really great

@flo-m commented on GitHub (Aug 8, 2025): > Not sure if this should be a separate issue but it would be great if the update script for the PBS LXC container could also perform the PBS4 upgrade (not sure if that is something in scope of that script) that would be really great

kerem commented

2026-02-26 12:48:49 +03:00

Author

Owner

@paolomainardi commented on GitHub (Sep 1, 2025):

Sorry, can the script pbs4-upgrade.sh implemented in #7214 be used on PBS LXC 3?

@paolomainardi commented on GitHub (Sep 1, 2025): Sorry, can the script `pbs4-upgrade.sh` implemented in #7214 be used on PBS LXC 3?

kerem commented

2026-02-26 12:48:49 +03:00

Author

Owner

@MickLesk commented on GitHub (Sep 1, 2025):

Thats an upgrade only from 3 to 4?

@MickLesk commented on GitHub (Sep 1, 2025): Thats an upgrade only from 3 to 4?

kerem commented

2026-02-26 12:48:49 +03:00

Author

Owner

@paolomainardi commented on GitHub (Sep 1, 2025):

@MickLesk, yes, it's a simple PBS LXC v3 based on Debian 12. I tried it and it worked, but I encountered an issue with apt keys that I resolved using wget https://enterprise.proxmox.com/debian/proxmox-archive-keyring-trixie.gpg -O /usr/share/keyrings/proxmox-archive-keyring.gpg.

@paolomainardi commented on GitHub (Sep 1, 2025): @MickLesk, yes, it's a simple PBS LXC v3 based on Debian 12. I tried it and it worked, but I encountered an issue with apt keys that I resolved using `wget https://enterprise.proxmox.com/debian/proxmox-archive-keyring-trixie.gpg -O /usr/share/keyrings/proxmox-archive-keyring.gpg`.

kerem commented

2026-02-26 12:48:49 +03:00

Author

Owner

@MickLesk commented on GitHub (Sep 1, 2025):

why enterprise keyring? and whats the error? - create an discussion or an issue, not on old requests

@MickLesk commented on GitHub (Sep 1, 2025): why enterprise keyring? and whats the error? - create an discussion or an issue, not on old requests

kerem commented

2026-02-26 12:48:49 +03:00

Author

Owner

@paolomainardi commented on GitHub (Sep 1, 2025):

why enterprise keyring? and whats the error? - create an discussion or an issue, not on old requests

Sorry, you are totally right.

Anyway the error was this one:

root@pbs:~# apt update
Hit:1 http://deb.debian.org/debian trixie InRelease
Hit:2 http://security.debian.org/debian-security trixie-security InRelease
Hit:3 http://deb.debian.org/debian trixie-updates InRelease
Get:4 http://download.proxmox.com/debian/pbs trixie InRelease [2,785 B]
Err:4 http://download.proxmox.com/debian/pbs trixie InRelease
The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY A7BCD1420BFE778E
Reading package lists… Done
W: GPG error: http://download.proxmox.com/debian/pbs trixie InRelease: The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY A7BCD1420BFE778E
E: The repository ‘http://download.proxmox.com/debian/pbs trixie InRelease’ is not signed.
N: Updating from such a repository can’t be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

(Sorry I cannot find now to properly format it as code from the GitHub app, as I am moving)

And the enterprise keyring fixed it.

Back to the original question, is the script intended to be used even in the LXC context?

Thanks!

@paolomainardi commented on GitHub (Sep 1, 2025): > why enterprise keyring? and whats the error? - create an discussion or an issue, not on old requests Sorry, you are totally right. Anyway the error was this one: root@pbs:~# apt update Hit:1 http://deb.debian.org/debian trixie InRelease Hit:2 http://security.debian.org/debian-security trixie-security InRelease Hit:3 http://deb.debian.org/debian trixie-updates InRelease Get:4 http://download.proxmox.com/debian/pbs trixie InRelease [2,785 B] Err:4 http://download.proxmox.com/debian/pbs trixie InRelease The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY A7BCD1420BFE778E Reading package lists… Done W: GPG error: http://download.proxmox.com/debian/pbs trixie InRelease: The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY A7BCD1420BFE778E E: The repository ‘http://download.proxmox.com/debian/pbs trixie InRelease’ is not signed. N: Updating from such a repository can’t be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. (Sorry I cannot find now to properly format it as code from the GitHub app, as I am moving) And the enterprise keyring fixed it. Back to the original question, is the script intended to be used even in the LXC context? Thanks!

kerem commented

2026-02-26 12:48:49 +03:00

Author

Owner

@MickLesk commented on GitHub (Sep 1, 2025):

Yes

@MickLesk commented on GitHub (Sep 1, 2025): Yes

kerem commented

2026-02-26 12:48:49 +03:00

Author

Owner

@paolomainardi commented on GitHub (Sep 1, 2025):

Ok thanks, I'll open an issue about the keyring problem.

@paolomainardi commented on GitHub (Sep 1, 2025): Ok thanks, I'll open an issue about the keyring problem.

kerem commented

2026-02-26 12:48:49 +03:00

Author

Owner

@chrisjenx commented on GitHub (Sep 6, 2025):

Had this issue today, @paolomainardi workaround fixed it for me after I got the error

@chrisjenx commented on GitHub (Sep 6, 2025): Had this issue today, @paolomainardi workaround fixed it for me after I got the error

kerem referenced this issue

2026-02-26 13:32:38 +03:00

[PR #1408] [MERGED] Fix user in ghost-cli install command #3168

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/ProxmoxVE#1408

No description provided.

Rows
Columns