The issue already exists in the Zitadel repo's issues. A guy has already mentioned that we can set the feature flag to the login page v1. https://github.com/zitadel/zitadel/issues/10526
If they want to use login ui v2, they go to the settings page and switch it later, or they can also build their own UI for their business.
Steps to Reproduce the Error
Deploy with the current Zitadel template.
Go to page /ui/console
It returns the error 404 Not found.
Environment Information
Ubuntu 20.04
Dokploy latest
When does this error occur?
After successful deployment
Additional Context
No response
Will you send a PR to fix it?
Yes
Originally created by @quochuydev on GitHub (Nov 21, 2025).
Original GitHub issue: https://github.com/Dokploy/templates/issues/543
### Template Name
Zitadel
### Relevant Logs of the Error
<img width="357" height="67" alt="Image" src="https://github.com/user-attachments/assets/c3d362cf-2145-49a5-97cd-680de8ee0ae0" />
The issue already exists in the Zitadel repo's issues. A guy has already mentioned that we can set the feature flag to the login page v1. [https://github.com/zitadel/zitadel/issues/10526](https://github.com/zitadel/zitadel/issues/10526)
If they want to use login ui v2, they go to the settings page and switch it later, or they can also build their own UI for their business.
### Steps to Reproduce the Error
1. Deploy with the current Zitadel template.
2. Go to page `/ui/console`
3. It returns the error 404 Not found.
### Environment Information
```bash
Ubuntu 20.04
Dokploy latest
```
### When does this error occur?
After successful deployment
### Additional Context
_No response_
### Will you send a PR to fix it?
Yes
GiteaMirror
added the bug label 2026-05-21 22:34:14 -05:00
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 @quochuydev on GitHub (Nov 21, 2025).
Original GitHub issue: https://github.com/Dokploy/templates/issues/543
Template Name
Zitadel
Relevant Logs of the Error
The issue already exists in the Zitadel repo's issues. A guy has already mentioned that we can set the feature flag to the login page v1. https://github.com/zitadel/zitadel/issues/10526
If they want to use login ui v2, they go to the settings page and switch it later, or they can also build their own UI for their business.
Steps to Reproduce the Error
/ui/consoleEnvironment Information
When does this error occur?
After successful deployment
Additional Context
No response
Will you send a PR to fix it?
Yes