Certificates not always generated

[rbalet]

I've read the Troubleshooting documentation.

I'm pretty sure I follow the domains article to the letter,
and when I try to connect I get the "Your connection is not private".

So this seems indeed to be a certificate not being generated kind of problem.
I've looked at my Traefik acme.json file and my new domain is indeed not being added in there.

I do have error inside my Traefik log

2026-01-02T05:22:11Z ERR Cannot retrieve the ACME challenge for dyn.83-228-212-024.dsl.vtx.ch (token "index.php") providerName=acme
2026-01-04T12:39:43Z ERR Unable to get token error="missing token" providerName=acme
2026-01-06T15:23:29Z ERR error="accept tcp [::]:8080: use of closed network connection" entryPointName=traefik
2026-01-06T15:23:29Z ERR Error while starting server error="accept tcp [::]:8080: use of closed network connection" entryPointName=traefik

But I can access the 8080 port, so I don't understand.. :/

Does anyone have an Idea, already had face this error and found a solution ?
(I'd like not having to delete my dokploy instance and restart it, I know normally this is the way to get this fixed)

Thanks in advance

[djsisson]

can you describe your setup, the error is in lines 1 and 2, ignore the closed connection on 8080 that's nothing
have you made any custom routes/priorities middleware yourself?, as the token request was not routed correctly, it got routed to index.php so the acme challenge failed.

[rbalet]

@djsisson Yes they are, this is the compose file

services:
  api:
    container_name: foo-bar
    build:
      context: .
      dockerfile: Dockerfile
    environment:
      - PORT=${PORT}
    ports:
      - ${PORT}
      - 80
    volumes:
      - ./src:/app/src
    healthcheck:
      test:
        - CMD-SHELL
        - curl -f http://localhost:${PORT}/healthcheck || exit 1
      interval: 10s
      timeout: 5s
      retries: 3
    labels:
      - traefik.docker.network=dokploy-network
      - traefik.http.routers.up4it-api-z1erno-4-web.rule=Host(`bar.foo.io`)
      - traefik.http.routers.up4it-api-z1erno-4-web.entrypoints=web
      - traefik.http.services.up4it-api-z1erno-4-web.loadbalancer.server.port=3000
      - traefik.http.routers.up4it-api-z1erno-4-web.service=foo-bar-z1erno-4-web
      - traefik.http.routers.up4it-api-z1erno-4-web.middlewares=redirect-to-https@file
      - traefik.http.routers.up4it-api-z1erno-4-websecure.rule=Host(`bar.foo.io`)
      - traefik.http.routers.up4it-api-z1erno-4-websecure.entrypoints=websecure
      - traefik.http.services.up4it-api-z1erno-4-websecure.loadbalancer.server.port=3000
      - traefik.http.routers.up4it-api-z1erno-4-websecure.service=foo-bar-z1erno-4-websecure
      - traefik.http.routers.up4it-api-z1erno-4-websecure.tls.certresolver=letsencrypt
      - traefik.enable=true
    networks:
      - dokploy-network
networks:
  dokploy-network:
    external: true

[djsisson]

you sure this is working, i.e can your curl your container from the host, the volume mount looks suspect.

[rbalet]

I believe so.

This is the deployment logs:

And the app logs
[Nest] 1 - 01/10/2026, 6:48:48 PM VERBOSE Server running on http://[::1]:3000

---

But

• I do understand that the ports looks strange (I found it in the dokploy documentation
• maybe the error could be on the http://[::1]:3000 as I red that Traefik may not have access to ::1.

I'll investigate those two points.
Please, let me know if you have any other idea.

[djsisson]

Yeah that's ipv6 loopack you need either 0.0.0.0 or :: also double check healthcheck as if that's not returning ok traefik also won't route to the container

[rbalet]

Well, I've

1. Removed the Health check.
2. changed my api to run on http://127.0.0.1:3000

and it fixed the issue.
So thanks @djsisson a lot for your help.

I'm wondering though if this would be possible to show somehow that Traefik couldn't be ran or something of the sort.
Because the newbie that I am just think "That's green so it should work".

What do you think ? (I'd be glad to open an issue, but you're more experience on that topic)

Thanks again !!