This just came in from reader Annie:

” I can’t get to your website using Chrome browser only Internet Explorer. Chrome says you have an unsafe website. Just FYI. I thought your website was out of business til I tried I.E. “

SantaBarbara seems to works fine with Chrome for me. How about other readers? FYI an entirely new, built-from-scratch is under development which is why I lag so much getting the news out these days.

Bookmark the permalink.


  1. Louie says:

    The culprit is always an SSL configuration error: bad certificate, mixed content issues, etc. I’m a local web developer who specializes in WordPress and can help you out.

    • The Restaurant Guy says:

      That would be great. I think the certificate is ok, as I bought it and installed it on the server myself, but I do know there are mixed content issues (some non-SSL content on an SSL page) but I didn’t know why.

  2. Jonathan Savell says:

    Chrome works for me. Clear cookies and cached files. If that doesn’t work, reset Chrome to original and if still doesn’t work remove and reinstall Chrome.

    • Louie says:

      It’s not a Chrome issue. I’m getting thenissue too sporadically. This is standard when a site either has an incorrectly installed SSL certificate or there’s mixed-content issues. With all of the minified scripts, linked files, etc it becomes a chore tracking everything down that references http:// and not https://.

      It’s a very common issue and something I deal with regularly.

      • The Restaurant Guy says:

        Louie emailed me and suggested I look at my settings and also try an SSL fixer plugin. I never knew there was a plugin to fix that issue, so I gave it a shot.

        1) I went into my blog settings and sure enough the base URL of my blog has http: in it so I changed it to https:. Unfortunately the images already added to the blog still had http: hard-coded in them.

        2) Just now, based on Louie’s suggestion, the installed the plugin “SSL Insecure Content Fixer” and selected the “content” level of fixing (instead of “simple”) because I know all the images and http: hard-coded into them instead.

        That seems to have solved the problem, because I now get a green lock in my browser with Firefox and Chrome now says it is secure.

  3. Tony says:

    Chrome works just fine for me too – those “unsafe” popups seem to be more common these days but I just ignore them (particularly if the site I’m using doesn’t own any confidential information)

  4. If it’s a mixed content error, it would also show up in Firefox. In Firefox you can click the error and find out what content isn’t secured properly. Changing the http:// to https:// in photos and links will usually solve the problem. Some people also have outdated browsers which can’t validate the certificate chain properly and will misreport the site as unsafe, a common issue with people still using Windows XP. There are also reputation services used by antivirus products that will trigger reporting sites as unsafe if someone maliciously reported you as a bad site. One of my clients recently had their site flagged by McAfee as malicious just because it expressed political opinions that someone disagreed with.

  5. Paul says:

    Chrome is not accessing your site. Here is what is displayed:
    This site can’t provide a secure connection uses an unsupported protocol.

    • The Restaurant Guy says:

      I just now upgraded to TLS 1.2 security protocol, and removed SSL2 and SSL3. I ran an secure protocol test before and after and my server’s score increased from F to B, so hopefully this solved the problem. To get a score of A I need to upgrade my server to an entirely new operating system and I’m not ready to make that leap.

Leave a Reply

Your email address will not be published. Required fields are marked *