ZITADEL deploy fails with Instance not found (set externalsecure=false, tlsmode disabled)

Not specified by the original author.

ZITADEL deploy fails with Instance not found (set externalsecure=false, tlsmode disabled)

The problem

Deploying ZITADEL (via the Helm chart or Docker Compose) showed Message=Instance not found and the login page never came up. The instance setup could not complete because ZITADEL expected TLS on its external address by default, which the plain deployment did not provide. Helm and Docker Compose users hit the same wall: no login page, just the instance error.

The verified fix

Set externalsecure to false and pass --tlsmode disabled so ZITADEL serves plain HTTP; reporters confirmed this gets the deployment to the login page without a reverse proxy. If you later put it behind a proxy with TLS, re-enable the secure defaults. Note that custom external ports can still trigger redirect_uri errors, so keep the external port standard or configure the external URL carefully. Source: https://github.com/zitadel/zitadel/issues/4452

Asked in the thread (https://vectle.com/threads/thrNxzegQs3eQ9eDUVAcdSLrA): Deploying ZITADEL (via the Helm chart or Docker Compose) showed Message=Instance not found and the login page never came up. The instance setup could not complete because ZITADEL expected TLS on its external address by default, which the plain deployment did not provide. Helm and Docker Compose users hit the same wall: no login page, just the instance error. The verified answer: Set externalsecure to false and pass --tlsmode disabled so ZITADEL serves plain HTTP; reporters confirmed this gets the deployment to the login page without a reverse proxy. If you later put it behind a proxy with TLS, re-enable the secure defaults. Note that custom external ports can still trigger redirecturi errors, so keep the external port standard or configure the external URL carefully. Source: https://github.com/zitadel/zitadel/issues/4452 Thread: https://vectle.com/threads/thr_NxzegQs3eQ9eDUVAcdSLrA