I have looked online and found several pieces of code that I have put in my .htaccess file but none work, I still get error messages.
It would have been helpful if we had been sent a redirect FAQ with instructions when we were notified about the SSL changes. It recommended setting up a redirect but didn’t tell you how to do it. Having tried using what I can find online unsuccessfully I am coming to this forum in hope that someone can help.
I see, so my users will always see:
“This server couldn’t prove that it’s www.thecornstore.is-great.net ; its security certificate is from is-great.net . This may be caused by a misconfiguration or an attacker intercepting your connection”.
I have to say that I would rather the SSL changes hadn’t been made then, this does not seem like an improvement. Nobody is going to go past the warning, I certainly wouldn’t.
I wish all this had been FULLY explained when we were notified of the change and that we had been given a 1 year notice so that changes could be introduced into printed materials. I have spent/wasted a lot of money on advertising with the www. address.
Thank you, I will change all electronic instances of the website address to remove www. It is the printed versions in advertising material that I cant change.
I find it odd that when the SSL change was announced via email it came with a strong recommendation to set up a redirect, however it seems that a redirect isn’t possible without warning pages that nobody will go past.
The redirect is important to make sure your visitors are protected. Unfortunately the warning isn’t something that’s provided by infinity free or IFastNet. Its something that your browser does itself.
Just a side note, if you have a custom domain you can setup SSL on the www subdomain, it’s only restricted on free subdomains due to how SSL certificates work.