mirror of
https://github.com/zitadel/zitadel.git
synced 2025-05-06 11:26:46 +00:00
0b742233f9
* fix: clarify instances in steps and config * docs: update setup step Co-authored-by: Fabi <38692350+hifabienne@users.noreply.github.com> Co-authored-by: Livio Amstutz <livio.a@gmail.com>
31 lines
972 B
Markdown
31 lines
972 B
Markdown
---
|
|
title: Custom Domain
|
|
---
|
|
|
|
# Run ZITADEL on a (Sub)domain of Your Choice
|
|
|
|
This guide assumes you are already familiar with [configuring ZITADEL](./configure).
|
|
|
|
You most probably need to configure these fields for making ZITADEL work on your custom domain.
|
|
|
|
## Standard Config
|
|
|
|
For security reasons, ZITADEL only serves requests sent to the expected protocol, host and port.
|
|
If not using localhost as ExternalDomain, ExternalSecure must be true and you need to serve the ZITADEL console over HTTPS.
|
|
|
|
```yaml
|
|
ExternalSecure: true
|
|
ExternalDomain: 'zitadel.my.domain'
|
|
ExternalPort: 443
|
|
```
|
|
|
|
## Database Initialization Steps Config
|
|
|
|
ZITADEL creates random subdomains for each instance created.
|
|
However, for the first instance, this is most probably not the desired behavior.
|
|
In this case the `ExternalDomain`-field of the configuration is used.
|
|
|
|
## Example
|
|
|
|
Go to the [loadbalancing example with Traefik](./loadbalancing-example) for seeing a working example configuration.
|