Universal SSL stuck — cannot enable

Application Security SSL / TLS
1

What is the name of the domain?

What is the error message?

an unknown error as occured

What is the issue you’re encountering

No universal certificate enabling

What steps have you taken to resolve the issue?

stop and restart proxyfication, reload the page, try with another browser

Was the site working with SSL prior to adding it to Cloudflare?

Yes

What is the current SSL/TLS setting?

Off

What are the steps to reproduce the issue?

Click on the enable universal SSL :

Screenshot of the error

Capture d’écran 2026-07-27 à 18.50.01.jpg
Capture d’écran 2026-07-27 à 18.50.01.jpg1104×820 60.7 KB

2

I deleted the zone entirely and re-added it from scratch. Cloudflare assigned the exact same nameservers (chloe.ns.cloudflare.com / kellen.ns.cloudflare.com), so nothing needed to change at the registrar. Despite this, the new zone shows the exact same status:

“allergique.org is pending until you complete the instructions on the Overview page and we are able to verify ownership.”

I’ve confirmed via multiple independent checks that the nameservers ARE correctly delegated:

  • dig NS allergique.org via public resolvers → returns chloe/kellen.ns.cloudflare.com
  • Direct query to the .org registry nameservers → same result
  • ICANN WHOIS lookup → confirms chloe/kellen as the domain’s nameservers

This has now been the case for 4+ days (original NS change: July 26). No CAA records, no DNSSEC. “Check nameservers now” has been clicked repeatedly with no change.

The fact that a brand-new zone reproduces the exact same “pending ownership verification” issue strongly suggests this isn’t a zone-level problem but something at the account or domain level on Cloudflare’s side. Any help from a Cloudflare staff member would be greatly appreciated — this is blocking HTTPS/proxy for a live medical information website.

3

You need to change your nameservers before Cloudflare can enable Universal SSL.

Currently, you have created NS records instead of changing your nameservers, which is not the correct thing to do:

allergique.org.         3600    IN      NS      ns42.infomaniak.com.
allergique.org.         3600    IN      NS      ns41.infomaniak.com.
;; Received 95 bytes from 199.19.54.1#53(b0.org.afilias-nst.org) in 28 ms

whois allergique.org
   Domain Name: allergique.org
   ...
   Name Server: ns41.infomaniak.com
   Name Server: ns42.infomaniak.com
4

Thank you