The problem is starting to pop up in all op systems browsers. It's part of the security code being written into browsers. It's called mixed content blocking. How I fixed it on my Windows system was to go into the browser settings (about:config) and disable mixed content blocking. Here's what happens, if you access a website that contains links and/or linked images where the link is missing the "s" in HTTPS but the website itself is secured the browser, depending on which, can kick you out if you are signed in, block the site entirely, or pop an error. Now most know about the "s" but where it can also happen is if the prelude is missing altogether as in "w-w-w.name.com" or even "name.com" rather than including "https://" at the front end. If you have an issue, click on the little padlock in the address bar of the browser. The drop-down box will tell you if it's a security issue.