Debian 13 Upgrade for existing LXC

[CrazyWolf13]

Looking for Debian 13 Upgrade Testers

We are currently looking for testers for Debian 13 (Trixie) in our LXC scripts.
At this stage, support will most likely only work on Proxmox VE 9 (currently 9.0). Proxmox VE 8.x is not targeted for Debian 13 support.

Caution

The following post is intended as Beta-test, proceed with Caution and ensure full Backups are created.

The ideal commands we recommand to update a Debian 12 (Bookworm) LXC to Debian 13 Trixie:

What it does

This will install the latest updates, install screen (kinda like a virtual terminal) this makes sure the update continues to run even if the ssh session would get interrupted, the user can just run screen -r to re-attach to the update process.
After that it will rewrite the sources to Trixie and upgrade everything.
Then existin source files will be rewritten to the new deb822 format.

Caution

Proceed with Caution, this may break your LXC, so be sure to create proper Backups beforehand.

Important

Check out this thread for more info on what LXC have issues upgrading and keep up to date on their status:
#7332

apt update apt install screen -y apt upgrade -y sed -i 's/bookworm/trixie/g' /etc/apt/sources.list apt update screen apt dist-upgrade apt autoremove apt autoclean apt modernize-sources apt update reboot

Tip

After the upgrade the MOTD (Message displayed on SSH login, will still show Debian 12, check out this guide on how to regenerate it.
#7227

Note

For new installations of a LXC, check this thread:
#7485

Warning

Please only report the apps that don't work. as otherwise this discussion get's a bit flooded.
Thanks!

We would appreciate your feedback
Simply let us know which scripts are working and which are not.
We will continuously clean up and update this post based on your reports.

Thank you for helping us move Debian 13 support forward 🙌
CrazyWolf13 (Community-Scripts-Team)

[oOStroudyOo]

Here are my findings from my server, all of these apps are in separate LXCs..

These apps (LXCs) have been pre-built via the community script (These are not fresh installs), and run fine after updating from Debian 12 to Debian 13 after following the commands above:

• Radarr
• Docker
• Uptime Kuma
• Sonarr
• Emby
• Pulse
• Jellyseerr
• Mealie
• Cloudflared
• FileBrowser Quantum
• Tdarr
• Cross-Seed
• Notifiarr - (Update script fails, it returns No Notifiarr Installation Found!)
• Cleanuparr
• Planka
• Apt-Cacher-NG

Note: Except for Notifarr, the update script run successfully on all LXCs, however I didn't actually have any apps that required updating so this has not been fully tested.

These apps (LXCs) were NOT pre-built via community scripts (as I prefer the beta version) but still run fine on Debian 13:

• Whisparr

These apps (LXCs) have been pre-built via the community script (These are not fresh installs) and do not work when updating to Debian 13:

• Huntarr
• Change Detection

For future reference, Unpackerr from the project board also runs fine on Debian 13.

I hope this helps.
I can gather more info on Huntarr and Change Detection if required.

Thanks.

[Aloe-recite]

these works for me (some extensively tested more than others):

• Sonarr
• Prowlarr
• ADGuard Home
• Gitea
• Karakeep
• Caddy
• Audiobookshelf
• Homepage
• Kavita
• Cronicle
• Peanut
• Homebox

NOT working:

• Adventurelog
• Changedetection
• Booklore (seems to start, but shows a generic nginx welcome page?)
• Calibre web

[jonnewman85]

These do not work for me after Debian 13 upgrade inside the LXC:

• WallOS
• Bar-Assistant
• phpipam

phpipam and WallOS seem to be Apache2/PHP module issues causing Apache2 to not load. Bar-Assistant will not connect to the API after upgrade (checked IPs in config, all correct)

[CrazyWolf13]

@jonnewman85 check out the linked github issue, it contains a fix for wallos.

[dxxxm]

LCX upgrade to Debian 13 worked OK:

• apt-cacher-ng
• pihole
• esphome
• paperless-ngx
• grafana
• influxdb
• deCONZ

[SinnedNima]

LCX upgrade to Debian 13 worked OK:

* apt-cacher-ng * pihole * esphome * paperless-ngx * grafana * influxdb * deCONZ 

couldn't get it to work with my paperless-ngx container. Prompted me to upgrade postgresql - i ran it with and without the upgrade, still not working.
Docker was painless so far. Will try the other containers one by one.

[PedroBuffon]

Grafana update script expects "/etc/apt/sources.list.d/grafana.list" not "/etc/apt/sources.list.d/grafana.sources" as debian 13 source

[vhsdream]

So I know we've established that the Homepage LXC is safe to update, but I've been running it for so long I forgot it was on Bullseye. I was able to upgrade to Bookworm, then reboot and upgrade to Trixie just fine.

[ksj9877us]

Heimdall-Dashboard no longer works when I try to load the webpage.

[CrazyWolf13]

@ksj9877us can you add some sort of logs or something like that?

[Seqway]

Technitium DNS works perfect with this script. Updated to Trixie without any problem
(except at the login still says Debian 12)

[MickLesk]

#7227

[kriss0707]

Zabbix seems to work (no postgresql upgrade).

I need to install the PostgreSQL database module for PHP package after all to recover database connection
apt install php-pgsql

After rebooting, the update command shows

⏳ Stopping ServicesFailed to stop zabbix-agent.service: Unit zabbix-agent.service not loaded.

[ERROR] in line 45: exit code 0: while executing command systemctl stop zabbix-server $AGENT_SERVICE

[CrazyWolf13]

@kriss0707 all php modules need to be reinstalled view here on how to do this: #7332

[summoningpixels]

these are working fine for me:

• adguard
• stirling-pdf
• tandoor
• debian
• readeck
• wireguard
• watcharr
• commafeed

I do get the "Policy will reject signature within a year" message for:
Tandoor: Warning: https://deb.nodesource.com/node_22.x/dists/nodistro/InRelease: Policy will reject signature within a year, see --audit for details Notice: Missing Signed-By in the sources.list(5) entry for 'https://apt.postgresql.org/pub/repos/apt'
CommaFeed Warning: https://repos.azul.com/zulu/deb/dists/stable/InRelease: Policy will reject signature within a year, see --audit for details Notice: Missing Signed-By in the sources.list(5) entry for 'https://repos.azul.com/zulu/deb'
Watcharr: Warning: https://deb.nodesource.com/node_22.x/dists/nodistro/InRelease: Policy will reject signature within a year, see --audit for details

Later edit: Vaultwarden has been fine too

[summoningpixels]

@CrazyWolf13

Output:

root@commafeed:~# cat /etc/apt/sources.list.d/adoptium.sources cat: /etc/apt/sources.list.d/adoptium.sources: No such file or directory root@commafeed:~# cat /etc/apt/sources.list.d/adoptium.lis cat: /etc/apt/sources.list.d/adoptium.lis: No such file or directory 

Modernizing sources worked for /etc/apt/sources.list.d/adoptium.sources

I ran through the steps again, if that's what you meant, and now:

root@commafeed:~# apt update Hit:1 http://deb.debian.org/debian trixie InRelease Hit:2 http://security.debian.org trixie-security InRelease Hit:3 http://deb.debian.org/debian trixie-updates InRelease Get:4 https://packages.adoptium.net/artifactory/deb trixie InRelease [7,503 B] Hit:5 https://repos.azul.com/zulu/deb stable InRelease Err:5 https://repos.azul.com/zulu/deb stable InRelease Sub-process /usr/bin/sqv returned an error code (1), error message is: Missing key 27BC0C8CB3D81623F59BDADCB1998361219BD9C9, which is needed to verify signature. Fetched 7,503 B in 1s (11.2 kB/s) All packages are up to date. Warning: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list.d/adoptium.list:1 and /etc/apt/sources.list.d/adoptium.sources:1 Warning: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list.d/adoptium.list:1 and /etc/apt/sources.list.d/adoptium.sources:1 Warning: Target Translations (main/i18n/Translation-en_US) is configured multiple times in /etc/apt/sources.list.d/adoptium.list:1 and /etc/apt/sources.list.d/adoptium.sources:1 Warning: Target Translations (main/i18n/Translation-en) is configured multiple times in /etc/apt/sources.list.d/adoptium.list:1 and /etc/apt/sources.list.d/adoptium.sources:1 Warning: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. OpenPGP signature verification failed: https://repos.azul.com/zulu/deb stable InRelease: Sub-process /usr/bin/sqv returned an error code (1), error message is: Missing key 27BC0C8CB3D81623F59BDADCB1998361219BD9C9, which is needed to verify signature. Warning: Failed to fetch https://repos.azul.com/zulu/deb/dists/stable/InRelease Sub-process /usr/bin/sqv returned an error code (1), error message is: Missing key 27BC0C8CB3D81623F59BDADCB1998361219BD9C9, which is needed to verify signature. Warning: Some index files failed to download. They have been ignored, or old ones used instead. Warning: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list.d/adoptium.list:1 and /etc/apt/sources.list.d/adoptium.sources:1 Warning: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list.d/adoptium.list:1 and /etc/apt/sources.list.d/adoptium.sources:1 Warning: Target Translations (main/i18n/Translation-en_US) is configured multiple times in /etc/apt/sources.list.d/adoptium.list:1 and /etc/apt/sources.list.d/adoptium.sources:1 Warning: Target Translations (main/i18n/Translation-en) is configured multiple times in /etc/apt/sources.list.d/adoptium.list:1 and /etc/apt/sources.list.d/adoptium.sources:1 Notice: Missing Signed-By in the sources.list(5) entry for 'https://repos.azul.com/zulu/deb' 

and here's adoptium.sources after modernizing sources:

root@commafeed:~# cat /etc/apt/sources.list.d/adoptium.sources Types: deb URIs: https://packages.adoptium.net/artifactory/deb/ Suites: trixie Components: main Signed-By: /etc/apt/trusted.gpg.d/adoptium.gpg root@commafeed:~# cat cat /etc/apt/sources.list.d/adoptium.lis cat: cat: No such file or directory cat: /etc/apt/sources.list.d/adoptium.lis: No such file or directory 

[CrazyWolf13]

@summoningpixels
You were missing a "t" at the end of list. Though you don't have to rerun those commands.

You should be fine to remove this:
/etc/apt/sources.list.d/adoptium.list

Can you send the outputs of the following:

ls /etc/apt/sources.list.d/

And also can you remove all the files related to azul zulu inside of /etc/apt/sources.list.d/ directory?

Then run apt update again and ensure with apt show temurin-17-jdk it's installed

[summoningpixels]

@CrazyWolf13 that did it, everything is clean now. apt status doesn't work, but I can confirm temurin-17-jdk is installed. Thanks for all the help with this!

[CrazyWolf13]

@summoningpixels awesome!

Can you share what files you had to remove from the azul zulu repo? So we can maybe do this via script?

[summoningpixels]

@CrazyWolf13 it was zulu-openjdk.list.bak and zulu-openjdk.sources

[stevang]

sabnzbd LXC Debian12 > 13 Upgrade

it failed to start the sabnzbd systemd service due to

Not all required Python modules are available, please check requirements.txt Missing module: sabctools You can read more at: https://sabnzbd.org/wiki/installation/install-off-modules If you still experience problems, remove all .pyc files in this folder and subfolders 

i had to remove the virtual environment

 cd /opt/sabnzbd rm -rf venv 

EDIT - Correct solution over here: #7489 (reply in thread)

.
.
.
and recreate it, still being in the /opt/sabnzbd folder
python3 -m venv venv

activate Venv
source venv/bin/activate

install requirements

pip install --upgrade pip pip install -r requirements.txt 

and close the Venv
deactivate

after restarting the sabnzbd systemd service, sabnzbd should run again

systemctl stop sabnzbd.service systemctl start sabnzbd.service systemctl status sabnzbd.service 

[MickLesk]

sabnzbd doesnt Work with python3 venv, so you Break the next Update

sabnzbd Runs with uv

[stevang]

how about that to rebuild venv? is that good for future updates?

rm -rf /opt/sabnzbd/venv uv venv /opt/sabnzbd/venv uv pip install -r /opt/sabnzbd/requirements.txt --python=/opt/sabnzbd/venv/bin/python 

[MickLesk]

Yeah

uv venv /opt/sabnzbd/venv
uv pip install --upgrade pip --python=/opt/sabnzbd/venv/bin/python
uv pip install -r /opt/sabnzbd/requirements.txt --python=/opt/sabnzbd/venv/bin/python

[Seqway]

Nginx Proxy Manager works perfect with this script. Updated to Trixie without any problem
(except at the login still says Debian 12) --> can be solved with this #7227

[ernie95]

The update to Debian 13 is not working for
MotionEye NVR LXC (LXC with Debian 12.12)

After update service is not accessible

[ernie95]

The update works for Resilio Sync LXC. No issue

The update works for Gotify LXC. No issue

The update works for Vaultwarden LXC. No issue

The update works for Adguardhome LXC (+ Stork + isc-kea-dhcp installed in the LXC). No issue (migration of postgresql from 15 to 17).

thanks for this guidance

[AntoninoBonanno]

I tried upgrading Nginx Proxy Manager to Trixie, but when I restart the container, it doesn't start.

Te update commands:

apt update apt install screen -y apt upgrade -y sed -i 's/bookworm/trixie/g' /etc/apt/sources.list apt update screen apt dist-upgrade apt autoremove apt autoclean apt modernize-sources apt update reboot 

After reboot command the LXC don't start

[AntoninoBonanno]

No, i have the Proxmox v9.0.11

[MickLesk]

That say nothing. "pve-container" is relevant

[MickLesk]

And you see Output If you start the Container with pct. Then you see whats broken

[AntoninoBonanno]

There were packages to update in proxmox, now I managed to update Nginx Proxy Manager (from v2.12.6 to v2.13.1)

[MickLesk]

👍

[Dirty504]

Updated a bunch of containers using this script and most worked great. A problematic culprit that has already been mentioned is Changedetection... and a couple that haven't been mentioned are Bazarr and Privatebin. About to troubleshoot them now.

[CrazyWolf13]

@Dirty504 check this issue, I have changedetection working fine on deb13:

#7332

[mintert91]

with evcc I had issues, because "/etc/apt/sources.list.d/evcc-stable.list" could not be found. there was only "/etc/apt/sources.list.d/evcc-stable.list.bak" available.
after running
curl -1sLf 'https://dl.evcc.io/public/evcc/stable/setup.deb.sh' | sudo -E bash it seems to run smoothly.

[CrazyWolf13]

@mintert91 can you try removing both old files and checking again:

rm /etc/apt/sources.list.d/evcc-stable.list.bak rm /etc/apt/sources.list.d/evcc-stable.list apt update

Though please take a backup beforehand, thanks!

PR is up: #9057

[mintert91]

Seems fine.

apt update Hit:1 http://deb.debian.org/debian trixie InRelease Get:2 http://deb.debian.org/debian trixie-updates InRelease [47.3 kB] Get:3 http://security.debian.org trixie-security InRelease [43.4 kB] Get:4 http://security.debian.org trixie-security/main amd64 Packages [69.7 kB] Get:5 http://security.debian.org trixie-security/main Translation-en [45.5 kB] Get:6 https://dl.evcc.io/public/evcc/stable/deb/debian bookworm InRelease Fetched 218 kB in 1s (409 kB/s) All packages are up to date. 

ls -al /etc/apt/sources.list.d total 16 drwxr-xr-x 2 root root 4096 Nov 12 08:20 . drwxr-xr-x 9 root root 4096 Nov 11 11:51 .. -rw-r--r-- 1 root root 572 Nov 11 11:51 debian.sources -rw-r--r-- 1 root root 146 Nov 11 11:51 evcc-stable.sources 

=== /etc/apt/sources.list.d/debian.sources === # Modernized from /etc/apt/sources.list Types: deb URIs: http://deb.debian.org/debian/ Suites: trixie Components: main contrib Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg # Modernized from /etc/apt/sources.list Types: deb URIs: http://deb.debian.org/debian/ Suites: trixie-updates Components: main contrib Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg # Modernized from /etc/apt/sources.list Types: deb URIs: http://security.debian.org/ Suites: trixie-security Components: main contrib Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg === /etc/apt/sources.list.d/evcc-stable.sources === Types: deb URIs: https://dl.evcc.io/public/evcc/stable/deb/debian/ Suites: bookworm Components: main Signed-By: /etc/apt/keyrings/evcc-stable.gpg 

[CrazyWolf13]

@mintert91 perfect, thanks!

Could you try changing the value bookworm to trixie and run apt update again, to check if the trixie repo works?

sed -i 's/bookworm/trixie/' /etc/apt/sources.list.d/evcc-stable.sources apt update

[mintert91]

good hint.

apt update Hit:1 http://deb.debian.org/debian trixie InRelease Hit:2 http://security.debian.org trixie-security InRelease Hit:3 http://deb.debian.org/debian trixie-updates InRelease Get:4 https://dl.evcc.io/public/evcc/stable/deb/debian trixie InRelease Get:5 https://dl.evcc.io/public/evcc/stable/deb/debian trixie/main amd64 Packages [28.1 kB] Fetched 39.8 kB in 0s (79.9 kB/s) All packages are up to date. 

[CrazyWolf13]

alright for anyone in the future, this is fixed in evcc update script, so after updating the LXC, just run update (This will update evcc sources and evcc version)

[i4mr000t]

upgraded nginx proxy manager lxc to debian 13.

its running but login at webgui throws bad gateway.

pve 9.0.11
nginxproxymanager v12

[i4mr000t]

I tried it twice. On the first attempt, I did an update afterwards, and then I got an error: "The API is not healthy. We'll keep checking and hope to be back soon!"

On the second attempt, I only installed Debian 13, and here I got a "bad gateway" error when trying to log in.

[CrazyWolf13]

@i4mr000t
interesting I was not ablt to replicate this behaviour, could you send the logs from npm service?

journalctl -u npm | tail -n 400

Redact any secrets or similar things before posting here.

Could you share screenshots of both error messages?

[i4mr000t]

Upgrade to Debian 13 (Bad Gateway on Login):

debian13.log

After the LXC Update:

npmupdate.log

I think the DNSMulti Plugin is the one who is causing this but i dont know.

[CrazyWolf13]

@i4mr000t Yes, that is most likely something with some dns plugins, can you try this:

/opt/certbot/bin/pip install setuptools # Restart NPM systemctl restart npm

if that does not work, can you also try:

apt update apt install python3-setuptools systemctl restart npm

[i4mr000t]

@CrazyWolf13

Sorry but your commands didn´t work. Same errors as before but i found a solution/workaround on ipv64-forum (https://v64.tech/t/nginx-proxy-manager-dnschallenge-ipv64-debian-13-fail/4177/7).

In Short:

1. Create a new LXC Nginx Proxy Manager with helper script
2. Change lxc ressources to 6GB Memory and 4 Cores (only for the build process you can set stock setting after executing the code.)
3. Run this code in lxc container:

#venv aktivieren source /opt/certbot/bin/activate apt-get update && apt-get install -y golang apt update && apt install -y build-essential git pip install --no-cache-dir setuptools-golang==2.9.0 export CGO_ENABLED=1 export GO111MODULE=on pip install --no-build-isolation --no-cache-dir certbot-dns-multi 

4. Now everthing is working correctly
5. Revert back to stock ressources e.g. 2GB Memory & 2 Cores