Note,
A fresh DNS record existed, but my Mac still said the domain did not
I checked a domain too early. The record went live, but my Mac kept the earlier negative answer.
Notes
One incident, one trap, one fix at a time. Written the day it happened, not tidied up after the fact.
Note,
Put a feature branch on an existing Coolify URL, then put it back
The URL stayed the same. I changed which Git branch Coolify built for that one app.
Note,
Check the offsite copy of a Coolify compose database backup
A successful local dump and an offsite backup are two different claims. Check both before promising recovery.
Note,
Two Umami first-boot checks I nearly missed on Coolify
A working analytics URL was only the start. I still had to close the default login and finish the domain setup.
Note,
Choosing a VPS in Australia for self-hosting
AUD billing, local latency and a familiar setup won my May 2026 decision. The concentration risk was real.
Note,
Point your app at a Coolify Postgres by container name, not IP
The database container IP can change on restart. The service name is the useful address inside the Docker network.
Note,
A launchd job that dies with no code change
Nothing in the script changed. The permission under it did.
Note,
Coolify quietly bakes your build secrets into the image layers
Docker history on one of my images printed out a GitHub token, an OAuth token, and a handful of other secrets in plain text. Here is why, and the actual fix.
Note,
A full VPS disk on Coolify: 1905 MB per rebuild, down to 31 MB
The disk didn't fill for one reason. It filled for four, and only one of them was obvious.
Note,
The Next.js standalone healthcheck trap on Coolify
The build succeeded. The container came up. Coolify still called it unhealthy.
Note,
serve -s makes every URL on a multi-page site come back 200
Every URL returned 200. That was the problem.