Troubleshooting · Domains
Custom domain not working? Check DNS first.
When a custom domain doesn't load on Runex, the cause is almost always DNS: a wrong CNAME value, a record that hasn't propagated, or a domain not attached to the app. Work through the checklist in order.
- Check the CNAME
- Wait for propagation
- Attach in the dashboard
$ dig app.example.com CNAME +short cname.runex.cloud. # ✓ correct $ dig app.example.com CNAME +short (empty) # ✗ record missing
Checklist
How do you fix a custom domain that won't load?
Five checks, in order. Stop at the first one that fails. For background on each record type, read how custom domains work.
- The app works on its *.runex.cloud URL. If not, fix the deploy first.
- The CNAME value is exactly cname.runex.cloud, no typos, no https://.
- The record has propagated: dig app.example.com CNAME returns cname.runex.cloud.
- The hostname is attached to the right app in the dashboard.
- No conflicting A or AAAA record exists for the same hostname.
Symptoms
What does each domain error mean?
The symptom points to the step. Certificate errors usually clear once DNS is correct, because automatic SSL can only issue a certificate for a domain that points at Runex.
| Likely cause | Fix | |
|---|---|---|
| Domain doesn't resolve | CNAME missing or not propagated | Add the record; wait for the TTL |
| Shows a different site | Domain attached to another app | Attach it to the correct app |
| HTTPS pending | DNS not resolving to Runex yet | Fix DNS; the certificate follows |
| Apex domain fails | CNAME not allowed at the root | Use ALIAS, ANAME, or CNAME flattening |
FAQ
Domain troubleshooting questions
DNS answers, fast.
How long does DNS propagation take?
Often a few minutes, but up to your record's TTL, and occasionally longer if resolvers cached an old answer. Lowering the TTL before a change helps.
Why does my HTTPS certificate stay pending?
Runex can only issue it after the domain resolves to cname.runex.cloud. Once DNS is correct, the certificate is issued automatically.
Why does my domain show someone else's site?
An old A record or a different CNAME is still in place. Remove conflicting records so only the CNAME to cname.runex.cloud remains.
Next step
DNS fixed? You're live.
Runex issues HTTPS the moment your domain resolves.