Skip to content

Coolify ​

Coolify v4 runs everything on the server: builds, containers, the Traefik proxy, databases, backups and scheduled tasks. It lives at coolify.stu-bot.uk, behind Cloudflare Access.

Settings that matter ​

  • Registration: off. The first account becomes root, and it has to be created within 10 minutes of Coolify starting. Restarting the coolify container reopens that window.
  • API: on, at /api/v1, with bearer tokens.
  • MCP server: on, at /mcp. This is what Claude Code talks to. It has about 80 tools covering apps, deployments, logs, env vars, databases, backups, DNS, services and server metrics.
  • Sentinel: on, sending server metrics (CPU, memory, disk, load, network) with 7 days of history.
  • Server: "localhost". Coolify reaches the host over SSH as root from its own container, which the sshd settings allow from the Docker networks only.

Tokens ​

TokenPermissionsUsed by
Claude Code (Mac)rootthe infra plugin and CLI
ops-serviceread, deploythe ops page (restart and redeploy buttons)
claude-runner-readonlyreadClaude on the server

All of them expire after a year. Resetting the root password revokes every one of them.

GitHub ​

Coolify has its own GitHub App, installed on all my repos. On push, GitHub calls https://coolify.stu-bot.uk/webhooks/... (an Access bypass path), and Coolify deploys whichever apps watch the changed paths.

If you register a GitHub App while logged out of Coolify, the GitHub callback is lost. Log in first.

Projects ​

Resources are grouped into Coolify projects, each with a production environment. The shared pieces of the stack live in a project called platform:

ResourceTypeReach
busValkey 9internal
n8nservice: n8n + Postgres + task runnersn8n.stu-bot.uk
opsapp from apps/opsops.stu-bot.uk
claude-runnerapp from apps/claude-runnerinternal
docsapp from apps/docsdocs.stu-bot.uk (public)

Notifications ​

Coolify sends its own Telegram messages for failed deploys, failed backups, failed scheduled tasks, disk usage, the server becoming unreachable (and reachable again), and Traefik updates.

Things that caught me out ​

  • An app created without a domain gets an automatic public *.sslip.io address. For internal apps, set the domain to empty and check fqdn comes back null. The firewall now blocks direct traffic anyway, but don't rely on that alone.
  • Coolify's health checks run curl (falling back to wget) inside the container, so slim images need one of them installed.
  • A database inside a Coolify service, like n8n's Postgres, can't have backups created through /databases/{uuid}/backups in the API. Use the service's Backups tab.