Domain no longer accessible on auto-deploy

I've got an express API server in dokploy, using a 'compose' service, and the docker-compose.yml has:

services:
  api:
    build: 
      context: .
      dockerfile: Dockerfile
    environment:
      - PORT=3003
    ports:
      - "3003:3003"
    networks:
      - dokploy-network

networks:
  dokploy-network:
    external: true

services:
  api:
    build: 
      context: .
      dockerfile: Dockerfile
    environment:
      - PORT=3003
    ports:
      - "3003:3003"
    networks:
      - dokploy-network

networks:
  dokploy-network:
    external: true

I have a domain configured which points to the service and port 3003.

When I make a new commit to the repo this auto-deploys, and then I can no longer connect to it via the domain.
HOWEVER, when I go back into domain, open it, save it (without any changes) and then redeploy, I can connect to the domain again.

Is there something I need to add to my docker-compose.yml that dokploy is doing when setting the domain?

Dokploy•11mo ago•

2 replies

Jon

Domain no longer accessible on auto-deploy

I've got an express API server in dokploy, using a 'compose' service, and the docker-compose.yml has:

services:
  api:
    build: 
      context: .
      dockerfile: Dockerfile
    environment:
      - PORT=3003
    ports:
      - "3003:3003"
    networks:
      - dokploy-network

networks:
  dokploy-network:
    external: true

services:
  api:
    build: 
      context: .
      dockerfile: Dockerfile
    environment:
      - PORT=3003
    ports:
      - "3003:3003"
    networks:
      - dokploy-network

networks:
  dokploy-network:
    external: true

Domain no longer accessible on auto-deploy

Similar Threads

Domain no longer accessible on auto-deploy

Similar Threads

Similar Threads

Similar Threads