custom domain troubleshooting

Most custom domain failures are dns-related and resolve themselves once dns propagates. Here is what to check, in order.

status reads failed

The verification job ran 10 times without seeing dns point at the cname target. Steps:

1. Open the custom domain page in spirby. Note the cname target shown there.
2. From a fresh terminal, run dig <your-host> +short. The result should be the cname target. If it is not, the dns record is wrong or has not propagated.
3. Check ttl on the existing record. If you recently changed it, a high ttl can keep the old value cached for hours.
4. Once dns is correct, click verify now. This resets the attempt counter and re-enqueues verification.

status stays pending for a long time

pending means dns is not yet right. Same fix path as failed, except spirby will keep retrying on its own up to 10 attempts.

ssl errors after verification

Cloudflare for SaaS issues the certificate automatically. If you see an ssl warning right after verifying:

• give it 1–2 minutes for the certificate to fully provision
• hard-reload the page; some browsers cache the old certificate state

If it persists, remove and re-add the domain. That triggers a fresh hostname registration at Cloudflare.

”conflicts with app” error on save

Spirby refuses to accept a host that is the app domain or a subdomain of it. Use a host you control, for example feedback.acme.com, not something.spirby.com.

domain previously belonged to another spirby org

Custom domains are unique across spirby. If the host was used elsewhere, you will see a “taken” error. Contact support and we will sort it out, the previous org needs to remove it before you can claim it.

changing your custom domain

Set a new host in the same screen. The previous Cloudflare hostname is left as an orphan (it stops working because dns no longer points at it). For v1 we accept that. We will surface an admin tool for clean-up in a later release.