Self hosted Zitadel v4.2.2 hangs after initial successful login
Use-case: I'm setting up v4 Zitadel from scratch.
Environment: I have a self hosted version running on a VPS.
Version: v4.2.2 (Postgres 17.6)
Stack: Debian 12, Docker, Traefik
What you expected to happen: After successful login the console is displayed.
What went wrong: No idea.
Attachments:
1) Screenshot of screen that is displayed after successful login.
2) My Docker Compose files and Zitadel config files (IMPORTANT NOTE: In the Zitadel configs I'm using secrets, these are handled in a pre-process container. This works as intended.) >>> The updated config has been added in a following message!!
Additional information:
I can access the different health endpoints:
grpcurl api.auth.xxx.com:443 zitadel.admin.v1.AdminService/Healthz
curl https://api.auth.xxx.com/admin/v1/healthz
curl https://api.auth.xxx.com/debug/healthz
2 Replies
Hi @nidkil, I'm an AI assistant for ZITADEL. While a team member reviews this question, I'll see if I can find relevant sources for your question.
Answer
I wasn't able to find a direct answer, here are some relevant sources:
1. Configure ZITADEL with Traefik :
Shows step-by-step how to run ZITADEL behind Traefik using Docker Compose, including TLS, health checks, and recommended login URLs for verifying full system health. 2. [Bug]: Zitadel v4 in docker compose :
Describes user reports of similar issues after a fresh v4 install with Docker and Traefik, and suggests workarounds like starting with a clean directory and removing old volumes. Feel free to tag @Ask Inkeep with additional questions.
Shows step-by-step how to run ZITADEL behind Traefik using Docker Compose, including TLS, health checks, and recommended login URLs for verifying full system health. 2. [Bug]: Zitadel v4 in docker compose :
Describes user reports of similar issues after a fresh v4 install with Docker and Traefik, and suggests workarounds like starting with a clean directory and removing old volumes. Feel free to tag @Ask Inkeep with additional questions.
I cleaned up the config.