Is anyone face this issue during install zitadel via helm chart?
Original message was deleted
FHi there, let me quickly check this
FOk so you need to set TLS to false
E.g.
E.g.
--set zitadel.configmapConfig.TLS.Enabled=falseFOtherwise ZITADEL tries to load TLS keys while starting
Fyes that makes sense
FZITADEL by default does listen only to localhost:8080
FIf you want zitadel to listen to other names you need to tell it this.
https://docs.zitadel.com/docs/guides/manage/self-hosted/custom-domain
https://docs.zitadel.com/docs/guides/manage/self-hosted/custom-domain
This guide assumes you are already familiar with configuring ZITADEL.
FWell zitadel needs to have the Hostname 
otherwise it would not be feasible to run multiple instances in parallel
otherwise it would not be feasible to run multiple instances in parallelFWe are open for ux changes in that regard 
We did discuss if zitadel should accept all Hostnamen per default but this brings other challenges (like from what domain should it send mails, and more)
We did discuss if zitadel should accept all Hostnamen per default but this brings other challenges (like from what domain should it send mails, and more)
FOn what platform are you trying to deploy? Docker compose?
FBecause in that case the docker-compose.yml already takes care of the cert to connect to the CRDB
FOk
FI think you don’t need to supply the certs if you deploy the whole chart directly
FHm Strange we automated test the chart
F@Elio this one is for you
FI can look into this later as soon as I am on a pc
FOk 
FAhh I see
Fthat has nothing to do with the database. Instead it is the way zitadel should start
https://docs.zitadel.com/docs/guides/manage/self-hosted/tls_modes
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.
FThe TLS mode defines if ZITADEL should be connected from the outside world with TLS, With TLS terminated at a proxy or without TLS eniterly
FThis has nothing to do with the connection being made to the database with TLS
FSo in your case if you run a proxy in front you should use tls-mode external which disables the need for TLS certificates in ZITADEL