Debian 13 Upgrade for existing LXC #7489
Replies: 23 comments 66 replies
-
|
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:
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: 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: For future reference, Unpackerr from the project board also runs fine on Debian 13. I hope this helps. Thanks. |
Beta Was this translation helpful? Give feedback.
-
|
these works for me (some extensively tested more than others):
NOT working:
|
Beta Was this translation helpful? Give feedback.
-
|
These do not work for me after Debian 13 upgrade inside the LXC:
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) |
Beta Was this translation helpful? Give feedback.
-
|
@jonnewman85 check out the linked github issue, it contains a fix for wallos. |
Beta Was this translation helpful? Give feedback.
-
|
LCX upgrade to Debian 13 worked OK:
|
Beta Was this translation helpful? Give feedback.
-
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. |
Beta Was this translation helpful? Give feedback.
-
|
Grafana update script expects "/etc/apt/sources.list.d/grafana.list" not "/etc/apt/sources.list.d/grafana.sources" as debian 13 source |
Beta Was this translation helpful? Give feedback.
-
|
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. |
Beta Was this translation helpful? Give feedback.
-
|
Heimdall-Dashboard no longer works when I try to load the webpage. |
Beta Was this translation helpful? Give feedback.
-
|
@ksj9877us can you add some sort of logs or something like that? |
Beta Was this translation helpful? Give feedback.
-
|
I managed to make Heimdall work: |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for this. It didn't work after running the additional commands above, but I did find the reason in the logs. Dec 01 09:47:07 heimdall-dashboard systemd[1]: Started heimdall.service - Heimdall. After installing php-zip, it works correctly. |
Beta Was this translation helpful? Give feedback.
-
|
Technitium DNS works perfect with this script. Updated to Trixie without any problem |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
This comment has been minimized.
This comment has been minimized.
-
|
Zabbix seems to work (no postgresql upgrade). I need to install the PostgreSQL database module for PHP package after all to recover database connection 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 |
Beta Was this translation helpful? Give feedback.
-
|
@kriss0707 all php modules need to be reinstalled view here on how to do this: #7332 |
Beta Was this translation helpful? Give feedback.
-
@CrazyWolf13 Seems nothing else than the mentioned I just updated my Debian 12 Zabbix container to Debian 13 with the procedure outlined above, then installed php-pgsql as mentioned by @kriss0707, and all is good. Unless I misunderstand something, looking at https://github.com/community-scripts/ProxmoxVE/blob/main/install/zabbix-install.sh line 26 I find: Now trying to reinstall those two PHP modules zabbix-frontend-php and php8.4-pgsql shows the following: Or did you refer to PHP modules in general, not for the Zabbix helper script specifically? |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
@CrazyWolf13 I did. But seems we are going in circles. According to @kriss0707 s0707 only |
Beta Was this translation helpful? Give feedback.
-
|
these are working fine for me:
I do get the "Policy will reject signature within a year" message for: Later edit: Vaultwarden has been fine too |
Beta Was this translation helpful? Give feedback.
-
|
Output: Modernizing sources worked for I ran through the steps again, if that's what you meant, and now: and here's adoptium.sources after modernizing sources: |
Beta Was this translation helpful? Give feedback.
-
|
@summoningpixels You should be fine to remove this: Can you send the outputs of the following:
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 |
Beta Was this translation helpful? Give feedback.
-
|
@CrazyWolf13 that did it, everything is clean now. |
Beta Was this translation helpful? Give feedback.
-
|
@summoningpixels awesome! Can you share what files you had to remove from the azul zulu repo? So we can maybe do this via script? |
Beta Was this translation helpful? Give feedback.
-
|
@CrazyWolf13 it was |
Beta Was this translation helpful? Give feedback.
-
|
sabnzbd LXC Debian12 > 13 Upgrade it failed to start the sabnzbd systemd service due to i had to remove the virtual environment EDIT - Correct solution over here: #7489 (reply in thread) . activate Venv install requirements and close the Venv after restarting the sabnzbd systemd service, sabnzbd should run again |
Beta Was this translation helpful? Give feedback.
-
|
sabnzbd doesnt Work with python3 venv, so you Break the next Update sabnzbd Runs with uv |
Beta Was this translation helpful? Give feedback.
-
|
how about that to rebuild venv? is that good for future updates? |
Beta Was this translation helpful? Give feedback.
-
|
Yeah uv venv /opt/sabnzbd/venv |
Beta Was this translation helpful? Give feedback.
-
|
Nginx Proxy Manager works perfect with this script. Updated to Trixie without any problem |
Beta Was this translation helpful? Give feedback.
-
|
The update to Debian 13 is not working for After update service is not accessible |
Beta Was this translation helpful? Give feedback.
-
|
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 |
Beta Was this translation helpful? Give feedback.
-
|
I tried upgrading Te update commands: After reboot command the LXC don't start |
Beta Was this translation helpful? Give feedback.
-
|
No, i have the Proxmox v9.0.11 |
Beta Was this translation helpful? Give feedback.
-
|
That say nothing. "pve-container" is relevant |
Beta Was this translation helpful? Give feedback.
-
|
And you see Output If you start the Container with pct. Then you see whats broken |
Beta Was this translation helpful? Give feedback.
-
|
There were packages to update in proxmox, now I managed to update 
|
Beta Was this translation helpful? Give feedback.
-
|
👍 |
Beta Was this translation helpful? Give feedback.
This comment was marked as off-topic.
This comment was marked as off-topic.
-
|
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. |
Beta Was this translation helpful? Give feedback.
-
|
@Dirty504 check this issue, I have changedetection working fine on deb13: |
Beta Was this translation helpful? Give feedback.
-
|
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. |
Beta Was this translation helpful? Give feedback.
-
|
@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 updateThough please take a backup beforehand, thanks! PR is up: #9057 |
Beta Was this translation helpful? Give feedback.
-
|
Seems fine. |
Beta Was this translation helpful? Give feedback.
-
|
@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 |
Beta Was this translation helpful? Give feedback.
-
|
good hint. |
Beta Was this translation helpful? Give feedback.
-
|
alright for anyone in the future, this is fixed in evcc update script, so after updating the LXC, just run |
Beta Was this translation helpful? Give feedback.
-
|
upgraded nginx proxy manager lxc to debian 13. its running but login at webgui throws bad gateway. pve 9.0.11 |
Beta Was this translation helpful? Give feedback.
-
|
@i4mr000t journalctl -u npm | tail -n 400Redact any secrets or similar things before posting here. Could you share screenshots of both error messages? |
Beta Was this translation helpful? Give feedback.
-
|
Upgrade to Debian 13 (Bad Gateway on Login): 
After the LXC Update: 
I think the DNSMulti Plugin is the one who is causing this but i dont know. |
Beta Was this translation helpful? Give feedback.
-
|
@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 npmif that does not work, can you also try: apt update
apt install python3-setuptools
systemctl restart npm |
Beta Was this translation helpful? Give feedback.
-
|
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:
|
Beta Was this translation helpful? Give feedback.
-
|
@MickLesk do we want to include the installation of this module or do we skipt this in the real script? I think we can't handle each plugin? |
Beta Was this translation helpful? Give feedback.
-
|
I have a very strange error in my last LXC that I want to bring to Trixie (six have worked without any problem). That is a debian 12 installation with XFCE as desktop and jdownloader 2 and java. After doing all the above mentioned steps, the LXC starts, but CPU only uses 0.4% and the console stays black, no reaction, no login possible. Nothing happens. What problem could this be? |
Beta Was this translation helpful? Give feedback.
-
|
@carsten-h I'm unsure which of our scripts are installing XFCE, jdonloader and java by default, unless manually changed by a user, please tell me which script of ours is not working? |
Beta Was this translation helpful? Give feedback.
-
|
Oh, sorry that wasn't clear enough. Now I tried the commands above in this thread: sed -i 's/bookworm/trixie/g' /etc/apt/sources.list screen apt dist-upgrade It seems to have everything updated, it took a while. But the LXC isn't really starting. Nothing can be seen inside the console. |
Beta Was this translation helpful? Give feedback.
-
|
IPv6 disable isn't respected after upgrading from debian12 to debian13 |
Beta Was this translation helpful? Give feedback.
-
|
That disable the whole ipv6 Management inside the container. Not the Network Management. So as hint, many Programs doesnt Work (correctly) after this, like nginx. With all - it disable the full ipv6 Logic, so the internal given ipv6 from proxmox too. |
Beta Was this translation helpful? Give feedback.
-
|
That's incorrect; that's not how Proxmox is handling IPv6. If you don't provide an IPv6 address in the PVE-UI, then it's up to the container to handle its own IPv6, so disabling IPv6 prevents it from establishing a local link address. My nginx instance has worked flawlessly with IPv6 disabled on PVE8.1 and Deb12 based LXC for about a year now. NginxProxyManager has also worked flawlessly with IPv6 disabled at the OS level. |
Beta Was this translation helpful? Give feedback.
-
|
Then make an PR against proxmoxVED (new core), with the for you perfect Solution. Lets Take a Look If some Installs Break after this. Like dispatcharr in this Repo. (Nginx failed) |
Beta Was this translation helpful? Give feedback.
-
|
Hmm I've tried this on my Nginx Proxy Manager LXC
So I've tried sth like that: (certbot) root@nginxproxymanager:~# source /opt/certbot/bin/activate
(certbot) root@nginxproxymanager:~# pip install certbot-dns-duckdns
Requirement already satisfied: certbot-dns-duckdns in /opt/certbot/lib/python3.13/site-packages (1.7.0)
Requirement already satisfied: certbot<6.0,>=1.18.0 in /usr/lib/python3/dist-packages (from certbot-dns-duckdns) (4.0.0)
Requirement already satisfied: requests<3.0,>=2.20.0 in /usr/lib/python3/dist-packages (from certbot-dns-duckdns) (2.32.3)
Requirement already satisfied: dnspython<3.0,>=2.0.0 in /opt/certbot/lib/python3.13/site-packages (from certbot-dns-duckdns) (2.8.0)
Requirement already satisfied: acme>=4.0.0 in /usr/lib/python3/dist-packages (from certbot<6.0,>=1.18.0->certbot-dns-duckdns) (4.0.0)
Requirement already satisfied: ConfigArgParse>=1.5.3 in /usr/lib/python3/dist-packages (from certbot<6.0,>=1.18.0->certbot-dns-duckdns) (1.7)
Requirement already satisfied: configobj>=5.0.6 in /usr/lib/python3/dist-packages (from certbot<6.0,>=1.18.0->certbot-dns-duckdns) (5.0.9)
Requirement already satisfied: cryptography>=43.0.0 in /usr/lib/python3/dist-packages (from certbot<6.0,>=1.18.0->certbot-dns-duckdns) (43.0.0)
Requirement already satisfied: distro>=1.0.1 in /usr/lib/python3/dist-packages (from certbot<6.0,>=1.18.0->certbot-dns-duckdns) (1.9.0)
Requirement already satisfied: josepy>=2.0.0 in /usr/lib/python3/dist-packages (from certbot<6.0,>=1.18.0->certbot-dns-duckdns) (2.0.0)
Requirement already satisfied: parsedatetime>=2.4 in /usr/lib/python3/dist-packages (from certbot<6.0,>=1.18.0->certbot-dns-duckdns) (2.6)
Requirement already satisfied: pyrfc3339 in /usr/lib/python3/dist-packages (from certbot<6.0,>=1.18.0->certbot-dns-duckdns) (2.0.1)
Requirement already satisfied: pytz>=2019.3 in /usr/lib/python3/dist-packages (from certbot<6.0,>=1.18.0->certbot-dns-duckdns) (2025.2)
Requirement already satisfied: charset_normalizer<4,>=2 in /usr/lib/python3/dist-packages (from requests<3.0,>=2.20.0->certbot-dns-duckdns) (3.4.2)
Requirement already satisfied: idna<4,>=2.5 in /usr/lib/python3/dist-packages (from requests<3.0,>=2.20.0->certbot-dns-duckdns) (3.10)
Requirement already satisfied: urllib3<3,>=1.21.1 in /usr/lib/python3/dist-packages (from requests<3.0,>=2.20.0->certbot-dns-duckdns) (2.3.0)
Requirement already satisfied: certifi>=2017.4.17 in /usr/lib/python3/dist-packages (from requests<3.0,>=2.20.0->certbot-dns-duckdns) (2025.1.31)
Requirement already satisfied: PyOpenSSL>=25.0.0 in /usr/lib/python3/dist-packages (from acme>=4.0.0->certbot<6.0,>=1.18.0->certbot-dns-duckdns) (25.0.0)
(certbot) root@nginxproxymanager:~# Yet still shows the same error, any ideas? |
Beta Was this translation helpful? Give feedback.
-
|
after updating NPM using [3/4] Linking dependencies...
warning " > @uiw/react-textarea-code-editor@3.1.1" has unmet peer dependency "@babel/runtime@>=7.10.0".
[4/4] Building fresh packages...
Done in 32.32s.
yarn run v1.22.22
$ tsc && vite build
vite v7.1.12 building for production...
✓ 7794 modules transformed.
dist/index.html 1.34 kB │ gzip: 0.61 kB
dist/assets/index-YJRSYeqY.css 0.10 kB │ gzip: 0.11 kB
dist/assets/index-BJF_4ZT_.css 543.36 kB │ gzip: 70.10 kB
dist/assets/CertificateFormatter-CeqeR-SL.js 0.22 kB │ gzip: 0.19 kB
dist/assets/TrueFalseFormatter-C3L3QbV5.js 0.33 kB │ gzip: 0.24 kB
dist/assets/IconPower-DvX5xW9v.js 0.37 kB │ gzip: 0.28 kB
dist/assets/ValueWithDateFormatter-UOUBvOrH.js 0.44 kB │ gzip: 0.27 kB
dist/assets/IconHelp-DCXFz_vg.js 0.46 kB │ gzip: 0.31 kB
dist/assets/IconEdit-B3gE3SR-.js 0.50 kB │ gzip: 0.33 kB
dist/assets/DomainsFormatter-BoT6f4EV.js 0.86 kB │ gzip: 0.50 kB
dist/assets/index-CJVrB2pr.js 1.82 kB │ gzip: 0.95 kB
dist/assets/IconTrash-TCFydYjJ.js 2.05 kB │ gzip: 0.79 kB
dist/assets/index-BOuY2Obz.js 2.45 kB │ gzip: 1.04 kB
dist/assets/index-CVmlp5_H.js 3.01 kB │ gzip: 0.73 kB
dist/assets/index-Mci0g5fc.js 3.42 kB │ gzip: 1.21 kB
dist/assets/index-Y1J-CR08.js 4.71 kB │ gzip: 1.75 kB
dist/assets/index-CDWGX8hA.js 5.26 kB │ gzip: 2.00 kB
dist/assets/index-D4U_aIgG.js 5.80 kB │ gzip: 2.13 kB
dist/assets/index-Ce2DwVNF.js 5.83 kB │ gzip: 2.09 kB
dist/assets/index-DkNXx0EH.js 5.88 kB │ gzip: 2.15 kB
dist/assets/index-C4jgmLMW.js 6.75 kB │ gzip: 2.49 kB
dist/assets/index-wDV9ExCs.js 7.14 kB │ gzip: 1.90 kB
dist/assets/index-xTK1dRzL.js 40.85 kB │ gzip: 14.69 kB
dist/assets/TableLayout-Bh3My8k1.js 50.49 kB │ gzip: 13.68 kB
dist/assets/index-gIHubYKY.js 2,050.03 kB │ gzip: 644.92 kB
(!) Some chunks are larger than 500 kB after minification. Consider:
- Using dynamic import() to code-split the application
- Use build.rollupOptions.output.manualChunks to improve chunking: https://rollupjs.org/configuration-options/#output-manualchunks
- Adjust chunk size limit for this warning via build.chunkSizeWarningLimit.
✓ built in 16.75s
Done in 26.41s.
✔️ Built Frontend
yarn install v1.22.22
[1/4] Resolving packages...
[2/4] Fetching packages...
warning lru.min@1.1.2: The engine "bun" appears to be invalid.
warning lru.min@1.1.2: The engine "deno" appears to be invalid.
[3/4] Linking dependencies...
warning " > @apidevtools/swagger-parser@10.1.1" has unmet peer dependency "openapi-types@>=7".
[4/4] Building fresh packages...
Done in 6.34s.
✔️ Initialized Backend
Hit:1 http://openresty.org/package/debian bullseye InRelease
Hit:2 http://deb.debian.org/debian trixie InRelease
Hit:3 http://deb.debian.org/debian trixie-updates InRelease
Hit:4 http://security.debian.org trixie-security InRelease
Hit:5 https://deb.nodesource.com/node_22.x nodistro InRelease
All packages are up to date.
Warning: http://openresty.org/package/debian/dists/bullseye/InRelease: Policy will reject signature within a year, see --audit for details
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 'http://openresty.org/package/debian'
openresty is already the newest version (1.27.1.2-1~bullseye1).
Summary:
Upgrading: 0, Installing: 0, Removing: 0, Not Upgrading: 0
Requirement already satisfied: pip in /usr/lib/python3/dist-packages (25.1.1)
Collecting pip
Downloading pip-25.3-py3-none-any.whl.metadata (4.7 kB)
Requirement already satisfied: setuptools in /usr/lib/python3/dist-packages (78.1.1)
Collecting setuptools
Downloading setuptools-80.9.0-py3-none-any.whl.metadata (6.6 kB)
Requirement already satisfied: wheel in /usr/lib/python3/dist-packages (0.46.1)
Requirement already satisfied: packaging>=24.0 in /usr/lib/python3/dist-packages (from wheel) (25.0)
Downloading pip-25.3-py3-none-any.whl (1.8 MB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 1.8/1.8 MB 5.9 MB/s eta 0:00:00
Downloading setuptools-80.9.0-py3-none-any.whl (1.2 MB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 1.2/1.2 MB 7.5 MB/s eta 0:00:00
Installing collected packages: setuptools, pip
Attempting uninstall: setuptools
Found existing installation: setuptools 78.1.1
Not uninstalling setuptools at /usr/lib/python3/dist-packages, outside environment /opt/certbot
Can't uninstall 'setuptools'. No files were found to uninstall.
Attempting uninstall: pip
Found existing installation: pip 25.1.1
Not uninstalling pip at /usr/lib/python3/dist-packages, outside environment /opt/certbot
Can't uninstall 'pip'. No files were found to uninstall.
Successfully installed pip-25.3 setuptools-80.9.0
Requirement already satisfied: certbot in /usr/lib/python3/dist-packages (4.0.0)
Collecting certbot
Downloading certbot-5.1.0-py3-none-any.whl.metadata (7.0 kB)
Requirement already satisfied: certbot-dns-cloudflare in /usr/lib/python3/dist-packages (4.0.0)
Collecting certbot-dns-cloudflare
Downloading certbot_dns_cloudflare-5.1.0-py3-none-any.whl.metadata (1.5 kB)
Collecting acme>=5.1.0 (from certbot)
Downloading acme-5.1.0-py3-none-any.whl.metadata (1.3 kB)
Requirement already satisfied: ConfigArgParse>=1.5.3 in /usr/lib/python3/dist-packages (from certbot) (1.7)
Requirement already satisfied: configobj>=5.0.6 in /usr/lib/python3/dist-packages (from certbot) (5.0.9)
Requirement already satisfied: cryptography>=43.0.0 in /usr/lib/python3/dist-packages (from certbot) (43.0.0)
Requirement already satisfied: distro>=1.0.1 in /usr/lib/python3/dist-packages (from certbot) (1.9.0)
Requirement already satisfied: josepy>=2.0.0 in /usr/lib/python3/dist-packages (from certbot) (2.0.0)
Requirement already satisfied: parsedatetime>=2.6 in /usr/lib/python3/dist-packages (from certbot) (2.6)
Requirement already satisfied: pyrfc3339 in /usr/lib/python3/dist-packages (from certbot) (2.0.1)
Collecting cloudflare<2.20,>=2.19 (from certbot-dns-cloudflare)
Downloading cloudflare-2.19.4.tar.gz (118 kB)
Installing build dependencies ... done
Getting requirements to build wheel ... done
Preparing metadata (pyproject.toml) ... done
Requirement already satisfied: requests in /usr/lib/python3/dist-packages (from cloudflare<2.20,>=2.19->certbot-dns-cloudflare) (2.32.3)
Requirement already satisfied: pyyaml in /usr/lib/python3/dist-packages (from cloudflare<2.20,>=2.19->certbot-dns-cloudflare) (6.0.2)
Collecting jsonlines (from cloudflare<2.20,>=2.19->certbot-dns-cloudflare)
Downloading jsonlines-4.0.0-py3-none-any.whl.metadata (1.6 kB)
Requirement already satisfied: PyOpenSSL>=25.0.0 in /usr/lib/python3/dist-packages (from acme>=5.1.0->certbot) (25.0.0)
Requirement already satisfied: charset_normalizer<4,>=2 in /usr/lib/python3/dist-packages (from requests->cloudflare<2.20,>=2.19->certbot-dns-cloudflare) (3.4.2)
Requirement already satisfied: idna<4,>=2.5 in /usr/lib/python3/dist-packages (from requests->cloudflare<2.20,>=2.19->certbot-dns-cloudflare) (3.10)
Requirement already satisfied: urllib3<3,>=1.21.1 in /usr/lib/python3/dist-packages (from requests->cloudflare<2.20,>=2.19->certbot-dns-cloudflare) (2.3.0)
Requirement already satisfied: certifi>=2017.4.17 in /usr/lib/python3/dist-packages (from requests->cloudflare<2.20,>=2.19->certbot-dns-cloudflare) (2025.1.31)
Collecting attrs>=19.2.0 (from jsonlines->cloudflare<2.20,>=2.19->certbot-dns-cloudflare)
Downloading attrs-25.4.0-py3-none-any.whl.metadata (10 kB)
Downloading certbot-5.1.0-py3-none-any.whl (407 kB)
Downloading certbot_dns_cloudflare-5.1.0-py3-none-any.whl (14 kB)
Downloading acme-5.1.0-py3-none-any.whl (94 kB)
Downloading jsonlines-4.0.0-py3-none-any.whl (8.7 kB)
Downloading attrs-25.4.0-py3-none-any.whl (67 kB)
Building wheels for collected packages: cloudflare
Building wheel for cloudflare (pyproject.toml) ... done
Created wheel for cloudflare: filename=cloudflare-2.19.4-py2.py3-none-any.whl size=121145 sha256=74f05d34aaac8f1fef883ae55d63dad05c36586357216b41fe1f19e6bc5718fa
Stored in directory: /root/.cache/pip/wheels/02/e2/07/9631d33674b55ec3dd3c4e1b0ba39cfc1f1bcf194831535e33
Successfully built cloudflare
Installing collected packages: attrs, jsonlines, acme, cloudflare, certbot, certbot-dns-cloudflare
Attempting uninstall: acme
Found existing installation: acme 4.0.0
Not uninstalling acme at /usr/lib/python3/dist-packages, outside environment /opt/certbot
Can't uninstall 'acme'. No files were found to uninstall.
Attempting uninstall: cloudflare
Found existing installation: cloudflare 2.20.0
Not uninstalling cloudflare at /usr/lib/python3/dist-packages, outside environment /opt/certbot
Can't uninstall 'cloudflare'. No files were found to uninstall.
Attempting uninstall: certbot
Found existing installation: certbot 4.0.0
Not uninstalling certbot at /usr/lib/python3/dist-packages, outside environment /opt/certbot
Can't uninstall 'certbot'. No files were found to uninstall.
Attempting uninstall: certbot-dns-cloudflare
Found existing installation: certbot-dns-cloudflare 4.0.0
Not uninstalling certbot-dns-cloudflare at /usr/lib/python3/dist-packages, outside environment /opt/certbot
Can't uninstall 'certbot-dns-cloudflare'. No files were found to uninstall.
Successfully installed acme-5.1.0 attrs-25.4.0 certbot-5.1.0 certbot-dns-cloudflare-5.1.0 cloudflare-2.19.4 jsonlines-4.0.0
✔️ Updated Certbot
✔️ Started Services
✔️ Updated successfully!I am still getting an error: {
"error": {
"message": "Internal Error"
},
"debug": {
"stack": [
"Error: usage: ",
" certbot [SUBCOMMAND] [options] [-d DOMAIN] [-d DOMAIN] ...",
"",
"Certbot can obtain and install HTTPS/TLS/SSL certificates. By default,",
"it will attempt to use a webserver both for obtaining and installing the",
"certificate. ",
"certbot: error: unrecognized arguments: --dns-duckdns-no-txt-restore",
""
],
"previous": {
"code": 2,
"killed": false,
"signal": null,
"cmd": "certbot renew --force-renewal --config /etc/letsencrypt.ini --work-dir /tmp/letsencrypt-lib --logs-dir /data/logs --cert-name npm-2 --preferred-challenges dns --disable-hook-validation --no-random-sleep-on-renew --dns-duckdns-no-txt-restore"
}
}
} |
Beta Was this translation helpful? Give feedback.
-
|
@ireun This is most likely related to a custom dns certbot you are using? We can't cover every certbot installation and update, for your error I suggest removing the option |
Beta Was this translation helpful? Give feedback.
-
Do you know from where exactly? I've tried removing it from |
Beta Was this translation helpful? Give feedback.
-
|
@ireun I don't run NginxProxyManager anymore at all, I've switched to zoraxy, so not really, as I only used it with the default plugins. Maybe someone else here knows it. |
Beta Was this translation helpful? Give feedback.
-
|
Tested these with existing 12 and also tested older backups to combine with update before and after. These pass all testing so far well:
Problematic:
By the way, I know there is a lot of scripts and a huge number already is moved to 13. |
Beta Was this translation helpful? Give feedback.
-
|
@drVLecter Check this for a board, though I'm not sure if its fully up to date. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks Wolfie, |
Beta Was this translation helpful? Give feedback.
-
|
@drVLecter :D |
Beta Was this translation helpful? Give feedback.
-
|
Great, Thanks mate. |
Beta Was this translation helpful? Give feedback.
-
|
@drVLecter Wait but it actually is debian 13? https://github.com/community-scripts/ProxmoxVE/blob/main/ct/nginxproxymanager.sh#L14 |
Beta Was this translation helpful? Give feedback.
-
|
I was not able to use the nginxproxymanager install script on a brand new install of proxmox and with Debian 13. With verbose I get this error when building the app: It seems like npm sqlite3 does not work with new python3.13. I manually changed the sqlite3 dependency in package.json with https://www.npmjs.com/package/sqlite3-gyp, build it manually, and hack the app source to use I found these issues helpful: |
Beta Was this translation helpful? Give feedback.
-
|
Proxmox-ngx Dashboard no longer works when I try to load the webpage. Got 500 Internal Server error. |
Beta Was this translation helpful? Give feedback.
-
|
@mparal we don't have proxmox-ngx, do you mean paperless ngx ? |
Beta Was this translation helpful? Give feedback.
-
|
Ohh, sorry typo.... of course I mean "paperless-ngx" |
Beta Was this translation helpful? Give feedback.
-
|
well can provide logs or so? For me it just took some reboots and re-running the upgrade, take a look at those suggestions: |
Beta Was this translation helpful? Give feedback.
and others
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
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 -rto 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 rebootTip
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)
Beta Was this translation helpful? Give feedback.
All reactions