Turn Coolify's ugly auto-generated URLs into short, on-brand links like replyee.t.boommedia.us — one DNS record, one Coolify field, applies to all 15 SaaS apps.
Right now, an app deployed without a domain falls back to Coolify's default — something like a1b2c3.159.65.235.140.sslip.io. It works, but it's long, unbrandable, and leaks the raw IP. The fix is to give Coolify a wildcard domain to build links from. You do it once at the server level and every app inherits it.
In whatever manages boommedia.us DNS (the same place db.boommedia.us lives), add two A records pointing at the droplet.
| Type | Name / Host | Value | |
|---|---|---|---|
| A | *.t | 159.65.235.140 | wildcard |
| A | t | 159.65.235.140 | root |
You're setting this at the server level, not per-app — that's why it applies to all 15 apps at once.
No restart needed. New domains generated from now on use the wildcard. Existing apps keep whatever domain they already have.
Two ways, per app, under its Domains section:
Click Generate Domain → Coolify hands you a random branded host with TLS already sorted:
Type a memorable host in the Domains field — cleaner than a random hash when you're sending previews to a client:
Before trusting a link, confirm DNS resolves. Run this from anywhere (your Mac, the droplet, wherever):
No dig on Windows? Use nslookup foo.t.boommedia.us in PowerShell instead — same idea.
The things that trip people up.
t = “temp” and is the shortest sensible label.
Swap it for on (echoes your .online app domains), link,
go, or app. Just use the same word in both the DNS record and the Coolify
field. Links become x.on.boommedia.us, etc.replyee.online,
displayee.online…). The wildcard only fills in the blank when an app has no
explicit domain — i.e. previews, staging, and quick shares. Both can coexist on the same app.sslip.io fallback literally puts the IP in the URL. A wildcard A record is no
different from any normal DNS record. If you later want the IP hidden, that's a separate project
(put Cloudflare proxy in front) and unrelated to this setup.dig), then in the app's Domains section
re-save / redeploy to retry issuance. Also make sure ports 80 and 443 are open on the
droplet firewall — 80 is required for the HTTP-01 challenge.