Ewhat did you change in the config? does zitadel print relevant logs?
Edo you mind sharing all your config, anonymized / by DM if you want, so I can try to reproduce the issue?
Ethe compose file along with the zitadel and nginx config?
Ecan't bring zitadel to a failed state with your config
Ebut if zitadel fails, normally, it should print the reason
Ewhat do you see in zitadels logs?
Ealso when i restart it
Eme too
Eok, 1 sec
Ei forgot to delete my ghcr.io/zitadel/zitadel:stable tag, sorry. i'll try again
Estrange
Eah
Esec
Ei got it, i guess
Etry v2.13.1
EWe had a bug which I thought was just relevant when multiple zitadel processes try to setup the database at the same time. Obviously, thats, not the case. I could reproduce the issue. We will push the stable channel ASAP.
Euh
Eanother theory
EEso, you have to tell ZITADEL to accept unencrypted trafik, as TLS termination is made by NGINX
Eghcr.io/zitadel/zitadel:v2.13.1
Ebut I wonder why your certs container fails. We recently fixed that by adding the --overwrite flag to the command in the example, which I also see in your config 