-
LDAP WebGUI v1.24.0
StableAll checks were successfulTests / pytest (Python 3.11) (push) Successful in 2m36sTests / pytest (Python 3.12) (push) Successful in 2m41sTests / shellcheck (install.sh, update.sh, bootstrap-ldap.sh, webupdate.sh, get_ldap-webgui.sh, setup.sh) (push) Successful in 2m41sRelease / Publish release (push) Successful in 3sreleased this
2026-11-01 19:50:27 +01:00 | 22 commits to main since this releaseAdded
- Who may reach the WebGUI. nginx now admits loopback plus the hosts
and networks in/etc/nginx/ldap-webgui-access.conf, and nothing else;
/healthadditionally admits the monitoring hosts in
/etc/nginx/ldap-webgui-monitoring.conf. The guided setup asks for both
(Access, suggesting the address of your SSH session);install.sh
takes--allow LISTand--allow-monitoring LIST(IPv4/IPv6, CIDR —
a network with host bits set is refused with the corrected form).
anywrites an unrestricted list and needs a second, explicit
confirmation (typedyes,access_any_keep=yes, or--confirm-any).
Loopback is always in the list — the health checks of the setup and of
every update go throughhttps://localhost/health. - Settings → Access shows both lists read-only, whether the host is
restricted, unrestricted or in an unknown state, and which entry admits
your own address. - README → Operating recommendation: admin network or VPN only, never
internet-facing; ideally from a jump host, at least from a browser
profile that is not the everyday one.
Changed
install.shstops whennginx -tfails after it wrote an access
file, and puts the previous file back — before, a failingnginx -t
was only a warning. A re-install that keeps both files still warns.install.shwithout--allowkeeps an existing access file; where
there is none it writes loopback only and says how to open it.- The vhost no longer has an ACME
/.well-known/acme-challenge/
exception on port 80, and no longer recommends certbot — certificates
come from your own CA. - Port 80's redirect and
/robots.txtanswer only allowed hosts. A
plainreturnruns before nginx's allow/deny; both now go through
try_filesto a named location, which is reached only after the
access check. Carry this over with the include lines.
Fixed
- An existing directory's CA certificate is trusted by the system.
setup.sh(directory existing) checked the CA as root, then wrote its
path intoconfig.yamlunchanged — a CA under/rootpassed the check,
but the service (ldapwebgui,ProtectHome=true) could not read it,
/healthanswered 503 and the setup stopped atstart. Unless the
system already trusts it (same SHA-256 fingerprint in
/etc/ssl/certs/ca-certificates.crt, whichldap.tls.ca_certthen
names), the setup copies it to
/usr/local/share/ca-certificates/ldap-webgui-ca.crt, runs
update-ca-certificatesand names that file. It stays trusted if the
WebGUI is removed: delete the file and run
update-ca-certificates --freshto undo. setup.shsays why the WebGUI is not healthy. When/healthdoes
not answer 200 with the new version, the error now shows the last
answer — the HTTP status and the start of the body, e.g.HTTP 503: {"ldap": "unreachable", ...}— instead of only pointing at the journal
andapp.log, which do not record a failed LDAP connection.
Upgrade notes
-
nginx/ldap-webgui.confchanged.update.shnever installs the
vhost, so an updated host stays unrestricted until you change it by
hand; the update's nginx drift check says so. Order matters — create
the files first, ornginx -tfails on the missing includes:printf 'allow 127.0.0.1;\nallow ::1;\nallow 192.168.10.0/24;\n' \ > /etc/nginx/ldap-webgui-access.conf # your admin hosts/networks printf '# monitoring hosts, /health only\n' \ > /etc/nginx/ldap-webgui-monitoring.confThen add
include /etc/nginx/ldap-webgui-access.conf;anddeny all;
to bothserverblocks, and tolocation = /healththe two includes
(access, then monitoring) followed bydeny all;— exactly as in the
shippednginx/ldap-webgui.conf.nginx -t && systemctl reload nginx.
Keep127.0.0.1and::1: without them every update rolls back. -
Re-running
install.shon such a host copies the new vhost and,
without--allow, writes loopback only — pass--allowwith your admin
hosts.
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
- Who may reach the WebGUI. nginx now admits loopback plus the hosts