Jump to content

Recommended Posts

Posted

Well, considering we recommend that people avoid both of those products, probably. CF is the more likely cause of that particular error though. That error is just saying there's support for old TLS (which CF has) though, it's not really an error so much as that service refusing to use older TLS to make a connection that's not as secure as newer technology.

 

Step 1 is to remove CF and set your name servers to ns1.heliohost.org and ns2.heliohost.org. We are unable to provide support for websites that are behind CF because CF does all sorts of stuff to connections, and also hides the real DNS settings of your account.

Posted

Also, as someone who set up CF today, I found there is an option to remove the TLS 1.0 support on CF. It's under SSL on their site if I remember right, and lets you set the minimum supported version. Just set it to 1.1 instead. Anything made in the past 10-15 years will support TLS 1.1...

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...