Potential bug Report: Zitadel self-hosted deploy on Dokploy fails #145

New Issue

GiteaMirror · 2025-11-22T20:31:09-06:00

GiteaMirror commented

2025-11-22 20:31:09 -06:00

Originally created by @chasylexus on GitHub (Nov 3, 2025).

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 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?

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

Originally created by @chasylexus on GitHub (Nov 3, 2025). ### 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

GiteaMirror commented

2025-11-22 20:31:10 -06:00

@emretaskiran1 commented on GitHub (Nov 16, 2025):

I got same error.

@emretaskiran1 commented on GitHub (Nov 16, 2025): I got same error.

GiteaMirror referenced this issue

2025-11-22 20:36:36 -06:00

[PR #326] [CLOSED] Add NTFY (Item requested on issue #145) #367

GiteaMirror referenced this issue

2025-11-22 20:36:50 -06:00

[PR #328] [MERGED] feat: add ntfy (Item requested on issue #145) #369

Sign in to join this conversation.