-
LDAP WebGUI v1.33.0
StableAll checks were successfulTests / Scope (push) Successful in 1sTests / pytest (newest CPython, warning only) (push) Has been skippedTests / shellcheck (install.sh, update.sh, bootstrap-ldap.sh, webupdate.sh, get_ldap-webgui.sh, setup.sh, config-backup.sh, certtool.sh, accesstool.sh) (push) Successful in 1m22sTests / pytest (Python 3.13) (push) Successful in 21m9sTests / pytest (Python 3.14) (push) Successful in 22m30sTests / Publish release (push) Successful in 3sreleased this
2026-11-08 19:02:50 +01:00 | 4 commits to main since this releaseUpgrade notes
- The nginx vhost is now replaced by every update.
/etc/nginx/sites-available/ldap-webguiis the application's file:
rendered from the shipped template and the new host settings file
/etc/ldap-webgui/vhost.env, checked, installed, confirmed served,
and put back if anything fails. Local edits to the vhost are lost —
host names, certificate paths and listen addresses belong in
vhost.env, who may connect stays Settings → Access. - The first update migrates: it reads those values from the
installed vhost and writesvhost.env; the previous file stays as
/etc/nginx/sites-available/ldap-webgui.pre-<version>. - A vhost edited by hand is not touched — no rollout, a manual step
that lists the differing lines, repeated by every update — until you
carry over what you need and run
sudo ldap-webgui-update --vhost-only --replace-vhost. - Git mode (
sudo ldap-webgui-update) and
ldap-webgui-update --archiveneed a second step: they run the
previous release'supdate.sh, which does not know the vhost yet.
Afterwards runsudo ldap-webgui-update --vhost-only(after
--archive:sudo bash <unpacked release>/update.sh --vhost-only).
The web update,--from-releaseand an unpacked release's own
update.shdo it in one run. - The steps, how to check, how to back out and the downgrade:
docs/upgrade-1.33.md(also under Settings → Documentation).
Added
/etc/ldap-webgui/vhost.env(root:root 0640) — the vhost's host
settings:SERVER_NAME,TLS_CERT,TLS_KEY,LISTEN. Parsed,
never sourced; an invalid file or an unknown key skips the rollout
with a manual step and never fails the update.update.sh --vhost-onlyre-renders the vhost fromvhost.envand
the installed release — checked,nginx -t, reloaded, confirmed, the
previous one put back on failure; no release change, no restart of the
WebGUI. The way to apply an editedvhost.env.- A change of the listen addresses restarts nginx (the update,
--vhost-only,install.sh): a reload cannot move nginx between
"every address" and given ones — it keeps the old sockets and still
reports success. Same addresses: a reload, as before. update.sh --replace-vhostreplaces a hand-edited vhost from
before 1.33.0 (the previous file is kept).install.sh --server-name "NAMES"and--listen "ADDRS"set
SERVER_NAMEandLISTENat install time. WithLISTENset, nginx
listens on those addresses plus127.0.0.1(the health checks use
loopback)./healthanswers with anX-LDAP-WebGUI-Vhostheader — the hash of
the rendered vhost, which the update and the installer use to confirm
nginx serves the new one.
Changed
- The security headers reach the static files. The locations for
/static/and/healthset headers of their own, and nginx then drops
every header set at server level: CSP,X-Frame-Options,
Referrer-PolicyandPermissions-Policywere missing on stylesheets,
scripts and images. Every such location now carries the full set. /robots.txtsends oneContent-Typeinstead of two.- The vhost template's comments are English, its header says it is
overwritten by every update, the cipher list is labelled Mozilla
intermediate;/healthis proxied withConnection ""like the rest. - A re-run of
install.shreplaces a differing vhost — an older
release's or one edited by hand — after keeping it as
ldap-webgui.pre-install-<timestamp>; host names, certificate paths
and listen addresses are carried over intovhost.env. Up to 1.32 it
kept any vhost that included the access list. install.shand the update take the access list lock and then the
certificate lock before touching nginx, so an access list change or a
certificate renewal from the web UI never runs into a vhost change.- The web update's One manual step is left box shows why the vhost
was not replaced, the lines a hand edit added, and the command the
update itself prints for that case (--replace-vhost, theln -sfn
line, or the lines that put the previous vhost back). install.shreports a vhost nginx does not serve as a failed check
and ends INCOMPLETE (exit 1) instead of "All checks passed".install.shrefuses avhost.envthat is not root's alone (a
symlink, another owner, group- or world-writable) before installing
anything — the update skips the rollout for it.- The vhost's structure check also refuses
return,rewriteandif
(they act before the access list) apart from the template's redirect
androbots.txtanswers, anderror_pagewith=or a named target.
Removed
- The update's vhost drift warning ("The installed nginx vhost differs
from the one this release ships") — the update replaces the vhost
instead. - The
NGINX_VHOST_FILEenvironment override ofupdate.sh; the vhost
is always/etc/nginx/sites-available/ldap-webgui.
Update without git access: download the source tar.gz below, extract it, then run the update.sh it contains:
sudo bash <extracted-dir>/update.sh --archive <tarball>Downloads
-
Source code (ZIP)
0 downloads
-
Source code (TAR.GZ)
0 downloads
- The nginx vhost is now replaced by every update.