EUse ZITADEL_PORT for the port, ZITADEL should listen at and ZITADEL_EXTERNALPORT for the port, your users will access ZITADEL at. For example, that would probably be 80 or 443 if you have a reverse proxy in front of ZITADEL
Ealso see the descriptions in the defaults.yaml https://github.com/zitadel/zitadel/blob/main/cmd/defaults.yaml#L17
GitHub
ZITADEL - The best of Auth0 and Keycloak combined. Built for the serverless era. - zitadel/defaults.yaml at main · zitadel/zitadel
Eif you want to access ZITADEL using localhost in your Host header, you need to set ExternalDomain to localhost https://docs.zitadel.com/docs/guides/manage/self-hosted/custom-domain
This guide assumes you are already familiar with configuring ZITADEL.
Ein that case, you can only access ZITADEL with your domain in your host header. Also see the loadbalancing example https://docs.zitadel.com/docs/guides/deploy/loadbalancing-example
With this example configuration, you create a near production environment for ZITADEL with Docker Compose.
Eif you configure my.domain as ExternalDomain and 443 as your ExternalPort and set ExternalSecure to true, then you have to open your browser at https://my.domain/ui/console/
EDid you change your ExternalDomain config after your initial ZITADEL setup?
EYou'd need to flush your database and let ZITADEL setup again in that case
Ebtw, the protocol is important, too
Eif you set ExternalSecure to true, you need to access ZITADEL using https://...
Ealso, it is possible that something is wrong with your proxy config. We have some examples here https://docs.zitadel.com/docs/guides/manage/self-hosted/reverseproxy/reverse_proxy
EThat looks promising
EMaybe you have to tell apache to pass the host header to ZITADEL somehow
EWould you mind sharing your apache config per DM? I'd also like to add an example to the docs.
EOr something anonymized...
Ecan you turn this on https://httpd.apache.org/docs/2.4/mod/mod_proxy.html#proxypreservehost
Ei guess, your console shows errors when making API calls, now?
Eof course 
tls modes are also documented here: https://docs.zitadel.com/docs/guides/manage/self-hosted/tls_modes
tls modes are also documented here: https://docs.zitadel.com/docs/guides/manage/self-hosted/tls_modesTo allow ZITADEL to be run on any kind of infrastrucute it allows to configure on how tho handle TLS connections.
ECould you sign in with the initial IAM_OWNER user?
Ezitadel-admin@zitadel.localhost and Password1! if you didn't configure something else
Eoh, sorry
Ethat should be zitadel-admin@zitadel.<your external domain>
Eare the api calls failing?
EI think your proxy needs to be configured to pass h2c traffic to ZITADEL
EEZITADEL follows a strict API first approach and makes heavy use of the modern API framework called gRPC.
EOk, I'll try to run it myself like https://docs.zitadel.com/docs/guides/deploy/loadbalancing-example but using httpd
With this example configuration, you create a near production environment for ZITADEL with Docker Compose.
Egot it working
Ecan you try the following?