[Bug] Coolify deployment fails with "No available server" (Missing Traefik port label)

[TrevorLowing]

Here is a draft for the GitHub issue. You can copy and paste this directly into the "Issues" tab of the repo.

---

Title: [Bug] Coolify deployment fails with "No available server" (Missing Traefik port label)

Description:
When deploying this template on Coolify, the application starts successfully and logs that it is listening on port 18789. However, the generated URL returns a 503 Service Unavailable / "No available server" error.

This appears to happen because Traefik defaults to routing traffic to port 80 inside the container, but OpenClaw is listening on 18789. The docker-compose.yml is missing the specific label to tell Traefik which internal port to use.

Steps to Reproduce:

1. Create a new service in Coolify using this repository as the source.
2. Deploy the service.
3. Wait for logs to show [gateway] listening on ws://0.0.0.0:18789.
4. Click the generated service URL.
5. Result: Browser displays "No available server".

Proposed Solution:
Add the explicit port label to the openclaw service in docker-compose.yml so Traefik knows where to route the traffic.

In the labels: section of the openclaw service, add:

- traefik.http.services.openclaw.loadbalancer.server.port=18789

Additional Context:

• Platform: Coolify v4 (Beta)
• Container Status: Running
• Logs: Confirm the app is active: [gateway] listening on ws://0.0.0.0:18789

---

[essamamdani]

Follow this https://coolify.io/docs/knowledge-base/docker/compose#coolify-s-magic-environment-variables