🔧 Patch release — updates always land + a fresh-Docker HTTPS login fix
Fixed
- HTTPS login on a fresh Docker container (#531) — on a brand-new install PegaProx couldn't write its self-signed certificate (the
/app/ssltarget didn't exist), so it silently fell back to plain HTTP. A browser then connecting over HTTPS got a "connection error" on login. The certificate is now generated into the persistedconfig/ssldirectory (created on startup), so HTTPS comes back on its own and survivesdocker compose pull. Thanks @tradexsrl for the logs. - Updates that didn't fully apply — both the in-app updater and
update.shhad a version-equality early-exit that could leave a half-applied install stuck (version bumped, some files stale) with no way to self-heal short of--force. They now always re-download and re-apply the full file tree: a same-version run is a silent re-sync, real upgrades still prompt. The shell fallback also pulls the complete tree from the GitHub API instead of a hand-maintained file list — so newly added files (e.g. sponsor logos) are never missed — with a guard that never overwritesconfig/,ssl/,logs/, backups or secrets.
Upgrade: in-app updater (Settings → Updates) or ./update.sh. Docker: docker compose pull && docker compose up -d.
💎 Platinum Sponsors
- netwolk GmbH — Swiss managed-services partner
- Expertize.nl — Dutch Proxmox specialists
A warm welcome to Datimo, joining as a 🥈 Silver sponsor — thank you! 💙
PegaProx lives entirely from sponsorships and donations — server costs, certificates and the developer hours behind every release. Massive thanks 🙌. Sponsor PegaProx → opencollective.com/pegaprox | pegaprox.com/#sponsor