I have been attempting to launch https://www.duenorthtulsa.org for over an hour now. All DNS entries are in place with a 600s TTL in Godaddy. In the browser, it switched to ERR_SSL_PROTOCOL_ERROR within a few minutes. This is totally expected and usually resolves fairly quickly. For this launch though, my domain has been sitting on the error for over an hour now.
I’ve launched a ton of sites in Webflow over the years and never have taken this long. Are there issues on the Webflow or AWS side of things today?
In my experience it’s very unlikely that it should take over an hour, but it’s not impossible. Most platforms mention at least 2 hours, but it’s not uncommon to see them say 24 hours or more.
For reference, Webflow’s own documention mentions 24-72 hours.
It’s normal for SSL propagation to take the longest to sort itself out so I’d recommend checking back in a while to see if it doesn’t sort itself out
Edit: I just checked the site and I see it’s working now. I’m going to mark this solved, but feel free to reach out if you’re still noticing issues.
I’m currently having this issue with my website www.alxndrfng.com . The domain says it’s connected on webflow but I’m nearing the 72 hour mark now with no change to the issue. I’ve spoken to GoDaddy’s support and there’s not much they can do besides checking if I have the right IP addresses in the record. I’m now unsure if it’s an error on my end, webflow’s end or Godaddy’s. Hoping to have this issues resolved ASAP.
According to What’sMyDNS, your CNAME record is currently set to be a value of alxndrfng.com, whereas it should be set to be proxy-ssl.webflow.com: www.alxndrfng.com - CNAME Records
Once this adjusted, it should solve within a few hours (but maybe up to 48! I’m not too sure how quickly GoDaddy’s records propogate)
I’ve replaced alxndrfng.com with http://proxy-ssl.webflow.com on my GoDaddy DNS manager, hoping to see the change reflected soon. In the meantime, what should I be looking for on whatsmydns.net so I know the correct changes have been made?
