After going from HTTPS to HTTP everyone is getting a Privacy error

[TacoCat]

Hey guys,

The domain previously was used as a shopify store address. So it had a HTTPs connection, as Shopify gives you the SSL certificate to use.

I had to close the store and wanted to put a simple HTML page that says that we're closed. But now every time I try to access the website in chrome it will show that the connection is not secure and won't display the basic HTML site.

How do I work around this?

 

[Robin]

You can most likely install a free SSL certificate through your web hosting provider - that should solve the SSL "insecure" issue.
Else setup a redirect from HTTPS to HTTP.

 

[Saulkaroo]

I suggest you to take the help of your web hosting service provider. He will be aware of such type of issues and can also make some changes to correct your problem. or there may be a redirection error so, you can also check for it. if you don’t find any solution then the service provider is the best option.

 

[CCarter]

How do I work around this?

Chrome reports ALL http (non-ssl) traffic as non secure now (Started October 2017). Firefox has done it for a bit longer. The only solution is to get SSL enabled on the domain so Chrome will not report it as non-secure.

 

[Calamari]

every time I try to access the website in chrome it will show that the connection is not secure and won't display the basic HTML site.

It should still display the page, you just won't get the green lock before the url in the address bar. If it's important to you I would spend a few dollars and hire a developer to iron it out. Something on your server isn't configured correctly.

 

[Apex]

Have you checked accessing from another browser or device? Something similar happened to me once, and I think it was the fault of using HSTS with HTTPS.

 

[nanexo]

Check the source code for any non secure non https elements and ensure all traffic is routed trough the https version