Hi! So i've installed the Outline template.
I've set the Outline domain to knowledge.klikbit.nl and the dex domain to knowledge-dex.klikbit.nl.
Inside the advanced -> volumes tab i've edited the config.yml to: issuer: https://knowledge-dex.klikbit.nl
Bad Request
Unregistered redirect_uri ("https://knowledge.klikbit.nl/auth/oidc.callback").
Expected behavour:
Seeing Outline.
I also tried reloading the application. Seems like it doesn't want to get the changes in config.yml?
Provide environment information
OS: Ubuntu Server 24
Hosting: Hetzner
Dokploy: Version v0.28.2
Template: OutLine
Which area(s) are affected? (Select all that apply)
Docker Compose
Are you deploying the applications where Dokploy is installed or on a remote server?
Remote server
Additional context
No response
Will you send a PR to fix it?
No
Originally created by @HeapReaper on GitHub (Mar 6, 2026).
Original GitHub issue: https://github.com/Dokploy/templates/issues/739
### To Reproduce
Hi! So i've installed the Outline template.
I've set the Outline domain to knowledge.klikbit.nl and the dex domain to knowledge-dex.klikbit.nl.
Inside the advanced -> volumes tab i've edited the config.yml to:
`issuer: https://knowledge-dex.klikbit.nl`
```
redirectURIs:
- "https://knowledge.klikbit.nl/auth/oidc.callback"
```
and i've set the enviroment vars to:
```
URL=https://knowledge.klikbit.nl
DEX_URL=https://knowledge-dex.klikbit.nl
DOMAIN_NAME=knowledge.klikbit.nl
```
Then i redeployed Outline
### Current vs. Expected behavior
Current behavour:
```
Bad Request
Unregistered redirect_uri ("https://knowledge.klikbit.nl/auth/oidc.callback").
```
Expected behavour:
Seeing Outline.
I also tried reloading the application. Seems like it doesn't want to get the changes in config.yml?
### Provide environment information
```bash
OS: Ubuntu Server 24
Hosting: Hetzner
Dokploy: Version v0.28.2
Template: OutLine
```
### Which area(s) are affected? (Select all that apply)
Docker Compose
### Are you deploying the applications where Dokploy is installed or on a remote server?
Remote server
### Additional context
_No response_
### Will you send a PR to fix it?
No
GiteaMirror
added the bug label 2026-07-16 05:15:18 -05:00
Hi @HeapReaper! I'm Dosu and I’m helping the dokploy team.
The issue is that the Dex configuration in the Outline template is embedded directly in the template.toml file, not stored as a separate volume file. Editing config.yml in the volumes tab won't work because that config is dynamically generated from the template when deployed.
Looking at the template.toml, the Dex config uses template variables like ${main_domain} and ${dex_domain} which are substituted at deployment time.
To fix this, you have a few options:
Redeploy with correct variables - Make sure main_domain is set to knowledge.klikbit.nl and dex_domain is set to knowledge-dex.klikbit.nl when deploying the template.
Manually update the mounted config - The config is mounted from ../files/etc/dex/config.yaml:/etc/dex/config.yaml per the docker-compose.yml. You may need to find and edit the actual generated file in the Dokploy files directory, not through the volumes tab.
Restart the Dex container after making changes - Dex won't pick up config changes without a container restart.
Also note: the template defaults to http:// URLs, but you're using https://. Make sure your redirect URI scheme (https://) matches exactly in both the Dex config and Outline environment variables.
<!-- gh-comment-id:4015604511 -->
@dosubot[bot] commented on GitHub (Mar 6, 2026):
<!-- Greeting -->
Hi @HeapReaper! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the dokploy team.
<!-- Answer -->
The issue is that the Dex configuration in the Outline template is **embedded directly in the `template.toml` file**, not stored as a separate volume file. Editing `config.yml` in the volumes tab won't work because that config is dynamically generated from the template when deployed.
Looking at the [template.toml](https://github.com/Dokploy/templates/blob/d157cef3c357550aff801c336b99611813b522ae/blueprints/outline/template.toml#L28-L66), the Dex config uses template variables like `${main_domain}` and `${dex_domain}` which are substituted at deployment time.
**To fix this**, you have a few options:
1. **Redeploy with correct variables** - Make sure `main_domain` is set to `knowledge.klikbit.nl` and `dex_domain` is set to `knowledge-dex.klikbit.nl` when deploying the template.
2. **Manually update the mounted config** - The config is mounted from `../files/etc/dex/config.yaml:/etc/dex/config.yaml` per the [docker-compose.yml](https://github.com/Dokploy/templates/blob/d157cef3c357550aff801c336b99611813b522ae/blueprints/outline/docker-compose.yml#L30). You may need to find and edit the actual generated file in the Dokploy files directory, not through the volumes tab.
3. **Restart the Dex container** after making changes - Dex won't pick up config changes without a container restart.
Also note: the template defaults to `http://` URLs, but you're using `https://`. Make sure your redirect URI scheme (`https://`) matches exactly in both the Dex config and Outline environment variables.
<!-- Dosu Comment Footer -->
*To reply, just mention [@dosu](https://go.dosu.dev/dosubot).*
---
<sup>How did I do? [Good](https://app.dosu.dev/response-feedback/1f580174-6c22-4139-882b-d91d2e62ad10?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/1f580174-6c22-4139-882b-d91d2e62ad10?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/1f580174-6c22-4139-882b-d91d2e62ad10?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/1f580174-6c22-4139-882b-d91d2e62ad10?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/1f580174-6c22-4139-882b-d91d2e62ad10?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/1f580174-6c22-4139-882b-d91d2e62ad10?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/1f580174-6c22-4139-882b-d91d2e62ad10?feedback_type=other)</sup>
[](https://app.dosu.dev/6bf07378-6531-485c-acb5-f8edab4b0c01/ask?utm_source=github) [](https://cursor.com/link/prompt?text=The%20issue%20is%20that%20the%20Dex%20configuration%20in%20the%20Outline%20template%20is%20%2A%2Aembedded%20directly%20in%20the%20%60template.toml%60%20file%2A%2A%2C%20not%20stored%20as%20a%20separate%20volume%20file.%20Editing%20%60config.yml%60%20in%20the%20volumes%20tab%20won%27t%20work%20because%20that%20config%20is%20dynamically%20generated%20from%20the%20template%20when%20deployed.%0A%0ALooking%20at%20the%20%5Btemplate.toml%5D%28https%3A//github.com/Dokploy/templates/blob/d157cef3c357550aff801c336b99611813b522ae/blueprints/outline/template.toml%23L28-L66%29%2C%20the%20Dex%20config%20uses%20template%20variables%20like%20%60%24%7Bmain_domain%7D%60%20and%20%60%24%7Bdex_domain%7D%60%20which%20are%20substituted%20at%20deployment%20time.%0A%0A%2A%2ATo%20fix%20this%2A%2A%2C%20you%20have%20a%20few%20options%3A%0A%0A1.%20%2A%2ARedeploy%20with%20correct%20variables%2A%2A%20-%20Make%20sure%20%60main_domain%60%20is%20set%20to%20%60knowledge.klikbit.nl%60%20and%20%60dex_domain%60%20is%20set%20to%20%60knowledge-dex.klikbit.nl%60%20when%20deploying%20the%20template.%0A%0A2.%20%2A%2AManually%20update%20the%20mounted%20config%2A%2A%20-%20The%20config%20is%20mounted%20from%20%60../files/etc/dex/config.yaml%3A/etc/dex/config.yaml%60%20per%20the%20%5Bdocker-compose.yml%5D%28https%3A//github.com/Dokploy/templates/blob/d157cef3c357550aff801c336b99611813b522ae/blueprints/outline/docker-compose.yml%23L30%29.%20You%20may%20need%20to%20find%20and%20edit%20the%20actual%20generated%20file%20in%20the%20Dokploy%20files%20directory%2C%20not%20through%20the%20volumes%20tab.%0A%0A3.%20%2A%2ARestart%20the%20Dex%20container%2A%2A%20after%20making%20changes%20-%20Dex%20won%27t%20pick%20up%20config%20changes%20without%20a%20container%20restart.%0A%0AAlso%20note%3A%20the%20template%20defaults%20to%20%60http%3A//%60%20URLs%2C%20but%20you%27re%20using%20%60https%3A//%60.%20Make%20sure%20your%20redirect%20URI%20scheme%20%28%60https%3A//%60%29%20matches%20exactly%20in%20both%20the%20Dex%20config%20and%20Outline%20environment%20variables.) [](https://go.dosu.dev/discord-bot) [](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/Dokploy/dokploy/issues/3908)
Share context across your team and agents. Try Dosu.
<!-- gh-comment-id:4015610804 -->
@dosubot[bot] commented on GitHub (Mar 7, 2026):
<!-- Answer -->
The issue is that Dex doesn't automatically reload configuration changes - you need to restart the Dex container after editing `config.yaml`.
Here's what's happening:
1. The [Outline template defaults to HTTP for redirect URIs](https://github.com/Dokploy/templates/blob/d157cef3c357550aff801c336b99611813b522ae/blueprints/outline/template.toml#L62-L63), but your domain uses HTTPS
2. [Dex requires a container restart to pick up config changes](https://github.com/Dokploy/dokploy/issues/3908) - editing the file alone isn't enough
**To fix this:**
1. SSH into your server and locate the config file at:
```
<COMPOSE_PATH>/<your-compose-app-name>/files/etc/dex/config.yaml
```
2. Ensure the `redirectURIs` uses **HTTPS** (matching your actual domain):
```yaml
redirectURIs:
- "https://knowledge.klikbit.nl/auth/oidc.callback"
```
3. **Restart the Dex container** (not just Outline) - this is the key step. The config won't apply until Dex restarts.
4. Then restart Outline as well.
If you're editing via Dokploy's Advanced → Volumes tab, make sure you're restarting the Dex service specifically, not just redeploying Outline.
<!-- Dosu Comment Footer -->
*To reply, just mention [@dosu](https://go.dosu.dev/dosubot?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=reply-with-mention&utm_term=Dokploy%2Ftemplates).*
---
Share context across your team and agents. Try [Dosu](https://dosu.dev?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-tagline&utm_term=Dokploy%2Ftemplates).
[](https://app.dosu.dev/response-feedback?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-feedback&utm_term=Dokploy%2Ftemplates#message_id=9cd5e215-421f-4bb9-9373-b79e7900617e) [](https://github.dosu.com/Dokploy/templates?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-learn-repo&utm_term=Dokploy%2Ftemplates) [](https://app.dosu.dev/signup?referrer=openSource&source=github-footer&utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-add-team&utm_term=Dokploy%2Ftemplates)
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 @HeapReaper on GitHub (Mar 6, 2026).
Original GitHub issue: https://github.com/Dokploy/templates/issues/739
To Reproduce
Hi! So i've installed the Outline template.
I've set the Outline domain to knowledge.klikbit.nl and the dex domain to knowledge-dex.klikbit.nl.
Inside the advanced -> volumes tab i've edited the config.yml to:
issuer: https://knowledge-dex.klikbit.nland i've set the enviroment vars to:
Then i redeployed Outline
Current vs. Expected behavior
Current behavour:
Expected behavour:
Seeing Outline.
I also tried reloading the application. Seems like it doesn't want to get the changes in config.yml?
Provide environment information
Which area(s) are affected? (Select all that apply)
Docker Compose
Are you deploying the applications where Dokploy is installed or on a remote server?
Remote server
Additional context
No response
Will you send a PR to fix it?
No
@dosubot[bot] commented on GitHub (Mar 6, 2026):
Hi @HeapReaper! I'm Dosu and I’m helping the dokploy team.
The issue is that the Dex configuration in the Outline template is embedded directly in the
template.tomlfile, not stored as a separate volume file. Editingconfig.ymlin the volumes tab won't work because that config is dynamically generated from the template when deployed.Looking at the template.toml, the Dex config uses template variables like
${main_domain}and${dex_domain}which are substituted at deployment time.To fix this, you have a few options:
Redeploy with correct variables - Make sure
main_domainis set toknowledge.klikbit.nlanddex_domainis set toknowledge-dex.klikbit.nlwhen deploying the template.Manually update the mounted config - The config is mounted from
../files/etc/dex/config.yaml:/etc/dex/config.yamlper the docker-compose.yml. You may need to find and edit the actual generated file in the Dokploy files directory, not through the volumes tab.Restart the Dex container after making changes - Dex won't pick up config changes without a container restart.
Also note: the template defaults to
http://URLs, but you're usinghttps://. Make sure your redirect URI scheme (https://) matches exactly in both the Dex config and Outline environment variables.To reply, just mention @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other
@dosubot[bot] commented on GitHub (Mar 7, 2026):
The issue is that Dex doesn't automatically reload configuration changes - you need to restart the Dex container after editing
config.yaml.Here's what's happening:
To fix this:
SSH into your server and locate the config file at:
Ensure the
redirectURIsuses HTTPS (matching your actual domain):Restart the Dex container (not just Outline) - this is the key step. The config won't apply until Dex restarts.
Then restart Outline as well.
If you're editing via Dokploy's Advanced → Volumes tab, make sure you're restarting the Dex service specifically, not just redeploying Outline.
To reply, just mention @dosu.
Share context across your team and agents. Try Dosu.