Bug Report: Zitadel self-hosted deploy on Dokploy fails with “Not Found” after setting custom subdomain
Description
I tried to deploy a self-hosted Zitadel instance using Dokploy from the built-in template, configured with a custom domain.
Here’s my setup:
Dokploy is running under a custom domain, e.g. dokploy.testhost.com.
For Zitadel, I set a subdomain zitadel.dokploy.testhost.com:
Added it under tab Env Vars
Set the same subdomain in the Domain tab (removed the default domain provided by Traefik)
Deployment completes successfully.
Problem
When I try to open the Zitadel web interface, it starts to load but then redirects to a page showing:
{"code":5,"message":"Not Found"}
Current vs. Expected behavior
Expected: working web interface of Citadel
Current: websited is "trying to open" but redirects to page with json {"code":5,"message":"Not Found"}.
Provide environment information
Zitadel web interface should open correctly under the configured subdomain.
Reproduction Steps
1. Set up Dokploy with a custom domain (e.g., dokploy.testhost.com)
2. Deploy Zitadel from the template
3. Configure Zitadel domain as zitadel.dokploy.testhost.com
4. Remove the default Traefik-provided domain
5. Set the same domain zitadel.dokploy.testhost.com in env var
6. Access https://zitadel.dokploy.testhost.com
7. Observe the error
Environment
• Dokploy version: (the latest)
• Zitadel version: (the latest)
• OS / Host: (Ubuntu 24.04 LTS)
• Deployment type: Self-hosted via Dokploy template
• Reverse proxy: Traefik (default from Dokploy)
Which area(s) are affected? (Select all that apply)
Traefik
Are you deploying the applications where Dokploy is installed or on a remote server?
Originally created by @chasylexus on GitHub (Nov 3, 2025).
Original GitHub issue: https://github.com/Dokploy/templates/issues/516
### To Reproduce
## Bug Report: Zitadel self-hosted deploy on Dokploy fails with “Not Found” after setting custom subdomain
### Description
I tried to deploy a self-hosted **Zitadel** instance using **Dokploy** from the built-in template, configured with a **custom domain**.
Here’s my setup:
1. Dokploy is running under a custom domain, e.g. `dokploy.testhost.com`.
2. For Zitadel, I set a subdomain `zitadel.dokploy.testhost.com`:
- Added it under tab **Env Vars**
- Set the same subdomain in the **Domain** tab (removed the default domain provided by Traefik)
3. Deployment completes successfully.
### Problem
When I try to open the Zitadel web interface, it starts to load but then redirects to a page showing:
```json
{"code":5,"message":"Not Found"}
```
### Current vs. Expected behavior
Expected: working web interface of Citadel
Current: websited is "trying to open" but redirects to page with json {"code":5,"message":"Not Found"}.
### Provide environment information
```bash
Zitadel web interface should open correctly under the configured subdomain.
Reproduction Steps
1. Set up Dokploy with a custom domain (e.g., dokploy.testhost.com)
2. Deploy Zitadel from the template
3. Configure Zitadel domain as zitadel.dokploy.testhost.com
4. Remove the default Traefik-provided domain
5. Set the same domain zitadel.dokploy.testhost.com in env var
6. Access https://zitadel.dokploy.testhost.com
7. Observe the error
Environment
• Dokploy version: (the latest)
• Zitadel version: (the latest)
• OS / Host: (Ubuntu 24.04 LTS)
• Deployment type: Self-hosted via Dokploy template
• Reverse proxy: Traefik (default from Dokploy)
```
### Which area(s) are affected? (Select all that apply)
Traefik
### Are you deploying the applications where Dokploy is installed or on a remote server?
Same server where Dokploy is installed
### Additional context
See the attached video demonstrating the issue.
https://github.com/user-attachments/assets/87f5abfd-e672-4ae9-964c-8e16d628df3c
### Will you send a PR to fix it?
No
hey folks thanks for reporting this, I will check with team as to what could we do here and update you all.
<!-- gh-comment-id:3754379988 -->
@rajatcing commented on GitHub (Jan 15, 2026):
hey folks thanks for reporting this, I will check with team as to what could we do here and update you all.
so a quick workaround would be to disable login V2 by ZITADEL_DEFAULTINSTANCE_FEATURES_LOGINV2_REQUIRED: false and it should resolve the issue.
<!-- gh-comment-id:3755096809 -->
@rajatcing commented on GitHub (Jan 15, 2026):
so a quick workaround would be to disable login V2 by `ZITADEL_DEFAULTINSTANCE_FEATURES_LOGINV2_REQUIRED: false` and it should resolve the issue.
@abhishukla610 commented on GitHub (Jan 15, 2026):
I solve the situation like the following trick which is mentioned on the official zitadel doc,
First run without zitadel v2 login (disable it) -> Follow v1 to v2 migrate guide (basically need to create a service role user, give it owner role and generate pat code) -> enable v2 login and add pat code in env
Also during this process, make sure to add attributes of https mode
<!-- gh-comment-id:3756428670 -->
@abhishukla610 commented on GitHub (Jan 15, 2026):
I solve the situation like the following trick which is mentioned on the official zitadel doc,
First run without zitadel v2 login (disable it) -> Follow v1 to v2 migrate guide (basically need to create a service role user, give it owner role and generate pat code) -> enable v2 login and add pat code in env
Also during this process, make sure to add attributes of https mode
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @chasylexus on GitHub (Nov 3, 2025).
Original GitHub issue: https://github.com/Dokploy/templates/issues/516
To Reproduce
Bug Report: Zitadel self-hosted deploy on Dokploy fails with “Not Found” after setting custom subdomain
Description
I tried to deploy a self-hosted Zitadel instance using Dokploy from the built-in template, configured with a custom domain.
Here’s my setup:
dokploy.testhost.com.zitadel.dokploy.testhost.com:Problem
When I try to open the Zitadel web interface, it starts to load but then redirects to a page showing:
Current vs. Expected behavior
Expected: working web interface of Citadel
Current: websited is "trying to open" but redirects to page with json {"code":5,"message":"Not Found"}.
Provide environment information
Which area(s) are affected? (Select all that apply)
Traefik
Are you deploying the applications where Dokploy is installed or on a remote server?
Same server where Dokploy is installed
Additional context
See the attached video demonstrating the issue.
https://github.com/user-attachments/assets/87f5abfd-e672-4ae9-964c-8e16d628df3c
Will you send a PR to fix it?
No
@emretaskiran1 commented on GitHub (Nov 16, 2025):
I got same error.
@heykapil commented on GitHub (Dec 12, 2025):
Same error!
@Abhiigg commented on GitHub (Dec 30, 2025):
+1
@yavilavi commented on GitHub (Dec 31, 2025):
Same error
@lightumcc commented on GitHub (Dec 31, 2025):
+1
@abhishukla610 commented on GitHub (Jan 1, 2026):
+1
@rajatcing commented on GitHub (Jan 15, 2026):
hey folks thanks for reporting this, I will check with team as to what could we do here and update you all.
@rajatcing commented on GitHub (Jan 15, 2026):
so a quick workaround would be to disable login V2 by
ZITADEL_DEFAULTINSTANCE_FEATURES_LOGINV2_REQUIRED: falseand it should resolve the issue.@abhishukla610 commented on GitHub (Jan 15, 2026):
I solve the situation like the following trick which is mentioned on the official zitadel doc,
First run without zitadel v2 login (disable it) -> Follow v1 to v2 migrate guide (basically need to create a service role user, give it owner role and generate pat code) -> enable v2 login and add pat code in env
Also during this process, make sure to add attributes of https mode