Dokploy / Dokploy/dokploy

Compose domains not generating Traefik config → all routes return 404

Open
#4,324 12 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

awaiting-feedback
Dominant language
TypeScript
Stars
37.4k
Forks
3k
Avg merge
1d 3h
Merged PRs (30d)
73

Description

To Reproduce

To Reproduce

  1. Deploy a Docker Compose app with two services:
    • client running on port 3002
    • backend running on port 3001
  2. Configure domains in Dokploy:
    • example.com → service client → path / → port 3002
    • example.com → service backend → path /api → port 3001
  3. Redeploy the compose
  4. Check Traefik dynamic config directory:

ls /etc/dokploy/traefik/dynamic
5. Access:
`https://example.com

https://example.com/api/config`

Current vs. Expected behavior

Expected:

  • Dokploy generates a dynamic Traefik config file for the compose
  • Routes:
    • / → client (3002)
    • /api → backend (3001)
  • App loads correctly

Actual:

  • No dynamic config file is created for this compose
  • /etc/dokploy/traefik/dynamic does not contain any file for this app
  • All routes return 404
  • Containers are running and healthy
Provide environment information
Ubuntu 20.04
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?

Same server where Dokploy is installed

Additional context

No response

Will you send a PR to fix it?

No

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the Docker Compose deployment and checking /etc/dokploy/traefik/dynamic after redeploy. Trace how the two configured domains and paths are converted into Traefik configuration; done means a dynamic config file is created and / routes to the client while /api routes to the backend without 404 responses.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker-compose
Domain
devops, infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.