github-starred/templates
2
0
Fork 1
mirror of https://github.com/Dokploy/templates.git synced 2026-11-11 13:38:07 -06:00
Code Issues 3.0k Packages Projects Releases Wiki Activity

Compose domain assignation problem #155

New Issue
Open
opened 2025-11-22 20:31:16 -06:00 by GiteaMirror · 4 comments
GiteaMirror commented 2025-11-22 20:31:16 -06:00
Owner
Copy Link
Copy Source

Originally created by @MaximePremont on GitHub (Nov 15, 2025).

To Reproduce

  1. Configure Dokploy with a letsencrypt domain
  2. Create a projet, and an app from template "Registry"
  3. Assign a domain to this registry
  4. Try to connect to it

docker login https://mydomain.com
Response :
`Error response from daemon: Get "https://mydomain.com/v2/": tls: failed to verify certificate: x509: certificate is valid for b4b8f18b9069f2169954d7fd1602f25b.0b24b28c0281864c569a4b8570fccc3c.traefik.default, not mydomain.com

Current vs. Expected behavior

I tried with default projets, or traefik domains, custom domains.
Always the same error.

Provide environment information

Debian 12
Lastest dokploy version when publishing this ( tried to reinstall )
Hetzner vps

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

EDIT :

Seems that the problem is with compose and not the registry template, please see my next messages.

Originally created by @MaximePremont on GitHub (Nov 15, 2025). ### To Reproduce 1. Configure Dokploy with a letsencrypt domain 2. Create a projet, and an app from template "Registry" 3. Assign a domain to this registry 4. Try to connect to it `docker login https://mydomain.com` Response : `Error response from daemon: Get "https://mydomain.com/v2/": tls: failed to verify certificate: x509: certificate is valid for b4b8f18b9069f2169954d7fd1602f25b.0b24b28c0281864c569a4b8570fccc3c.traefik.default, not mydomain.com ### Current vs. Expected behavior I tried with default projets, or traefik domains, custom domains. Always the same error. ### Provide environment information ```bash Debian 12 Lastest dokploy version when publishing this ( tried to reinstall ) Hetzner vps ``` ### 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 # EDIT : Seems that the problem is with compose and not the registry template, please see my next messages.
GiteaMirror commented 2025-11-22 20:31:17 -06:00
Author
Owner
Copy Link
Copy Source

@MaximePremont commented on GitHub (Nov 15, 2025):

The problem may be a bit more complex, it seems that there is no dynamic traefik file generated, and I just saw someone have the same problem with a wordpress template today so it may be a more global problem with compose and domains.

@MaximePremont commented on GitHub (Nov 15, 2025): The problem may be a bit more complex, it seems that there is no dynamic traefik file generated, and I just saw someone have the same problem with a wordpress template today so it may be a more global problem with compose and domains.
GiteaMirror commented 2025-11-22 20:31:17 -06:00
Author
Owner
Copy Link
Copy Source

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

Hey, for problems with templates, use the repository at https://github.com/Dokploy/templates. As I see it, you are using HTTPS with traefik.me domains, which cannot be configured. To do this, use your own domain. You can also consult the documentation for that template at https://distribution.github.io/distribution/about/.

@Siumauricio commented on GitHub (Nov 16, 2025): Hey, for problems with templates, use the repository at https://github.com/Dokploy/templates. As I see it, you are using HTTPS with traefik.me domains, which cannot be configured. To do this, use your own domain. You can also consult the documentation for that template at https://distribution.github.io/distribution/about/.
GiteaMirror commented 2025-11-22 20:31:17 -06:00
Author
Owner
Copy Link
Copy Source

@MaximePremont commented on GitHub (Nov 17, 2025):

Hello @Siumauricio , as indicated in my second message it seems that the problem is related to compose in general and not only with this template.

Also : as I mentioned in my first message, I am using my own domain, and it is precisely a problem if a Traefik domain is associated with it : I have deleted the Traefik domain and specified my own domain for HTTPS.
Also, as I explained, no dynamic files for the compose seem to be created, and I don't know if this is normal.

Same for custom personal compose or other templates like Odoo or WordPress : domain assignation not working, no traefik router/service

Notice that : routers and services are not showed on the traefik dashboard, even if the labels are shown in the converted compose :

  registry:
    restart: always
    image: registry:2
    ports:
      - 5000:5000
    volumes:
      - ../files/auth/registry.password:/auth/registry.password
      - registry-data:/var/lib/registry
    environment:
      REGISTRY_STORAGE_DELETE_ENABLED: true
      REGISTRY_HEALTH_STORAGEDRIVER_ENABLED: false
      REGISTRY_HTTP_SECRET: ${REGISTRY_HTTP_SECRET}
      REGISTRY_AUTH: htpasswd
      REGISTRY_AUTH_HTPASSWD_REALM: Registry Realm
      REGISTRY_AUTH_HTPASSWD_PATH: /auth/registry.password
    networks:
      - smer-registry-u0edp3
    labels:
      - traefik.http.routers.smer-registry-u0edp3-13-web.rule=Host(`example.com`)
      - traefik.http.routers.smer-registry-u0edp3-13-web.entrypoints=web
      - traefik.http.services.smer-registry-u0edp3-13-web.loadbalancer.server.port=5000
      - traefik.http.routers.smer-registry-u0edp3-13-web.service=smer-registry-u0edp3-13-web
      - traefik.http.routers.smer-registry-u0edp3-13-web.middlewares=redirect-to-https@file
      - traefik.http.routers.smer-registry-u0edp3-13-websecure.rule=Host(`example.com`)
      - traefik.http.routers.smer-registry-u0edp3-13-websecure.entrypoints=websecure
      - traefik.http.services.smer-registry-u0edp3-13-websecure.loadbalancer.server.port=5000
      - traefik.http.routers.smer-registry-u0edp3-13-websecure.service=smer-registry-u0edp3-13-websecure
      - traefik.http.routers.smer-registry-u0edp3-13-websecure.tls.certresolver=letsencrypt
      - traefik.enable=true
volumes:
  registry-data: null
networks:
  smer-registry-u0edp3:
    name: smer-registry-u0edp3
    external: true
@MaximePremont commented on GitHub (Nov 17, 2025): Hello @Siumauricio , as indicated in my second message it seems that the problem is related to compose in general and not only with this template. Also : as I mentioned in my first message, **I am using my own domain**, and it is precisely a problem if a Traefik domain is associated with it : I have deleted the Traefik domain and specified my own domain for HTTPS. Also, as I explained, no dynamic files for the compose seem to be created, and I don't know if this is normal. ## Same for custom personal compose or other templates like Odoo or WordPress : domain assignation not working, no traefik router/service **Notice that : routers and services are not showed on the traefik dashboard, even if the labels are shown in the converted compose** : ```services: registry: restart: always image: registry:2 ports: - 5000:5000 volumes: - ../files/auth/registry.password:/auth/registry.password - registry-data:/var/lib/registry environment: REGISTRY_STORAGE_DELETE_ENABLED: true REGISTRY_HEALTH_STORAGEDRIVER_ENABLED: false REGISTRY_HTTP_SECRET: ${REGISTRY_HTTP_SECRET} REGISTRY_AUTH: htpasswd REGISTRY_AUTH_HTPASSWD_REALM: Registry Realm REGISTRY_AUTH_HTPASSWD_PATH: /auth/registry.password networks: - smer-registry-u0edp3 labels: - traefik.http.routers.smer-registry-u0edp3-13-web.rule=Host(`example.com`) - traefik.http.routers.smer-registry-u0edp3-13-web.entrypoints=web - traefik.http.services.smer-registry-u0edp3-13-web.loadbalancer.server.port=5000 - traefik.http.routers.smer-registry-u0edp3-13-web.service=smer-registry-u0edp3-13-web - traefik.http.routers.smer-registry-u0edp3-13-web.middlewares=redirect-to-https@file - traefik.http.routers.smer-registry-u0edp3-13-websecure.rule=Host(`example.com`) - traefik.http.routers.smer-registry-u0edp3-13-websecure.entrypoints=websecure - traefik.http.services.smer-registry-u0edp3-13-websecure.loadbalancer.server.port=5000 - traefik.http.routers.smer-registry-u0edp3-13-websecure.service=smer-registry-u0edp3-13-websecure - traefik.http.routers.smer-registry-u0edp3-13-websecure.tls.certresolver=letsencrypt - traefik.enable=true volumes: registry-data: null networks: smer-registry-u0edp3: name: smer-registry-u0edp3 external: true ```
GiteaMirror commented 2025-11-22 20:31:17 -06:00
Author
Owner
Copy Link
Copy Source

@MaximePremont commented on GitHub (Nov 17, 2025):

I just foud out that in my Dokploy logs, I am spammed with thoses messages :

2025-11-17T15:42:54Z ERR Failed to retrieve information of the docker client and server host error="Error response from daemon: client version 1.24 is too old. Minimum supported API version is 1.44, please upgrade your client to a newer version" providerName=swarm
2025-11-17T15:42:54Z ERR Provider error, retrying in 2.109967731s error="Error response from daemon: client version 1.24 is too old. Minimum supported API version is 1.44, please upgrade your client to a newer version" providerName=swarm
2025-11-17T15:42:56Z ERR Failed to retrieve information of the docker client and server host error="Error response from daemon: client version 1.24 is too old. Minimum supported API version is 1.44, please upgrade your client to a newer version" providerName=swarm
2025-11-17T15:42:56Z ERR Provider error, retrying in 4.025365163s error="Error response from daemon: client version 1.24 is too old. Minimum supported API version is 1.44, please upgrade your client to a newer version" providerName=swarm
2025-11-17T15:42:57Z ERR Failed to retrieve information of the docker client and server host error="Error response from daemon: client version 1.24 is too old. Minimum supported API version is 1.44, please upgrade your client to a newer version" providerName=docker
2025-11-17T15:42:57Z ERR Provider error, retrying in 12.756002413s error="Error response from daemon: client version 1.24 is too old. Minimum supported API version is 1.44, please upgrade your client to a newer version" providerName=docker

After some search, it seems that a change with the docker API/traefik cause this error, and it seems that for some people this error means that the labels for traefik/compose are now not working.
So I think that the problem is linked to this error.

EDIT AND SOLUTION

I added :

"min-api-version": "1.24"

to /etc/docker/daemon.json and it works now, so the problem is the docker api version used by traefik

@MaximePremont commented on GitHub (Nov 17, 2025): I just foud out that in my Dokploy logs, I am spammed with thoses messages : ```2025-11-17T15:42:53Z ERR Provider error, retrying in 1.194691696s error="Error response from daemon: client version 1.24 is too old. Minimum supported API version is 1.44, please upgrade your client to a newer version" providerName=swarm 2025-11-17T15:42:54Z ERR Failed to retrieve information of the docker client and server host error="Error response from daemon: client version 1.24 is too old. Minimum supported API version is 1.44, please upgrade your client to a newer version" providerName=swarm 2025-11-17T15:42:54Z ERR Provider error, retrying in 2.109967731s error="Error response from daemon: client version 1.24 is too old. Minimum supported API version is 1.44, please upgrade your client to a newer version" providerName=swarm 2025-11-17T15:42:56Z ERR Failed to retrieve information of the docker client and server host error="Error response from daemon: client version 1.24 is too old. Minimum supported API version is 1.44, please upgrade your client to a newer version" providerName=swarm 2025-11-17T15:42:56Z ERR Provider error, retrying in 4.025365163s error="Error response from daemon: client version 1.24 is too old. Minimum supported API version is 1.44, please upgrade your client to a newer version" providerName=swarm 2025-11-17T15:42:57Z ERR Failed to retrieve information of the docker client and server host error="Error response from daemon: client version 1.24 is too old. Minimum supported API version is 1.44, please upgrade your client to a newer version" providerName=docker 2025-11-17T15:42:57Z ERR Provider error, retrying in 12.756002413s error="Error response from daemon: client version 1.24 is too old. Minimum supported API version is 1.44, please upgrade your client to a newer version" providerName=docker ``` After some search, it seems that a change with the docker API/traefik cause this error, and it seems that for some people this error means that the labels for traefik/compose are now not working. So I think that the problem is linked to this error. # EDIT AND SOLUTION I added : ``` "min-api-version": "1.24" ``` to `/etc/docker/daemon.json` and it works now, so the problem is the docker api version used by traefik
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 labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
GiteaMirror ninjasurge (Kaehlen Rog)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/templates#155