Zitadel in Cloud Run is returning 403
I've set up Zitadel to run in Cloud Run behind LB and when I try to access it I get 403 error, error is coming from Zitadel, not from LB. Could someone help me debug why this is happening or provide tutorial or example YAML I could follow? My config YAML attached
3 Replies
hello @Sebastian thanks for reaching out, can you share the steps to reproduce? what endpoint is returning that status code? how are you calling it?
hello @Federico!
the steps to reproduce is to deploy the app in cloud run using my attached manifest, deploy LB pointing to this service and then just trying to open the subdomain pointed to this service. I've tried calling it both as
sub.domain.com and as sub.domain.com/ui/console
LB setup is in the screenshots
Hello @Sebastian apologies for the delay, could you please share with me a network trace?
- https://help.zitadel.com/steps-to-record-a-network-trace-har-file
Steps to record a network trace (HAR file)
A network trace is a detailed log of the communication between your device and a server. In the context of authentication or login errors, it records the requests sent and the responses received during the login process. Support teams use it to identify where the process fails — for example, whether the issue is due to a network problem, a mis...