Using Pulse CMS, I've got a warning when trying to login, help please

Haha:
https://arstechnica.com/security/2017/03/firefox-gets-complaint-for-labeling-unencrypted-login-page-insecure/

3 Likes

Hi @yuzool, just a nudge to say I’d love some guidance on SSL when you are ready thank you.

1 Like

Who is your hosting company? If I remember you are with Chilidog?

At any rate, the first step is to get a certificate, That varies from host to host. Many host companies offer a free certificate from services like LetsEncrypt https://letsencrypt.org/. Some host requires you to purchase your certificate. Chilidog offers this through its cPannel Although it’s not covered in the knowledge base so. You will need to contact Greg if you have questions. @barchard

Once you have the Certificate set up on your site you should be able to access your site through https:// just like http://.

Find and fix all mixed content - Mixed content is when you have assets/resources on pages that try to load over HTTP instead of HTTPS. This affects images, scripts, CSS and more.
There are two types of mixed content active or passive.

Active are things like Javascript CSS web fonts, basically anything that can change the appearance of the site. Active must be fixed as most all modern browsers will block this content from loading.
Passive content such as images should be fixed; the browser will not usually block passive content but will issue a warning message.
Some of this content that needs to be fixed maybe out of your control, it will be part of your theme, plugin or stacks, so you will need to contact the developer.
Now while you’re waiting to get this fixed your users will still be able to access your site with the non-secure http://, and nothing will be different.

Once you have all the mixed content cleared up then you can do a redirect from http:// to https://.

To find the mixed content you can use the console on your browser or a site like:
https://www.whynopadlock.com/index.html

Some additional resources:

https://support.google.com/webmasters/answer/6073543?hl=en

https://movingtohttps.com

3 Likes

Hi there, I have lots of different hosts but will check it out thank you :-).
In the meantime yes I now see that some browsers are showing the warning and some aren’t, which is somewhat reassuring :slight_smile:

Interestingly I’ve just asked my hoster about getting a SSL certificate on my own site and he says he wants to charge Ā£50 annually for the privilege. Does this sound right? I don’t think anyone mentioned charges for this in this thread?

Yes it’s is normal to pay for it but the first level of SSL is usually about Ā£20 per year. There are different levels of SSL and as an example here is what Clook offer https://www.clook.net/ssl-certificates/

1 Like

Another option for SSL certificates is Cloudflare - with their free CDN plan you also get a free flexible SSL certificate as well, and it is compatible with pretty much any hosting. All you do is point your nameservers at Cloudflare.

1 Like