I’m new to everything relating to domains, hosting, designs and so on. So I was stupid enough to buy a domain from Godaddy.
However, I followed the guide to change the nameservers over to Cloudflare, so I could setup Webflow with Cloudflare. No problems there. But I can’t publish my site, even through Webflow says it is connected.
Currently:
I’ve enabled Webflow’s SSL
Set Cloudflare’s SSL to Full (I read Webflow provide certificate?)
I haven’t activated any Pagerules in Cloudflare (Always HTTPS etc)
The DNS seems to be working fine, but I guess it’s something with SSL. But I’m simply too unknowledgeable to figure it out. I tried Cloudflare support, but recieved some Bot replies. So I would also try here.
I tried using the site from a friends computer; and it worked. But then suddenly it didn’t. “Connection not secure”.
UPDATE: I tried clearing my cache manually from Brave browser. Now it works, but will every person visiting my site have problems with this? Do they suddenly have to clear cache files, since “Connection isn’t secure”?
Stopped working again. Now it says: “NET::ERR_CERT_COMMON_NAME_INVALID”
Hi @Jookie, I had this error before. Make sure the cloud next to the A records connection to webflow is not Orange and it says DNS Only. Meaning do not bring traffic through Cloudflare.
Not sure if its exactly the same issue, but this is best practice. And yes, webflow already provide SSL.
@Jookie you need to remove this btw. and yes as @screenfluent said, you have to wait a few hours. You can keep tabs from dnschecker.org. Once it shows the IP, try loading your page again
Is this correct? It seems pretty unreliable with connecting. I receive the following error: “NET::ERR_CERT_COMMON_NAME_INVALID” several times before I can connect. On mobile, I just get “A server with the specified hostname could not be found”.
Am I doing something wrong? ‘A Records’ comes back with a host address at dnschecker.org. But CNAME records cause back with a negative. Could it be DNSSEC is still pending at Cloudflare?
The CNAME was resolved yesterday (and pretty quickly; maybe 2 hours after your reply). But when I woke up today, it was back to the same and unsolved.
I’ve changed the TTL to auto and tried clearing all my browser data (Everything from login, cache and settings for a total refresh in my browser). It still gives me: “NET::ERR_CERT_COMMON_NAME_INVALID”. I did the same for my mobile and it says the same: “A server with the specified hostname could not be found”
The site also worked for 10-20 minutes at another PC, but after some time, it just keeps repeating the error. Does the site still work for you?
Also, we agree on Cloudflare’s SSL option should be set to “Full”?
Thats really weird. The website still works for me.
Have you also double checked the IP, make sure that it matches what is provided on your webflow project.
Any cloudflare settings is irrelevant at this point, because by stating that you are using DNS Only any cloudflare service will be unavailable to your domain. Your SSL is now provided by Webflow.
If all else fails, I think you can try re-setup the DNS records.
I just tried a different browser (Edge) and the site works. So it’s probably a local problem from my end - I just don’t know what. Could it be I am using Brave Browser? Will try with Firefox and chrome in two.
By re-setup DNS, you mean deleting the current settings and just paste the same DNS records in again?
Doesn’t work on Firefox or Chrome. It keeps giving me a warning about the certificate and if I proceed, then I cannot connect. (Also, Edge is giving me the same warning now. So the site only worked with that for 10-20 minutes again) Will try to re-setup DNS as you said.
I read somewhere on Brave support, it could be something with the browser rejecting cache files or how Windows reads the certificates?
Sure. First thing I noticed was they used my domain as free marketing, before I understood how to properly set it up. (They even used the words ‘courtesy of godaddy’). Well, I googled them and a whole lot of shady things came up. But the one thing which Especially came up a lot was their horrible customer service (I haven’t tried it; Just read it. Don’t take my or their word for it. A lot of the hate is from their SOPA support back in 2012).
Other thing for me personally. The UI sucked and I got less stuff for the same price compared to other sites (.dk domain). I hear many recommend NameCheap or Google Domains, but don’t take my word for it (again).
Does the site still work for you?
