Domain issues

A custom domain moves through Needs ownership, Verifying, Needs routing and Securing to Active, checked automatically while anything is pending. Custom domains describes the happy path; this page is for a status that stays where it is, or goes backwards. Check DNS on the domain's row asks for a check now rather than at the next interval.

Stuck at Needs ownership

Kuppit cannot see the ownership TXT record.

• The record's name is _kuppit-verification.<hostname>, the full hostname included. At most DNS providers you enter only the part before your zone, so for app.example.com the name you type is _kuppit-verification.app, not _kuppit-verification.app.example.com.
• The value is the token shown on the row, exactly, with no quotes added by hand.
• DNS takes time to propagate. Kuppit rechecks every minute; give a new record a few minutes.
• A CNAME already pointing at Kuppit does not count. Ownership is proved by the TXT record only, on purpose.

Stuck at Needs routing

Ownership is verified but the hostname does not reach Kuppit.

• A subdomain needs a CNAME to domains.kuppit.app. A CNAME to anything else is an explicit conflict and Kuppit says so.
• A root domain needs your provider's CNAME flattening, ALIAS or ANAME feature pointing at the same target. A plain A record cannot work: Kuppit has no fixed address. If your provider has no such feature, use a subdomain such as www.example.com.
• Some providers proxy or flatten records in ways Kuppit cannot see directly. Kuppit accepts the certificate authority's own view of routing when the record itself is hidden, so a correctly configured domain does move on; it may take a check or two.

Stuck at Securing

Ownership and routing hold; the certificate is being issued. This normally takes minutes. It waits on the same DNS the routing check used, so a record that only just propagated can hold it up briefly. If it stays for more than an hour, choose Check DNS, and check that no CAA record on the domain forbids the certificate authority.

DNS issue

The domain was Active and its DNS no longer points at Kuppit. Traffic to it is failing or going elsewhere. Restore the routing record described above; Kuppit rechecks and returns the domain to Active on its own. Nothing is removed while a domain is in this state.

Failed

Certificate issuance failed. Kuppit keeps retrying every ten minutes, and the authority retries on its own schedule too, so this is rarely permanent. If it persists, the usual cause is a CAA record on the domain that does not allow the authority; otherwise, remove and re-add the domain after the 24-hour hold.

This hostname is unavailable

Kuppit refused to add the hostname. Either it is attached to another service anywhere on Kuppit, or it was removed within the last 24 hours and is being held so that a hostname whose DNS still points at Kuppit cannot be claimed by someone else. In the second case, wait out the hold. In the first, remove it from the service it is on.

Enter a registrable domain or subdomain

Kuppit accepts hostnames under a public suffix: example.com, app.example.com, example.co.uk. It refuses IP addresses, bare suffixes, wildcards (*.example.com), and anything under kuppit.app.