[Bug] Ubuntu 26.04 compatibility issue

[surreal70]

Hey there! 👋 Thanks for taking the time to report this bug — we appreciate it!

Please keep in mind: PegaProx is developed and maintained entirely by volunteers in our free time. We do our best, but we can't work magic 🪄 — please be patient, we'll get to your issue as soon as we can.

Want to help keep PegaProx alive?

• ⭐ Star the project — it's free and helps a lot!
• 💖 Become a Sponsor — helps us dedicate more time to development
• 🤝 Contributing code or docs is always welcome too!

---

Describe the bug

After updating from Ubuntu 24.04LTS to Ubuntu 26.04LTS Pegaprox does no longer start.

Current PegaProx Version is 0.9.7.

Even a forced update did not resolve the problem.

Systemlogs show the following:
systemctl status pegaprox.service
● pegaprox.service - PegaProx - Proxmox Cluster Management
Loaded: loaded (/etc/systemd/system/pegaprox.service; enabled; preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Sun 2026-04-26 18:11:50 UTC; 265ms ago
Invocation: d0b025f5b0554b82b5e1c8079f8fe7dc
Process: 8971 ExecStart=/opt/PegaProx/venv/bin/python /opt/PegaProx/pegaprox_multi_cluster.py (code=exited, status=1/FAIL>
Main PID: 8971 (code=exited, status=1/FAILURE)
Mem peak: 9.4M
CPU: 93ms

IMHO it seems that somethin with the Python venv is wrong as the flask binary is available in the bin directory...

Steps to Reproduce

1. Use or update to Ubuntu 26.04
2. start PegaProx service

Expected behavior

Pegaprox should start

Environment

• PegaProx Version: 0.9.7
• Installation Method: shellscript
• OS: Ubuntu 26.04 -->

Logs

syslog states:

2026-04-26T18:13:52.255831+00:00 srv-adh-vm-0084 systemd[1]: Started pegaprox.service - PegaProx - Proxmox Cluster Management.
2026-04-26T18:13:52.342192+00:00 srv-adh-vm-0084 pegaprox[9275]: Missing dependency: No module named 'flask'
2026-04-26T18:13:52.342371+00:00 srv-adh-vm-0084 pegaprox[9275]: A virtual environment exists. Use it to start PegaProx:
2026-04-26T18:13:52.342405+00:00 srv-adh-vm-0084 pegaprox[9275]: /opt/PegaProx/venv/bin/python3 /opt/PegaProx/pegaprox_multi_cluster.py
2026-04-26T18:13:52.342453+00:00 srv-adh-vm-0084 pegaprox[9275]: Or via systemd:
2026-04-26T18:13:52.342487+00:00 srv-adh-vm-0084 pegaprox[9275]: systemctl start pegaprox
2026-04-26T18:13:52.353400+00:00 srv-adh-vm-0084 systemd[1]: pegaprox.service: Main process exited, code=exited, status=1/FAILURE
2026-04-26T18:13:52.353645+00:00 srv-adh-vm-0084 systemd[1]: pegaprox.service: Failed with result 'exit-code'.

Screenshots

Checklist

• [yes ] I have searched existing issues to make sure this is not a duplicate
• [ yes] I am using the latest version of PegaProx

[mkellermann97]

Hey @surreal70 — this isn't really a PegaProx bug, your venv just got broken by the 24.04 → 26.04 upgrade.

Ubuntu 26.04 ships Python 3.14. Your /opt/PegaProx/venv was built against 3.12, so the symlinks inside it now point to a Python binary that no longer exists — that's why it can't find flask either (it's in the 3.12 site-packages, not 3.14).

Fix:

sudo systemctl stop pegaprox
sudo rm -rf /opt/PegaProx/venv
sudo python3 -m venv /opt/PegaProx/venv
sudo /opt/PegaProx/venv/bin/pip install --upgrade pip
sudo /opt/PegaProx/venv/bin/pip install -r /opt/PegaProx/requirements.txt
sudo chown -R pegaprox:pegaprox /opt/PegaProx/venv
sudo systemctl start pegaprox

If python3 -m venv complains, install the build deps first: sudo apt install python3-venv python3-dev build-essential.

Same thing happens on any Ubuntu/Debian major release upgrade. We're thinking about catching it in update.sh or a repair mode — but for now: rebuild the venv and you should be back up.

Cheers,
Marcus

[surreal70]

worked like a charme...stupid me not comming to the solution for myself...shame on me.