Skip to main content

Hostname Pre-Validation Failing or Returning 500 Error on Umbraco Cloud

Occurs when hostnames fail to sync with Umbraco's Cloudflare backend, often due to bulk-adding or incorrect DNS proxy settings, causing validation to stall or throw a 500 error.

Written by Joana Knobbe

Product or Service: Umbraco Cloud

Version: All versions

Issue:

When trying to add or pre-validate new hostnames in the Umbraco Cloud portal, the process stalls on "hostname validation pending" or fails with an HTTP Status 500 error in the network tab. The backend fails to generate the required TXT validation records, preventing the domain ownership verification from completing.

Solution:

To resolve the sync failure and trigger a clean generation of the TXT validation records, follow these steps:

  1. Remove the stuck hostnames: Go to your Umbraco Cloud project portal, navigate to Configuration > Hostnames, and delete the hostnames that are stuck or failing.

  2. Check external proxy settings: If the domain is managed within an external Cloudflare account, make sure the CNAME or A-records for the hostname are temporarily set to DNS Only (grey cloud).

  3. Re-add hostnames sequentially: Add the hostnames back into the Umbraco Cloud portal one at a time. Avoid bulk-adding them all at once, ensuring the pre-validation successfully initializes for each one individually.

  4. Complete DNS verification: Apply the newly generated TXT record values to your DNS provider configuration to verify domain ownership.

  5. Re-enable proxy (if applicable): Once the hostname shows a status of protected within the Umbraco Cloud portal, you can change the proxy status in your external Cloudflare account back to Proxied (orange cloud).

Article last update date: 13-07-2026

Did this answer your question?