zitadel-login ghcr.io/zitadel/zitadel-login:latest https://github.com/zitadel/zitadel/pkgs/container/zitadel-login bridge sh false https://forums.unraid.net/topic/200036-unraid-templates-nebur692/ https://github.com/zitadel/zitadel ZITADEL v4 Login UI — the interactive sign-in pages (username/password, MFA, WebAuthn, etc.) for a ZITADEL v4 core instance. Since v4, ZITADEL split its interactive login pages out of the main API container into this separate service. Without it, every login attempt against a v4 "zitadel" container fails with a 404 on /ui/v2/login/login — this template exists to fix exactly that. REQUIRES the companion "zitadel" template from the same repository to already be running, using the exact same Bootstrap Volume path, since this container reads the login-client.pat token that ZITADEL writes there on its first start. Your reverse proxy needs a path-based rule so that requests to "/" and "/ui/v2/login/*" reach this container's port 3000, while everything else keeps going to the "zitadel" container's port 8080. See the setup guide below for an Nginx Proxy Manager example. Full setup guide: https://github.com/Nebur692/unraid-zitadel-templates Security: Network:Management http://[IP]:[PORT:3000]/ui/v2/login/ https://raw.githubusercontent.com/Nebur692/unraid-zitadel-templates/main/zitadel-login/zitadel-login.xml https://raw.githubusercontent.com/Nebur692/unraid-zitadel-templates/main/zitadel/zitadel-icon.png --restart unless-stopped Support this project https://ko-fi.com/nebur69265723 The companion "zitadel" template (v4 core/API), already started at least once, sharing the same Bootstrap Volume path. /ui/v2/login /zitadel/bootstrap/login-client.pat /mnt/user/appdata/zitadel/bootstrap 3000