EHi, @mosamlife
Edid you configure sso.example.io as ExternalDomain when you setupped ZITADEL?
Ebtw, nginx also needs to pass the requests Host header to ZITADEL
Eyou just run a single zitadel container, right?
Edo you mind sharing your zitadel config?
Ecan you try, adding the following to your config and try again, please?
This is described here: https://docs.zitadel.com/docs/guides/manage/self-hosted/tls_modes
This is described here: https://docs.zitadel.com/docs/guides/manage/self-hosted/tls_modes
To allow ZITADEL to be run on any kind of infrastrucute it allows to configure on how tho handle TLS connections.
EI think it's mostly gRPC-web stubs 
@peintnermax do you have a more sophisticated answer?
@peintnermax do you have a more sophisticated answer?EIf you are concerned about network latency: we use brotli compression for our SaaS service, which reduces the size to ~ 7k
PYes it includes all the gRPC stubs but should be a lot smaller when content encoded..
Ewith gzip fallback
EFYI, I added that to the production checklist, yesterday https://docs.zitadel.com/docs/guides/manage/self-hosted/production#networking
As soon as you successfully deployed ZITADEL as a proof of concept using one of our deployment guides,