Skip to content
uploy docs

Domain not resolving

Where to look first

Section titled “Where to look first”

The Domains tab on the app shows the current state and a detail line explaining why verification or issuance stalled.

Common causes

Section titled “Common causes”

DNS not yet propagated

Section titled “DNS not yet propagated”
  • Symptom: Row is stuck in DNS not yet pointing at Uploy after you created the CNAME.
  • Fix: DNS propagation can take minutes to hours. Check with dig <hostname> CNAME or a public tool like dnschecker.org. Once the CNAME returns {project-slug}.run.uploy.eu, click Recheck on the row.

Wrong CNAME target

Section titled “Wrong CNAME target”
  • Symptom: Row stays in DNS not yet pointing at Uploy and the detail shows CNAME points to <something-else>; expected {slug}.run.uploy.eu.
  • Fix: Edit the CNAME at your DNS provider so it points exactly to the target shown in the dashboard. The target is case-insensitive and the trailing dot is tolerated.

Apex domain attempted

Section titled “Apex domain attempted”
  • Symptom: POST /domains returned apex and two-label domains are not supported yet; use a subdomain.
  • Fix: Add a subdomain instead (e.g. www.example.com or app.example.com) and point your apex (example.com) at it via a separate redirect at your DNS provider. Native apex support is a planned follow-up.

Conflicting existing DNS records

Section titled “Conflicting existing DNS records”
  • Symptom: CNAME creation is refused by your DNS provider.
  • Fix: A CNAME cannot coexist with other record types on the same name. Remove any A / AAAA / TXT records at the exact subdomain before adding the CNAME.

TLS rate-limit

Section titled “TLS rate-limit”
  • Symptom: Row moves to Issuing certificate… then to Failed with a message mentioning rate limits.
  • Fix: Let’s Encrypt rate-limits are per apex domain per week. Wait for the window to reset. Avoid repeatedly adding and deleting the same domain while debugging — each failure counts toward the limit.

HTTP-01 challenge blocked

Section titled “HTTP-01 challenge blocked”
  • Symptom: Row fails with a message about reaching the challenge URL.
  • Fix: Uploy serves port 80 for HTTP-01. If your DNS / firewall / proxy forces HTTPS-only or redirects / upstream, the challenge path /.well-known/acme-challenge/* may not reach us. Ensure the CNAME points directly at Uploy without an intermediate proxy.

CAA records blocking Let’s Encrypt

Section titled “CAA records blocking Let’s Encrypt”
  • Symptom: Row fails with a CAA-related error.
  • Fix: Your domain (or its parent) has a CAA record that does not permit letsencrypt.org to issue. Either add letsencrypt.org to the CAA allow-list or remove the record.

Retrying

Section titled “Retrying”

On any Failed or DNS not yet pointing row, click Recheck. If the row is stuck for hours without progress, Delete it and re-add — this recreates the Ingress and Certificate CR from scratch.

If none of the above matches

Section titled “If none of the above matches”

Contact support with the hostname, the Domains tab screenshot, and the status detail line.