Coolify
Nimbox SRE monitors a Coolify installation without write credentials. The agent detects Coolify on its own, but to read applications, services, deployments, backups and certificates it needs a read-only API token.
Until that token exists, the coolify-core check reports a problem. It does not mean Coolify is broken: it means you are not watching it.
1. Enable the API
In Coolify, go to Settings → API and enable API access. It is off by default.
If you keep an allowlist of addresses, add the server's own: the agent asks from the same machine, against localhost.
2. Create a read-only token
Under Keys & Tokens → API tokens, create a new one:
| Field | Value |
|---|---|
| Permissions | read-only |
| Expiration | Never |
Read-only, and nothing more
Do not use root or *. The agent only reads, and a write-capable token sitting on disk is one key too many: anyone who could read that file could deploy, stop or delete services.
Never is a deliberate choice. A token that expires turns monitoring into something that switches itself off on an ordinary Tuesday months later, and nobody finds out until they need it.
Copy the token now: Coolify will not show it again.
3. Hand it to the agent
On the server running Coolify:
install -d -m 0700 /etc/nimboxsre-agent
printf '%s' 'YOUR_TOKEN' > /etc/nimboxsre-agent/coolify.token
chmod 0600 /etc/nimboxsre-agent/coolify.token
systemctl restart nimboxsre-agent
The permissions are not optional
The agent rejects the file if anyone other than its owner can read it, and the check stays red saying it must be 0600. That is on purpose: a token anyone can read is not a token.
Use printf rather than echo so no trailing newline is written. The agent would trim it, but it is better not to add it.
What you get when it works
The host page gains the Coolify cards:
- Platform: version, server state, and whether the metrics engine is enabled.
- Applications and Services: what is running, what is stopped, and what reports itself unhealthy.
- Healthchecks: public applications whose state is inconclusive. It shows up as a recommendation, not a fault: the applications are running, what is missing is a declared healthcheck.
- Deployments, Backups, Certificates and Image storage.
Quick troubleshooting
| Symptom | Action |
|---|---|
falta /etc/nimboxsre-agent/coolify.token |
Step 3 has not been done yet. |
debe tener permisos 0600 |
Run chmod 0600 on the token file. |
| API is not authenticated | The token is invalid, or the API is still disabled. Redo steps 1 and 2. |
| API connection error | Coolify is not listening on the default port. Set api_url in the detector configuration. |
| Coolify does not appear on the host page | The agent looks for the installation directory in the standard path. If you moved it, point at it with root in the detector configuration. |
What it does not do
The token is read-only and the agent never writes: it does not deploy, restart, or change configuration. If you want the agent to act on an incident, that is decided in the panel and carried out over the remote access channels, not through the Coolify API.