In all honesty any half decent host provider should do this for you. Did you ask them?

Not a techie and hopefully someone drops by to guide you but read an article last year that companies are switching over to some form of FREE SSL initiative.

Do a search on "lets encrypt" and "free ssl certificates" -- Should point you in the right direction on how to get the certificate installed properly.

you need https.
if its wordpress you need 'really simple ssl' plug in. it will sort out all the weird redirects and everything will work properly

You don't need https unless you have people login or give personal data.

If not done right, https will cause all sorts of problems.

The biggest problem is that people mix the too, which is fine one way, but not the other.

Besides, you will always need (in most average joe cases) a plain http as a backup anyway.

You need a modern host with modern servers.

Going back "if done right," you should not have to worry about going from http to https, and back again....if done right.

You did not have great work done if it blows up. Everybody must be up to date and an expert on what you have. You would not hire a yugo mechanic to work on your mercedes. Even if they do great work...

Paul

Hi mytrafficjourney,

Something doesn't seem right.

If you had a script that wasn't performing correctly with a secure website protocol, it seems it would have made a lot more sense to fix that script implementation than to switch protocols.

By switching protocols you are literally breaking all of your backlinks and flushing all the previous work you did to promote your web pages down the toilet.

While you can retain most of that SEO benefit if you update all your internal links and implement permanent 301 Redirects, would it not be much simpler to just fix the improper script implementation?

It seems that you are investing heavily in fixing many issues that wouldn't exist if you simply fixed the one issue that caused the original problem. How hard could it be? From the sound of it, it was just a simple implementation error that could likely have been fixed by altering a single line of code. Please check on that script implementation error before doing all of these radical, expensive, and potentially unnecessary workarounds.

Perhaps there is more to the story that you are not sharing?

HTH,

Don Burk

thanks for all the replys. It was not anything to do with my provider it is the script provider who sold me the website script not sure if anyone heard of them. MN-Shop they do social exchange site scripts that is what I have installed on my website.

I wanted to use SSL to make it look more professional but when I used SSL on my website script it always showed load unsafe script in the browser.

You don't need to go back. If you have people buy things or login, you need https.

You should look for solutions.

The script was most likely sold as all regular http files and installed them as such.

It would take a long time and an army of people to find and change all references to an http file to an https.

Look for a script that has this feature already, or find out if there is an upgrade.

You cannot just change all pages to https. The fact that the script has a zillion lines of code and calling on an http file, would make changing each line ridiculously tedious and impossible.

The solution could actually be as simple as a bad ssl certificate.

Another "easy" solution, would just have the login pages/purchase pages changed to https, and all references to http on them. It would mean checking a couple of dozen files and pages.

The best solution of to get a script that is secure already, or contact the seller of the script and see if they upgrade for a few bucks more.

Paul