Log-in stuck in fresh self-hosted instance
🏬Self-hosted🔍Authentication❌Unsolved🪵Login❓Question
Hi. I have a zitadel instance setup with the
The application starts up, the login UI as well.
I use the specified domain to go to the login page, and I'm presented with the login form.
I login using the values-defined
The login UI stalls, loading perpetually with
I have attached a screenshot from the network traffic the browser sees. As you can see the
I also have Hubble for monitoring the network traffic on cilium, and ll the requests seem to get forwarded to the correct endpoints as well (attached pic).
Is that something that has come up before? Is there something I'm doing wrong in the configuration?
I can provide the values I'm using if needed
9.30.09.30.0 chart, 4.13.04.13.0 application version. I'm using cilium as kube-proxy and gatewayAPI provider and I have defined both login UI as enabled and have enabled the HTTPRoutes for both the zitadel server and the login UI. I'm also using cert-managercert-manager for provisioning secrets. With the "requirements" out of the way, let's dive into the issue. The application starts up, the login UI as well. I use the specified domain to go to the login page, and I'm presented with the login form. I login using the values-defined zitadel-adminzitadel-admin user and credentials. The login UI stalls, loading perpetually with [unimplemented] {"code":5,"message":"Not Found"}[unimplemented] {"code":5,"message":"Not Found"} and [unknown] missing trailer[unknown] missing trailer toasts popping up.I have attached a screenshot from the network traffic the browser sees. As you can see the
.v2.v2 endpoints respond correctly, but the .v1.v1 ones give a 404 status.I also have Hubble for monitoring the network traffic on cilium, and ll the requests seem to get forwarded to the correct endpoints as well (attached pic).
Is that something that has come up before? Is there something I'm doing wrong in the configuration?
I can provide the values I'm using if needed
