SSL provisioning stuck – custom hostname reset needed

Hi, when I visit the website https://www.sonachhaltig.de, I get the following error message:

Since then, the site has been unavailable.

SSL provisioning for www.sonachhaltig.de has been stuck for over a day.

DNS is correct (A records, CNAME, and both _cf-custom-hostname TXT records are present and verified).

The root domain was previously connected and had a valid SSL certificate, then the domain was disconnected and reconnected with www as the primary domain.

Since then, SSL verification does not complete and browsers show SSL handshake / cipher errors.

We using as Provider United Domains https://www.united-domains.de/.

Mayber its not possilbe to setup the root domain (https://sonachhaltig.de) and change later to www.sonachhaltig.de

for the root i got two A Entries + cname + two Txts.

For https://sonachhaltig.de it worked well. Than i disconnted the root and the redirctions Domain - and setup www.sonachhaltig.de for the Hosting Domain and redirected https://sonachhalitg.de o www.

Since then, the site has been unavailable.

Could you help me?

Hi @FCaspar

Thanks for sharing all those details — SSL issues after switching primary domains can be especially stressful when everything looks correct on the DNS side.

I’d like to bring a few Community members into this conversation who are very familiar with domain connections, SSL provisioning, and edge cases around switching from root to www.
@TomM2 @Mike_Eastwood @Phil_Vallender — hope you’re all having a great week! Have you seen cases where SSL provisioning gets stuck after disconnecting a root domain and reconnecting with www as primary (especially with providers like United Domains)? Any guidance on whether this sequence is supported, or how to safely recover SSL provisioning in this state, would be hugely appreciated.

Looking forward to your insights.
Best,
Victor

Hey @FCaspar I’m not sure I follow everything I’m sorry.

Checking your domain: https://www.sonachhaltig.de/ I can see this leads to a website the root domain sonachhaltig.de also leads to the subdomain www.sonachhaltig.de. Is this what you’re intending to do?

SSL and domain provisioning can be fickle and have random, relatively unexplained issues. Normally it can be done in 5-10 mins but on occasion it might take a day or even two to provision correctly.

Are you still experiencing these issues? If so, it doesn’t happen for me so it may likely be a caching issue on your machine or network.

If you try a new device on a new network (e.g. try a phone on a mobile network) do you still see this issue? Could you send a screenshot of the exact error you’re seeing?