Docker Compose Traefik Domain not working?

[jontstaz]

Hi all,

I've got a Docker compose for a simple app containing 2 services: a JS frontend and a postgres DB. I followed the documentation regarding the adding of the Traefik labels and I've made sure to make the corresponding DNS A record on the relevant subdomain. However it seems no such Traefik service is started as when I visit the domain, it just shows the default "404 error" which appears for any domains you point to Dokploy which aren't bound to a running service.

Any help would be appreciated as I'm not sure what I've done wrong considering I followed the documentation example exactly. I also ensured the service itself is indeed running as when I bind it to an external port (3015:3000) and then visit the raw IP:3015, the login page for the service appears correctly.

My Compose file:

services:
  app:
    image: ghcr.io/maybe-finance/maybe:latest
    volumes:
      - ./storage:/rails/storage
    ports:
      - "3000"
    restart: unless-stopped
    environment:
      SELF_HOSTING_ENABLED: "true"
      RAILS_FORCE_SSL: "false"
      RAILS_ASSUME_SSL: "false"
      GOOD_JOB_EXECUTION_MODE: async
      SECRET_KEY_BASE: ${SECRET_KEY_BASE:?}
      DB_HOST: postgres
      POSTGRES_DB: ${POSTGRES_DB:-maybe_production}
      POSTGRES_USER: ${POSTGRES_USER:-maybe_user}
      POSTGRES_PASSWORD: ${POSTGRES_PASSWORD:?}
    depends_on:
      postgres:
        condition: service_healthy
    networks:
      - dokploy-network
    labels:
      - traefik.enable=true
      - traefik.http.routers.maybeapp.rule=Host(`maybe.mydomain.ai`)
      - traefik.http.routers.maybeapp.entrypoints=websecure
      - traefik.http.routers.maybeapp.tls.certResolver=letsencrypt
      - traefik.http.services.maybeapp.loadbalancer.server.port=3000
  postgres:
    image: postgres:16
    restart: unless-stopped
    volumes:
      - postgres-data:/var/lib/postgresql/data
    environment:
      POSTGRES_USER: ${POSTGRES_USER:-maybe_user}
      POSTGRES_DB: ${POSTGRES_DB:-maybe_production}
      POSTGRES_PASSWORD: ${POSTGRES_PASSWORD:?}
    healthcheck:
      test: [ "CMD-SHELL", "pg_isready -U $$POSTGRES_USER -d $$POSTGRES_DB" ]
      interval: 5s
      timeout: 5s
      retries: 5
    networks:
      - dokploy-network
volumes:
  postgres-data:
networks:
  dokploy-network:
    external: true

[Siumauricio]

Hi, everything seems right, would you mind to share the traefik.yml from the traefik file system tab, and also share what version you have?

[jontstaz]

Hi, yes that's why it's strange that it's not working. And sure, below is the traefik.yml from the traefik file system tab (just censored my email). I haven't made any manual edits to this file FYI.

I'm running on the latest version, v0.2.2.

providers:
  file:
    directory: /etc/dokploy/traefik/dynamic
    watch: true
entryPoints:
  web:
    address: ':80'
    http:
      redirections:
        entryPoint:
          to: websecure
          scheme: https
          permanent: true
  websecure:
    address: ':443'
    http:
      tls:
        certResolver: letsencrypt
api:
  insecure: true
certificatesResolvers:
  letsencrypt:
    acme:
      email: [email protected]
      storage: /etc/dokploy/traefik/dynamic/acme.json
      httpChallenge:
        entryPoint: web

[Siumauricio]

Looks like you didn't apply the migration we specified in the release notes in the v0.2.0, check here, follow the Note and let me know if you still have issues!

https://github.com/Dokploy/dokploy/releases/tag/v0.2.0