github-starred/templates
2
0
Fork 1
mirror of https://github.com/Dokploy/templates.git synced 2026-05-08 09:38:42 -05:00
Code Issues 1.2k Packages Projects Releases Wiki Activity

[GH-ISSUE #516] Potential bug Report: Zitadel self-hosted deploy on Dokploy fails #679

New Issue
Open
opened 2026-04-16 11:12:17 -05:00 by GiteaMirror · 9 comments
GiteaMirror commented 2026-04-16 11:12:17 -05:00
Owner
Copy Link

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:

{"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). 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
GiteaMirror commented 2026-04-16 11:12:18 -05:00
Author
Owner
Copy Link

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

I got same error.

<!-- gh-comment-id:3539167750 --> @emretaskiran1 commented on GitHub (Nov 16, 2025): I got same error.
GiteaMirror commented 2026-04-16 11:12:18 -05:00
Author
Owner
Copy Link

@heykapil commented on GitHub (Dec 12, 2025):

Same error!

<!-- gh-comment-id:3645133390 --> @heykapil commented on GitHub (Dec 12, 2025): Same error!
GiteaMirror commented 2026-04-16 11:12:19 -05:00
Author
Owner
Copy Link

@Abhiigg commented on GitHub (Dec 30, 2025):

+1

<!-- gh-comment-id:3698632459 --> @Abhiigg commented on GitHub (Dec 30, 2025): +1
GiteaMirror commented 2026-04-16 11:12:19 -05:00
Author
Owner
Copy Link

@yavilavi commented on GitHub (Dec 31, 2025):

Same error

<!-- gh-comment-id:3700915200 --> @yavilavi commented on GitHub (Dec 31, 2025): Same error
GiteaMirror commented 2026-04-16 11:12:20 -05:00
Author
Owner
Copy Link

@lightumcc commented on GitHub (Dec 31, 2025):

+1

<!-- gh-comment-id:3702333539 --> @lightumcc commented on GitHub (Dec 31, 2025): +1
GiteaMirror commented 2026-04-16 11:12:20 -05:00
Author
Owner
Copy Link

@abhishukla610 commented on GitHub (Jan 1, 2026):

+1

<!-- gh-comment-id:3703850287 --> @abhishukla610 commented on GitHub (Jan 1, 2026): +1
GiteaMirror commented 2026-04-16 11:12:21 -05:00
Author
Owner
Copy Link

@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.

<!-- 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.
GiteaMirror commented 2026-04-16 11:12:22 -05:00
Author
Owner
Copy Link

@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.

<!-- 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.
GiteaMirror commented 2026-04-16 11:12:24 -05:00
Author
Owner
Copy Link

@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
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
documentation
pull-request
Mirrored from GitHub Pull Request
 template
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/templates#679
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?