starred/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-07-16 05:34:07 +03:00
Code Issues 23 Packages Projects Releases 44 Wiki Activity

Debian 13 UPGRADE Incompatibilities #1563

New Issue
Open
opened 2026-02-05 01:34:04 +03:00 by OVERLORD · 47 comments
OVERLORD commented 2026-02-05 01:34:04 +03:00
Owner
Copy Link

Originally created by @CrazyWolf13 on GitHub (Sep 1, 2025).

Originally assigned to: @CrazyWolf13 on GitHub.

📌 Task summary

Check Script for Debian 13 Compatibility

Warning

Do not run the migration without taking full backups of the LXC, this process can render your service unusable.

This Task serves to create a list of all LXC that don't currently work with debian 13, this will be updated as soon as problems are resolved.

📋 Task details

Following LXC have issues:

Possibly needs user fixing:
Remove the following line from you /etc/apache2/sites-available/fresrss.conf
OIDCRefreshAccessTokenBeforeExpiry 30
https://github.com/OpenIDC/mod_auth_openidc/discussions/1349#discussioncomment-14542930

  • MongoDB
    So far detected:
  • Omada
  • All LXC that have custom PHP Modules installed:
    So far detected:
  • Wallos
  • Striling-PDF

Fix:
Go to this url: https://github.com/community-scripts/ProxmoxVE/tree/main/install and find the install file for the broken service.
Locate the php command including the vars, in wallos it's this: PHP_VERSION="8.4" PHP_APACHE="YES" PHP_MODULE="imagick,bz2,sqlite3" setup_php

Then run the following in the LXC:

source <(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/misc/core.func)
source <(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/misc/tools.func)
# Add the line from the installer script here, for example from wallos:
# PHP_VERSION="8.4" PHP_APACHE="YES" PHP_MODULE="imagick,bz2,sqlite3" setup_php
  • All LXC that have custom Python Modules installed and not yet a venv?:
    Fix: manually re-run the python install commands or re-create the LXC.

Signature Errors (Non-breaking)

Warning: http://openresty.org/package/debian/dists/bookworm/InRelease: Policy will reject signature within a year, see --audit for details.

Warning: https://archive.heckel.io/apt/dists/debian/InRelease: Policy will reject signature within a year, see --audit for details

Warning: https://deb.nodesource.com/node_20.x/dists/nodistro/InRelease: Policy will reject signature within a year, see --audit for details

  • Unify Controller
    --Outstanding, created a forums entry.

Warning: https://www.ui.com/downloads/unifi/debian/dists/stable/InRelease: Policy will reject signature within a year, see --audit for details

Originally created by @CrazyWolf13 on GitHub (Sep 1, 2025). Originally assigned to: @CrazyWolf13 on GitHub. ### 📌 Task summary Check Script for Debian 13 Compatibility > [!WARNING] > Do not run the migration without taking full backups of the LXC, this process can render your service unusable. This Task serves to create a list of all LXC that don't currently work with debian 13, this will be updated as soon as problems are resolved. ### 📋 Task details Following LXC have issues: - [x] FreshRSS: ---FIXED--- https://github.com/FreshRSS/FreshRSS/issues/7860 > Possibly needs user fixing: > Remove the following line from you /etc/apache2/sites-available/fresrss.conf > `OIDCRefreshAccessTokenBeforeExpiry 30` > https://github.com/OpenIDC/mod_auth_openidc/discussions/1349#discussioncomment-14542930 --- - [x] Changedetection: ---FIXED--- Problem with Playwright https://github.com/browserless/browserless/issues/4914 https://github.com/browserless/browserless/pull/4927 --- - [x] MQTT ---FIXED--- https://github.com/eclipse-mosquitto/mosquitto/issues/3339 --- - [ ] MongoDB So far detected: - Omada --- - [ ] All LXC that have custom PHP Modules installed: So far detected: - Wallos - Striling-PDF Fix: Go to this url: https://github.com/community-scripts/ProxmoxVE/tree/main/install and find the install file for the broken service. Locate the php command including the vars, in wallos it's this: `PHP_VERSION="8.4" PHP_APACHE="YES" PHP_MODULE="imagick,bz2,sqlite3" setup_php` Then run the following in the LXC: ```bash source <(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/misc/core.func) source <(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/misc/tools.func) # Add the line from the installer script here, for example from wallos: # PHP_VERSION="8.4" PHP_APACHE="YES" PHP_MODULE="imagick,bz2,sqlite3" setup_php ``` --- - [ ] All LXC that have custom Python Modules installed and not yet a venv?: Fix: manually re-run the python install commands or re-create the LXC. --- Signature Errors (Non-breaking) - [ ] NginxProxyManager https://github.com/openresty/openresty/issues/1054 > Warning: http://openresty.org/package/debian/dists/bookworm/InRelease: Policy will reject signature within a year, see --audit for details. --- - [x] Ntfy https://github.com/binwiederhier/ntfy/issues/1401 > Warning: https://archive.heckel.io/apt/dists/debian/InRelease: Policy will reject signature within a year, see --audit for details --- - [ ] Nodesource (all apps that use Node) https://github.com/nodesource/distributions/issues/1865 > Warning: https://deb.nodesource.com/node_20.x/dists/nodistro/InRelease: Policy will reject signature within a year, see --audit for details ---- - [ ] Unify Controller --Outstanding, created a forums entry. > Warning: https://www.ui.com/downloads/unifi/debian/dists/stable/InRelease: Policy will reject signature within a year, see --audit for details ---
OVERLORD added the investigation label 2026-02-05 01:34:04 +03:00
OVERLORD commented 2026-02-05 01:34:08 +03:00
Author
Owner
Copy Link

@Aloe-recite commented on GitHub (Sep 2, 2025):

I can confirm Changedetection.
Adding in AdventureLog (didn't test v0.11 released yesterday), Calibre-Web, Wallos, all showing a blank page ufter the LXC update to Trixie that I wasn't able to investigate being the noob I am (and didn't bother too much honestly, since they work fine with 12 and I wanted to update to 13 just for fur / forthe sake of it).
Tailscale also gives me issues but I installed it manually, not with helper-scripts, so don't count it but let me warn nonetheless

@Aloe-recite commented on GitHub (Sep 2, 2025): I can confirm Changedetection. Adding in AdventureLog (didn't test v0.11 released yesterday), Calibre-Web, Wallos, all showing a blank page ufter the LXC update to Trixie that I wasn't able to investigate being the noob I am (and didn't bother too much honestly, since they work fine with 12 and I wanted to update to 13 just for fur / forthe sake of it). Tailscale also gives me issues but I installed it manually, not with helper-scripts, so don't count it but let me warn nonetheless
OVERLORD commented 2026-02-05 01:34:11 +03:00
Author
Owner
Copy Link

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

Known missing repos:

@MickLesk commented on GitHub (Sep 2, 2025): Known missing repos: - MQTT - MongoDB (https://repo.mongodb.org/apt/debian/dists/)
OVERLORD commented 2026-02-05 01:34:13 +03:00
Author
Owner
Copy Link

@CrazyWolf13 commented on GitHub (Sep 2, 2025):

@Aloe-recite yes all scripts that use the php function also fail, I forgot to add that, though they can be fixed with the following:

Go to this url: https://github.com/community-scripts/ProxmoxVE/tree/main/install and find the install file for the broken service.
Locate the php command including the vars, in wallos it's this: PHP_VERSION="8.4" PHP_APACHE="YES" PHP_MODULE="imagick,bz2,sqlite3" setup_php

Then run the following in the LXC:

source <(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/misc/core.func)
source <(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/misc/tools.func)
# Add the line from the installer script here, for example from wallos:
# PHP_VERSION="8.4" PHP_APACHE="YES" PHP_MODULE="imagick,bz2,sqlite3" setup_php
@CrazyWolf13 commented on GitHub (Sep 2, 2025): @Aloe-recite yes all scripts that use the php function also fail, I forgot to add that, though they can be fixed with the following: Go to this url: https://github.com/community-scripts/ProxmoxVE/tree/main/install and find the install file for the broken service. Locate the php command including the vars, in wallos it's this: `PHP_VERSION="8.4" PHP_APACHE="YES" PHP_MODULE="imagick,bz2,sqlite3" setup_php` Then run the following in the LXC: ```bash source <(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/misc/core.func) source <(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/misc/tools.func) # Add the line from the installer script here, for example from wallos: # PHP_VERSION="8.4" PHP_APACHE="YES" PHP_MODULE="imagick,bz2,sqlite3" setup_php ```
OVERLORD commented 2026-02-05 01:34:16 +03:00
Author
Owner
Copy Link

@Aloe-recite commented on GitHub (Sep 2, 2025):

@CrazyWolf13 thanks for your help, I'm not sure I understand the procedure though. Should I upgrade to 13 and then run your code, or viceversa? Will it survive future "update" commands or should we wait for a rebuild? On a side note, also Stirling PDF is affected - I suppose for the same reasons.
Thanks!

@Aloe-recite commented on GitHub (Sep 2, 2025): @CrazyWolf13 thanks for your help, I'm not sure I understand the procedure though. Should I upgrade to 13 and then run your code, or viceversa? Will it survive future "update" commands or should we wait for a rebuild? On a side note, also Stirling PDF is affected - I suppose for the same reasons. Thanks!
OVERLORD commented 2026-02-05 01:34:23 +03:00
Author
Owner
Copy Link

@CrazyWolf13 commented on GitHub (Sep 2, 2025):

@Aloe-recite Apologies, I may have explained a bit too little, my guess is that during the migration php modules that were previously installed don't get re-installed properly during the migration, my code re-installs the modules as they were during initial install of wallos. So first do the migration, then run my code.

Same for Stirling-PDF, yes.

@CrazyWolf13 commented on GitHub (Sep 2, 2025): @Aloe-recite Apologies, I may have explained a bit too little, my guess is that during the migration php modules that were previously installed don't get re-installed properly during the migration, my code re-installs the modules as they were during initial install of wallos. So first do the migration, then run my code. Same for Stirling-PDF, yes.
OVERLORD commented 2026-02-05 01:34:31 +03:00
Author
Owner
Copy Link

@Aloe-recite commented on GitHub (Sep 3, 2025):

@CrazyWolf13 thanks, it worked for Wallos!
For Stirling-pdf, honestly I just upgraded normally and it worked this time. I did two tentatives before to no avail, same set of commands, this time works as a charme...

Booklore on the contrary seems not to cooperate and looking at the script it doesn't seem like a php issue, but I haven't been able to determine the origin, except that it probably has to do with Nginx: instead of the app, I see the default "Welcome to nginx!" page. Nginx.conf seems correct and is the booklore one though. For good measure I reapplied the commands in the script but to no avail.

Calibre-web, will test it tomorrow...

@Aloe-recite commented on GitHub (Sep 3, 2025): @CrazyWolf13 thanks, it worked for Wallos! For Stirling-pdf, honestly I just upgraded normally and it worked this time. I did two tentatives before to no avail, same set of commands, this time works as a charme... Booklore on the contrary seems not to cooperate and looking at the script it doesn't seem like a php issue, but I haven't been able to determine the origin, except that it probably has to do with Nginx: instead of the app, I see the default "Welcome to nginx!" page. Nginx.conf seems correct and is the booklore one though. For good measure I reapplied the commands in the script but to no avail. Calibre-web, will test it tomorrow...
OVERLORD commented 2026-02-05 01:34:33 +03:00
Author
Owner
Copy Link

@sym0nd0 commented on GitHub (Sep 4, 2025):

Updated to Debian 13 and hosed my Beszel LXC, can't see any mention of PHP in the install script.

@sym0nd0 commented on GitHub (Sep 4, 2025): Updated to Debian 13 and hosed my Beszel LXC, can't see any mention of PHP in the install script.
OVERLORD commented 2026-02-05 01:34:37 +03:00
Author
Owner
Copy Link

@CrazyWolf13 commented on GitHub (Sep 5, 2025):

@sym0nd0 my beszel updated without issues.
Try restoring a backup.

Beszel is a plain debian installation with the package from the dev.

Try checking status with systemctl status beszel-hub

@CrazyWolf13 commented on GitHub (Sep 5, 2025): @sym0nd0 my beszel updated without issues. Try restoring a backup. Beszel is a plain debian installation with the package from the dev. Try checking status with `systemctl status beszel-hub`
OVERLORD commented 2026-02-05 01:34:43 +03:00
Author
Owner
Copy Link

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

The MQTT topic should be solved with #7423

@EtlamGit commented on GitHub (Sep 6, 2025): The MQTT topic should be solved with #7423
OVERLORD commented 2026-02-05 01:34:45 +03:00
Author
Owner
Copy Link

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

true, thanks @EtlamGit

@CrazyWolf13 commented on GitHub (Sep 6, 2025): true, thanks @EtlamGit
OVERLORD commented 2026-02-05 01:34:50 +03:00
Author
Owner
Copy Link

@CrazyWolf13 commented on GitHub (Sep 10, 2025):

LXC that need testing to fruther analyse the cause of a failing update:

  • Bar-Assistant
  • phpipam
  • Adventurelog
  • Booklore (seems to start, but shows a generic nginx welcome page?)
  • Calibre web
  • Huntarr
@CrazyWolf13 commented on GitHub (Sep 10, 2025): LXC that need testing to fruther analyse the cause of a failing update: - Bar-Assistant - phpipam - Adventurelog - Booklore (seems to start, but shows a generic nginx welcome page?) - Calibre web - Huntarr
OVERLORD commented 2026-02-05 01:34:53 +03:00
Author
Owner
Copy Link

@vehystrix commented on GitHub (Sep 14, 2025):

Omada LXC also doesn't work, because it tries to install mongodb and there's no mongodb for debian 13

Err:7 http://repo.mongodb.org/apt/debian trixie/mongodb-org/7.0 Release
  404  Not Found

I changed the apt source to go to bookworm instead and installing mongodb 7 works, but the update script still fails
Suggestion:
only add the mongodb source if the source file doesn't already exist

@vehystrix commented on GitHub (Sep 14, 2025): Omada LXC also doesn't work, because it tries to install mongodb and there's no mongodb for debian 13 ``` Err:7 http://repo.mongodb.org/apt/debian trixie/mongodb-org/7.0 Release 404 Not Found ``` I changed the apt source to go to bookworm instead and installing mongodb 7 works, but the update script still fails Suggestion: only add the mongodb source if the source file doesn't already exist
OVERLORD commented 2026-02-05 01:34:56 +03:00
Author
Owner
Copy Link

@CrazyWolf13 commented on GitHub (Sep 14, 2025):

@vehystrix this is already listed above, I add omada to the list.

@CrazyWolf13 commented on GitHub (Sep 14, 2025): @vehystrix this is already listed above, I add omada to the list.
OVERLORD commented 2026-02-05 01:35:01 +03:00
Author
Owner
Copy Link

@vhsdream commented on GitHub (Sep 19, 2025):

@CrazyWolf13 I didn't install FreshRSS via a Community Script, but I found after upgrading to Trixie I had the same issue you're experiencing. In my case I was missing a PHP module because for some reason my install also upgrades PHP from 8.2 to 8.4. I just installed a test version via the script, setup OpenID, then ran through the Trixie upgrade, rebooted and everything worked.

But I was able to find out why my original instance wasn't working by checking the freshrss error log. I see that in the issue on the FreshRSS Github you didn't seem to include that log. It's in /var/log/apache2/freshrss_error.log - perhaps you'll find more info there.

@vhsdream commented on GitHub (Sep 19, 2025): @CrazyWolf13 I didn't install FreshRSS via a Community Script, but I found after upgrading to Trixie I had the same issue you're experiencing. In my case I was missing a PHP module because for some reason my install also upgrades PHP from 8.2 to 8.4. I just installed a test version via the script, setup OpenID, then ran through the Trixie upgrade, rebooted and everything worked. But I was able to find out why my original instance wasn't working by checking the freshrss error log. I see that in the issue on the FreshRSS Github you didn't seem to include that log. It's in `/var/log/apache2/freshrss_error.log` - perhaps you'll find more info there.
OVERLORD commented 2026-02-05 01:35:04 +03:00
Author
Owner
Copy Link

@CrazyWolf13 commented on GitHub (Sep 19, 2025):

@vhsdream because my freshrss_error log is empty ;)

So you are running openidc SSO with debian trixie successfully?
Would you mind sharing you config then?

@CrazyWolf13 commented on GitHub (Sep 19, 2025): @vhsdream because my freshrss_error log is empty ;) So you are running openidc SSO with debian trixie successfully? Would you mind sharing you config then?
OVERLORD commented 2026-02-05 01:35:07 +03:00
Author
Owner
Copy Link

@Aloe-recite commented on GitHub (Sep 19, 2025):

Hi, this might be relevant I hope.
Flaresolverr 3.4.1 (latest as of today) works fine within an. LXC update to 13.1, however a few recent packages upgrades broke it.

google-chrome-stable/stable 140.0.7339.185-1 amd64 [upgradable from: 140.0.7339.80-1]
libcups2t64/stable-security 2.4.10-3+deb13u1 amd64 [upgradable from: 2.4.10-3]
libnss-systemd/stable-updates 257.8-1~deb13u2 amd64 [upgradable from: 257.8-1~deb13u1]
libpam-systemd/stable-updates 257.8-1~deb13u2 amd64 [upgradable from: 257.8-1~deb13u1]
libsystemd-shared/stable-updates 257.8-1~deb13u2 amd64 [upgradable from: 257.8-1~deb13u1]
libsystemd0/stable-updates 257.8-1~deb13u2 amd64 [upgradable from: 257.8-1~deb13u1]
libudev1/stable-updates 257.8-1~deb13u2 amd64 [upgradable from: 257.8-1~deb13u1]
systemd-cryptsetup/stable-updates 257.8-1~deb13u2 amd64 [upgradable from: 257.8-1~deb13u1]
systemd-sysv/stable-updates 257.8-1~deb13u2 amd64 [upgradable from: 257.8-1~deb13u1]
systemd-timesyncd/stable-updates 257.8-1~deb13u2 amd64 [upgradable from: 257.8-1~deb13u1]
systemd/stable-updates 257.8-1~deb13u2 amd64 [upgradable from: 257.8-1~deb13u1]
udev/stable-updates 257.8-1~deb13u2 amd64 [upgradable from: 257.8-1~deb13u1]

Seems like the executable is being moved/deleted?

root@flaresolverr:~# journalctl -u flaresolverr -f
Sep 18 19:24:51 flaresolverr (esolverr)[86475]: flaresolverr.service: Unable to locate executable '/opt/flaresolverr/flaresolverr': No such file or directory
Sep 18 19:24:51 flaresolverr (esolverr)[86475]: flaresolverr.service: Failed at step EXEC spawning /opt/flaresolverr/flaresolverr: No such file or directory
Sep 18 19:24:51 flaresolverr systemd[1]: flaresolverr.service: Main process exited, code=exited, status=203/EXEC
Sep 18 19:24:51 flaresolverr systemd[1]: flaresolverr.service: Failed with result 'exit-code'.
Sep 18 19:24:56 flaresolverr systemd[1]: flaresolverr.service: Scheduled restart job, restart counter is at 3.
Sep 18 19:24:56 flaresolverr systemd[1]: Started flaresolverr.service - FlareSolverr.
Sep 18 19:24:56 flaresolverr (esolverr)[86477]: flaresolverr.service: Unable to locate executable '/opt/flaresolverr/flaresolverr': No such file or directory
Sep 18 19:24:56 flaresolverr (esolverr)[86477]: flaresolverr.service: Failed at step EXEC spawning /opt/flaresolverr/flaresolverr: No such file or directory
Sep 18 19:24:56 flaresolverr systemd[1]: flaresolverr.service: Main process exited, code=exited, status=203/EXEC
Sep 18 19:24:56 flaresolverr systemd[1]: flaresolverr.service: Failed with result 'exit-code'.
@Aloe-recite commented on GitHub (Sep 19, 2025): Hi, this might be relevant I hope. Flaresolverr 3.4.1 (latest as of today) works fine within an. LXC update to 13.1, however a few recent packages upgrades broke it. ``` google-chrome-stable/stable 140.0.7339.185-1 amd64 [upgradable from: 140.0.7339.80-1] libcups2t64/stable-security 2.4.10-3+deb13u1 amd64 [upgradable from: 2.4.10-3] libnss-systemd/stable-updates 257.8-1~deb13u2 amd64 [upgradable from: 257.8-1~deb13u1] libpam-systemd/stable-updates 257.8-1~deb13u2 amd64 [upgradable from: 257.8-1~deb13u1] libsystemd-shared/stable-updates 257.8-1~deb13u2 amd64 [upgradable from: 257.8-1~deb13u1] libsystemd0/stable-updates 257.8-1~deb13u2 amd64 [upgradable from: 257.8-1~deb13u1] libudev1/stable-updates 257.8-1~deb13u2 amd64 [upgradable from: 257.8-1~deb13u1] systemd-cryptsetup/stable-updates 257.8-1~deb13u2 amd64 [upgradable from: 257.8-1~deb13u1] systemd-sysv/stable-updates 257.8-1~deb13u2 amd64 [upgradable from: 257.8-1~deb13u1] systemd-timesyncd/stable-updates 257.8-1~deb13u2 amd64 [upgradable from: 257.8-1~deb13u1] systemd/stable-updates 257.8-1~deb13u2 amd64 [upgradable from: 257.8-1~deb13u1] udev/stable-updates 257.8-1~deb13u2 amd64 [upgradable from: 257.8-1~deb13u1] ``` Seems like the executable is being moved/deleted? ``` root@flaresolverr:~# journalctl -u flaresolverr -f Sep 18 19:24:51 flaresolverr (esolverr)[86475]: flaresolverr.service: Unable to locate executable '/opt/flaresolverr/flaresolverr': No such file or directory Sep 18 19:24:51 flaresolverr (esolverr)[86475]: flaresolverr.service: Failed at step EXEC spawning /opt/flaresolverr/flaresolverr: No such file or directory Sep 18 19:24:51 flaresolverr systemd[1]: flaresolverr.service: Main process exited, code=exited, status=203/EXEC Sep 18 19:24:51 flaresolverr systemd[1]: flaresolverr.service: Failed with result 'exit-code'. Sep 18 19:24:56 flaresolverr systemd[1]: flaresolverr.service: Scheduled restart job, restart counter is at 3. Sep 18 19:24:56 flaresolverr systemd[1]: Started flaresolverr.service - FlareSolverr. Sep 18 19:24:56 flaresolverr (esolverr)[86477]: flaresolverr.service: Unable to locate executable '/opt/flaresolverr/flaresolverr': No such file or directory Sep 18 19:24:56 flaresolverr (esolverr)[86477]: flaresolverr.service: Failed at step EXEC spawning /opt/flaresolverr/flaresolverr: No such file or directory Sep 18 19:24:56 flaresolverr systemd[1]: flaresolverr.service: Main process exited, code=exited, status=203/EXEC Sep 18 19:24:56 flaresolverr systemd[1]: flaresolverr.service: Failed with result 'exit-code'. ```
OVERLORD commented 2026-02-05 01:35:10 +03:00
Author
Owner
Copy Link

@CrazyWolf13 commented on GitHub (Sep 20, 2025):

@Aloe-recite I can't replicate this behaviour, I just updated my flarresolver app some days ago without problems. I've been running it as a upgraded deb12->deb13 lxc since some weeks without issues.

Can you do ls -al /opt/flaresolverr ?

EDIT: why are you even running such a new version?

we pinned the release long ago? did you mess with this by yourself?
522f427677

@CrazyWolf13 commented on GitHub (Sep 20, 2025): @Aloe-recite I can't replicate this behaviour, I just updated my flarresolver app some days ago without problems. I've been running it as a upgraded deb12->deb13 lxc since some weeks without issues. Can you do `ls -al /opt/flaresolverr` ? EDIT: why are you even running such a new version? we pinned the release long ago? did you mess with this by yourself? https://github.com/community-scripts/ProxmoxVE/commit/522f427677632d78fdd594236da6bf9c9a801f72
OVERLORD commented 2026-02-05 01:35:14 +03:00
Author
Owner
Copy Link

@Riggspsk commented on GitHub (Sep 24, 2025):

Overseerr has the "Warning: https://deb.nodesource.com/node_22.x/dists/nodistro/InRelease: Policy will reject signature within a year, see --audit for details".

@Riggspsk commented on GitHub (Sep 24, 2025): Overseerr has the "Warning: https://deb.nodesource.com/node_22.x/dists/nodistro/InRelease: Policy will reject signature within a year, see --audit for details".
OVERLORD commented 2026-02-05 01:35:18 +03:00
Author
Owner
Copy Link

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

that has all node repos https://github.com/nodesource/distributions/issues/1865

@MickLesk commented on GitHub (Sep 24, 2025): that has all node repos https://github.com/nodesource/distributions/issues/1865
OVERLORD commented 2026-02-05 01:35:21 +03:00
Author
Owner
Copy Link

@Aloe-recite commented on GitHub (Sep 24, 2025):

that has all node repos nodesource/distributions#1865

I read that thread but it looks like that there isn't a solution yet and it's something on their side. Is that correct?

@Aloe-recite commented on GitHub (Sep 24, 2025): > that has all node repos [nodesource/distributions#1865](https://github.com/nodesource/distributions/issues/1865) I read that thread but it looks like that there isn't a solution yet and it's something on their side. Is that correct?
OVERLORD commented 2026-02-05 01:35:27 +03:00
Author
Owner
Copy Link

@CrazyWolf13 commented on GitHub (Sep 24, 2025):

@Aloe-recite yes that's just a warning, nothing we or the users can change, this needs a fix from node.

@CrazyWolf13 commented on GitHub (Sep 24, 2025): @Aloe-recite yes that's just a warning, nothing we or the users can change, this needs a fix from node.
OVERLORD commented 2026-02-05 01:35:32 +03:00
Author
Owner
Copy Link

@Czbernd commented on GitHub (Sep 28, 2025):

@CrazyWolf13 it seems like the unifi controller lxc is also affected:

"W: https://www.ui.com/downloads/unifi/debian/dists/stable/InRelease: Policy will reject signature within a year, see --audit for details"

from the signature issue.

@Czbernd commented on GitHub (Sep 28, 2025): @CrazyWolf13 it seems like the unifi controller lxc is also affected: "W: https://www.ui.com/downloads/unifi/debian/dists/stable/InRelease: Policy will reject signature within a year, see --audit for details" from the signature issue.
OVERLORD commented 2026-02-05 01:35:37 +03:00
Author
Owner
Copy Link

@burgerga commented on GitHub (Sep 28, 2025):

Guacamole also affected:

Debian 13 updated to freerdp3 (freerdp2-dev is no longer availlable), but guacamole has marked freerdp3 support experimental (https://issues.apache.org/jira/browse/GUACAMOLE-1026).

Currently switching from freerdp2-dev to freerdp3-dev results in a compile error because of deprecation warnings (https://github.com/FreeRDP/FreeRDP/issues/11412) that are converted into errors because guacamole compiles freerdp with -Werror (https://github.com/apache/guacamole-server/blob/main/configure.ac#L768)

@burgerga commented on GitHub (Sep 28, 2025): Guacamole also affected: Debian 13 updated to freerdp3 (freerdp2-dev is no longer availlable), but guacamole has marked freerdp3 support experimental (https://issues.apache.org/jira/browse/GUACAMOLE-1026). Currently switching from freerdp2-dev to freerdp3-dev results in a compile error because of deprecation warnings (https://github.com/FreeRDP/FreeRDP/issues/11412) that are converted into errors because guacamole compiles freerdp with `-Werror` (https://github.com/apache/guacamole-server/blob/main/configure.ac#L768)
OVERLORD commented 2026-02-05 01:35:39 +03:00
Author
Owner
Copy Link

@CrazyWolf13 commented on GitHub (Sep 28, 2025):

@burgerga I updated my guacamole LXC just fine first to guacamole 1.6 then the lxc to debian trixie without issues.

@CrazyWolf13 commented on GitHub (Sep 28, 2025): @burgerga I updated my guacamole LXC just fine first to guacamole 1.6 then the lxc to debian trixie without issues.
OVERLORD commented 2026-02-05 01:35:44 +03:00
Author
Owner
Copy Link

@burgerga commented on GitHub (Sep 28, 2025):

@CrazyWolf13 I think you then compiled with freerdp2-dev (in Debian 12) not triggering the issue, right? That would work, but setting debian 13 for new LXC doesn't work (see my https://github.com/burgerga/ProxmoxVE/commits/feat_guacamole_debian13/ branch)

@burgerga commented on GitHub (Sep 28, 2025): @CrazyWolf13 I think you then compiled with `freerdp2-dev` (in Debian 12) not triggering the issue, right? That would work, but setting debian 13 for new LXC doesn't work (see my https://github.com/burgerga/ProxmoxVE/commits/feat_guacamole_debian13/ branch)
OVERLORD commented 2026-02-05 01:35:47 +03:00
Author
Owner
Copy Link

@CrazyWolf13 commented on GitHub (Sep 29, 2025):

For everyone Freshrss has been fixed by the authors of the SSO plugin that freshrss used, above in the initial post I added steps on how to fix a "bad gateway" issue when using OIDC Single-Sign-On.
(cc: @vhsdream)

@CrazyWolf13 commented on GitHub (Sep 29, 2025): For everyone Freshrss has been fixed by the authors of the SSO plugin that freshrss used, above in the initial post I added steps on how to fix a "bad gateway" issue when using OIDC Single-Sign-On. (cc: @vhsdream)
OVERLORD commented 2026-02-05 01:35:53 +03:00
Author
Owner
Copy Link

@bwh commented on GitHub (Sep 30, 2025):

Zabbix LXC update command results in
"Unsupported Debian version: bookworm – please upgrade to Debian 13 (Trixie) before updating Zabbix."
I hope this is the right place to mention this.

@bwh commented on GitHub (Sep 30, 2025): Zabbix LXC update command results in "Unsupported Debian version: bookworm – please upgrade to Debian 13 (Trixie) before updating Zabbix." I hope this is the right place to mention this.
OVERLORD commented 2026-02-05 01:35:58 +03:00
Author
Owner
Copy Link

@CrazyWolf13 commented on GitHub (Sep 30, 2025):

@bwh Yeah that's correct isn't it?

Because this comment is added by us 😂

@CrazyWolf13 commented on GitHub (Sep 30, 2025): @bwh Yeah that's correct isn't it? Because this comment is added by us 😂
OVERLORD commented 2026-02-05 01:36:02 +03:00
Author
Owner
Copy Link

@bwh commented on GitHub (Sep 30, 2025):

@CrazyWolf13 that much I know already, I wasn't sure Zabbix was included in your task here , so thought it'd be helpful to add it :)

@bwh commented on GitHub (Sep 30, 2025): @CrazyWolf13 that much I know already, I wasn't sure Zabbix was included in your task here , so thought it'd be helpful to add it :)
OVERLORD commented 2026-02-05 01:36:08 +03:00
Author
Owner
Copy Link

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

zabbix is already deb13 package, you only need to upgrade your lxc

@MickLesk commented on GitHub (Sep 30, 2025): zabbix is already deb13 package, you only need to upgrade your lxc
OVERLORD commented 2026-02-05 01:36:16 +03:00
Author
Owner
Copy Link

@bwh commented on GitHub (Sep 30, 2025):

zabbix is already deb13 package, you only need to upgrade your lxc

Thanks for the help guys, but the error above is what I get when I run "update" from within the Zabbix LXC, I assumed it would update itself however needed when I run the command. The Zabbix LXC page suggests the LXC to be updatable.
Am I missing something?

@bwh commented on GitHub (Sep 30, 2025): > zabbix is already deb13 package, you only need to upgrade your lxc Thanks for the help guys, but the error above is what I get when I run "update" from within the Zabbix LXC, I assumed it would update itself however needed when I run the command. The Zabbix LXC page suggests the LXC to be updatable. Am I missing something?
OVERLORD commented 2026-02-05 01:36:23 +03:00
Author
Owner
Copy Link

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

you need to upgrade your lxc, as i said. apt-get update && apt-get upgrade .... -> https://github.com/community-scripts/ProxmoxVE/discussions/7489

@MickLesk commented on GitHub (Sep 30, 2025): you need to upgrade your lxc, as i said. apt-get update && apt-get upgrade .... -> https://github.com/community-scripts/ProxmoxVE/discussions/7489
OVERLORD commented 2026-02-05 01:36:25 +03:00
Author
Owner
Copy Link

@burgerga commented on GitHub (Sep 30, 2025):

@CrazyWolf13 With these changes (suggested by the guacomole people) I have a functional guacomole in Debian 13: 6148649911
(however I'm not a power user, so maybe someone else can test it better)
I'm not sure if we should upgrade though, as the guacamole people consider support for freerdp3 experimental because there are some problems with the remoteapp functionality (see https://issues.apache.org/jira/browse/GUACAMOLE-1026).

@burgerga commented on GitHub (Sep 30, 2025): @CrazyWolf13 With these changes (suggested by the guacomole people) I have a functional guacomole in Debian 13: https://github.com/burgerga/ProxmoxVE/commit/61486499115cb51884ef92da2b27e0cd6ed4930c (however I'm not a power user, so maybe someone else can test it better) I'm not sure if we should upgrade though, as the guacamole people consider support for freerdp3 experimental because there are some problems with the remoteapp functionality (see https://issues.apache.org/jira/browse/GUACAMOLE-1026).
OVERLORD commented 2026-02-05 01:36:28 +03:00
Author
Owner
Copy Link

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

Push it to VE ^^ then we can see if anyone report issues with new installs

@MickLesk commented on GitHub (Sep 30, 2025): Push it to VE ^^ then we can see if anyone report issues with new installs
OVERLORD commented 2026-02-05 01:36:33 +03:00
Author
Owner
Copy Link

@burgerga commented on GitHub (Oct 14, 2025):

Is there a policy/preference on using deb822 style sources for Debian 13, as mentioned in the debian upgrade instructions?

@burgerga commented on GitHub (Oct 14, 2025): Is there a policy/preference on using deb822 style sources for Debian 13, as mentioned in the [debian upgrade instructions](https://www.debian.org/releases/trixie/release-notes/upgrading.en.html#preparing-apt-sources-files)?
OVERLORD commented 2026-02-05 01:36:37 +03:00
Author
Owner
Copy Link

@CrazyWolf13 commented on GitHub (Oct 14, 2025):

@burgerga deb13 (apt3.0) uses deb822, so yes :)

@CrazyWolf13 commented on GitHub (Oct 14, 2025): @burgerga deb13 (apt3.0) uses deb822, so yes :)
OVERLORD commented 2026-02-05 01:36:40 +03:00
Author
Owner
Copy Link

@SirLokiRichards commented on GitHub (Oct 20, 2025):

Any script that uses MySQL appears to be affected.
no available dist files for trixie in public MySQL repo urls.

some known scripts affected (but not limited to)

  1. https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/mysql.sh
  2. https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/managemydamnlife.sh

known workaround:
updating each CT script to use bookworm for now

Changes made:
'update var_version="${var_version:-13}"' to be 'var_version="${var_version:-12}"'

@SirLokiRichards commented on GitHub (Oct 20, 2025): Any script that uses MySQL appears to be affected. no available dist files for trixie in public MySQL repo urls. some known scripts affected (but not limited to) 1. https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/mysql.sh 2. https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/managemydamnlife.sh known workaround: updating each CT script to use bookworm for now Changes made: 'update var_version="${var_version:-13}"' to be 'var_version="${var_version:-12}"'
OVERLORD commented 2026-02-05 01:36:42 +03:00
Author
Owner
Copy Link

@samwathegreat commented on GitHub (Oct 23, 2025):

You guys are awesome!

Quick question:

For the containers that use repositories that don't have Trixie support yet, or the ones that have signature issues (reject within a year), once those issues are resolved or the Trixie repos are released, will the script automatically adjust accordingly when you run 'update'?

I'm noticing that some containers upgraded to Trixie or even brand new installs using trixie still use some bookworm repos or have the signature error messages.

Thanks!

@samwathegreat commented on GitHub (Oct 23, 2025): You guys are awesome! Quick question: For the containers that use repositories that don't have Trixie support yet, or the ones that have signature issues (reject within a year), once those issues are resolved or the Trixie repos are released, will the script automatically adjust accordingly when you run 'update'? I'm noticing that some containers upgraded to Trixie or even brand new installs using trixie still use some bookworm repos or have the signature error messages. Thanks!
OVERLORD commented 2026-02-05 01:36:44 +03:00
Author
Owner
Copy Link

@jlacour-git commented on GitHub (Oct 24, 2025):

Regarding the scripts known to have problems with php modules: just tried „phpIPAM“, it also has problems as the modules like mySQL are not installed for php 8.4.

@jlacour-git commented on GitHub (Oct 24, 2025): Regarding the scripts known to have problems with php modules: just tried „phpIPAM“, it also has problems as the modules like mySQL are not installed for php 8.4.
OVERLORD commented 2026-02-05 01:36:46 +03:00
Author
Owner
Copy Link

@CrazyWolf13 commented on GitHub (Oct 24, 2025):

@samwathegreat The goal is to "fix" them, but that requires a lot of code, a lot of changes and help from the community, by submitting bugs and possibly submitting PRs.

@CrazyWolf13 commented on GitHub (Oct 24, 2025): @samwathegreat The goal is to "fix" them, but that requires a lot of code, a lot of changes and help from the community, by submitting bugs and possibly submitting PRs.
OVERLORD commented 2026-02-05 01:36:50 +03:00
Author
Owner
Copy Link

@BunpGhost commented on GitHub (Oct 28, 2025):

Hi, recently made a new install of Omada Controller. It went with trixie, all good.
Today tried running the update and have an error.
The source: /etc/apt/sources.list.d/mongodb-org-7.0.list keeps being added up to the list via the scrip in the https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/omada.sh because mongo version is hard-coded to 7.0, but the installer uses 8.0.
I don't know how to fix this.. Can someone help?

@BunpGhost commented on GitHub (Oct 28, 2025): Hi, recently made a new install of Omada Controller. It went with trixie, all good. Today tried running the update and have an error. The source: `/etc/apt/sources.list.d/mongodb-org-7.0.list` keeps being added up to the list via the scrip in the `https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/omada.sh` because mongo version is hard-coded to 7.0, but the installer uses 8.0. I don't know how to fix this.. Can someone help?
OVERLORD commented 2026-02-05 01:36:53 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Oct 28, 2025):

Create an issue and we Bump to 8

@MickLesk commented on GitHub (Oct 28, 2025): Create an issue and we Bump to 8
OVERLORD commented 2026-02-05 01:37:00 +03:00
Author
Owner
Copy Link

@diskworld3 commented on GitHub (Oct 30, 2025):

I'm guessing my issues are related to this from reading some of the commentary, but I've tried today to install these 3 scripts and all just hang after starting, I don't get any errors or messages, nothing in the system log, just hangs until I kill it.

https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/homebridge.sh
https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/myip.sh
https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/netbox.sh https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/myspeed.sh

@diskworld3 commented on GitHub (Oct 30, 2025): I'm guessing my issues are related to this from reading some of the commentary, but I've tried today to install these 3 scripts and all just hang after starting, I don't get any errors or messages, nothing in the system log, just hangs until I kill it. https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/homebridge.sh https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/myip.sh https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/netbox.sh https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/myspeed.sh
OVERLORD commented 2026-02-05 01:37:05 +03:00
Author
Owner
Copy Link

@CrazyWolf13 commented on GitHub (Oct 30, 2025):

@diskworld3 no, please create an issue and fill out the correct details or report in our discord, thanks.

@CrazyWolf13 commented on GitHub (Oct 30, 2025): @diskworld3 no, please create an issue and fill out the correct details or report in our discord, thanks.
OVERLORD commented 2026-02-05 01:37:07 +03:00
Author
Owner
Copy Link

@famewolf commented on GitHub (Nov 21, 2025):

I created this issue (including a fixed script) before I saw this thread for the home assistant os script.

https://github.com/community-scripts/ProxmoxVE/issues/9339

@famewolf commented on GitHub (Nov 21, 2025): I created this issue (**including a fixed script)** before I saw this thread for the home assistant os script. https://github.com/community-scripts/ProxmoxVE/issues/9339
OVERLORD commented 2026-02-05 01:37:11 +03:00
Author
Owner
Copy Link

@stevefxp1 commented on GitHub (Dec 16, 2025):

Hello all,

I am still seeing that if I use the Proxmox post-install script that it does not run as it did under Proxmox 8. For example the application of updates just hangs and it does not run. I literally have to kick it off in a separate window. Has anyone looked into this yet?

Thanks,
Steve

@stevefxp1 commented on GitHub (Dec 16, 2025): Hello all, I am still seeing that if I use the Proxmox post-install script that it does not run as it did under Proxmox 8. For example the application of updates just hangs and it does not run. I literally have to kick it off in a separate window. Has anyone looked into this yet? Thanks, Steve
OVERLORD commented 2026-02-05 01:37:15 +03:00
Author
Owner
Copy Link

@pafade89 commented on GitHub (Jan 8, 2026):

LXC that need testing to fruther analyse the cause of a failing update:

  • Bar-Assistant
  • phpipam
  • Adventurelog
  • Booklore (seems to start, but shows a generic nginx welcome page?)
  • Calibre web
  • Huntarr

Same here for Booklore.

@pafade89 commented on GitHub (Jan 8, 2026): > LXC that need testing to fruther analyse the cause of a failing update: > > * Bar-Assistant > * phpipam > * Adventurelog > * Booklore (seems to start, but shows a generic nginx welcome page?) > * Calibre web > * Huntarr Same here for Booklore.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Implemented in VED waiting push to Main
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
in project pipeline
invalid
investigation
json
maintenance
needs triage
new script
new script
nice to have
not a script issue
not planned
organization
pull-request
Mirrored from GitHub Pull Request
 question
refactor
rename script
security
update script
website
wontdo
🛑 Failure to comply with the guidelines
No Label investigation
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#1563
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?