Skip to content

fix(deploy): make docker-compose deploy correctly on Coolify - #1

Merged
Nxssie merged 1 commit into
mainfrom
fix/coolify-deploy
Jun 20, 2026
Merged

Nxssie merged 1 commit into
mainfrom
fix/coolify-deploy

Conversation

@Nxssie

@Nxssie Nxssie commented Jun 20, 2026

Copy link
Copy Markdown
Owner
  • web healthcheck: use 127.0.0.1 instead of localhost so busybox wget doesn't hit IPv6 ::1 (nginx listens IPv4-only); container now reaches healthy and Traefik keeps it in the load balancer instead of returning 503
  • drop custom networks: Coolify auto-creates the per-stack network and attaches its proxy; declaring our own multi-homes the container and causes 504s
  • remove hardcoded Traefik labels: let Coolify generate routers/TLS from the UI domain (the entrypoint name "websecure" does not exist in Coolify's Traefik)
  • switch SQLite persistence from a relative bind mount to a named volume

- web healthcheck: use 127.0.0.1 instead of localhost so busybox wget doesn't
  hit IPv6 ::1 (nginx listens IPv4-only); container now reaches healthy and
  Traefik keeps it in the load balancer instead of returning 503
- drop custom networks: Coolify auto-creates the per-stack network and attaches
  its proxy; declaring our own multi-homes the container and causes 504s
- remove hardcoded Traefik labels: let Coolify generate routers/TLS from the UI
  domain (the entrypoint name "websecure" does not exist in Coolify's Traefik)
- switch SQLite persistence from a relative bind mount to a named volume
@Nxssie
Nxssie merged commit 333bbc6 into main Jun 20, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant