Troubleshooting

A custom domain does not work

It almost always is the DNS record: a CNAME to the right target, and a little patience.

  1. Not verified? At your DNS provider, the subdomain needs a CNAME record to the target shown on Settings › Domains, not an A record.
  2. Just changed it? DNS changes can take a while to spread. Press Check DNS again later.
  3. A whole domain (yourbrand.com) instead of a subdomain? Use a subdomain such as dashboard.yourbrand.com.
  4. Browser warns about the certificate? The secure certificate is made after the domain is verified; open it again a minute later.
  5. Opens another site? Another CNAME or a proxy in front (such as a CDN) may catch it; point the subdomain straight at the target.

Checked against the app on October 18, 2026