SSL issue with an Insecure stylesheet?

I am sure I saw a solution to this recently but for some reason I can’t find it now.

I have updated a customers website with an SSL certificate, and I am getting a few errors.

Google Chrome is saying the site is trying to load scripts from unauthenticated sauces.

Chrome developer tools is saying the site: requested an insecure stylesheet ‘http://fonts.googleapis.com/css?family=Source%20Sans%20Pro:400,700’. This request has been blocked; the content must be served over HTTPS.

I think all I need to do is find the http://fonts.googleapis.com/css?family=Source%20Sans%20Pro:400,700 in the site code and change http to https. But can I find it!?? Of course not…

Could someone point me in the right direction? Would be very very much appreciated.

Thanks

M

A URL to your site would help.

Good point!..
https://www.chapmanworth.co.uk/
Thanks
M

How are you using Google fonts? Is it in the theme blueballfreestackresponsive?
I see an import statement right at the top of the consolidated CSS file. Hard to tell where it’s coming from since you have the consolidated CSS turned on. The font name you are looking for Source Sans Pro( the %20 are spaces), also using Ubuntu font.

1 Like

Thanks for the advice @teefers I think I have sorted it. Found the fonts in the CSS folder of the theme style. Changed the guilty party to https and republished. Looks like it sorted now.

2 Likes

Glad you got it sorted out. You should let the theme developer know so they can fix the theme for other users.

I ran your home page through Why no Padlock, and it passed. You might want to check the rest of your site.

2 Likes

Mysterious! I have found that unsecure web-font calls don’t stop the https padlock. I found a load of these and thought they were the cause of a missing padlock. However, the only fix I need to do was an unrelated Trip Advisor widget. The font calls had no effect even though they are all showing as an issue on whynopadlock.com

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.