Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

FireFox treating Google Images as unsecure content.

  • 5 replies
  • 5 have this problem
  • 3 views
  • Last reply by Superman514

more options

For the past week, Google Images has not been working properly. One of two things happens when I search for images:

1. Google straight-up tells me that it could find no results.

2. I just get a blank white page.

The only add-on I've installed is AdBlock Plus with the EasyList, EasyPrivacy, and Malware filter lists. I tried searching with add-ons disabled, and it worked for a bit, but now I'm searching for images with AdBlock Plus REMOVED, and I'm getting the above results yet again.

I noticed that the grey shield keeps appearing -- the one notifying the user that FireFox has blocked content that isn't secure. I've never noticed this shield before. I've search all over the internet and I haven't found any solutions. I've updated FireFox, cleared my history, cache, and cookies, but the issue persists.

For the past week, Google Images has not been working properly. One of two things happens when I search for images: 1. Google straight-up tells me that it could find no results. 2. I just get a blank white page. The only add-on I've installed is AdBlock Plus with the EasyList, EasyPrivacy, and Malware filter lists. I tried searching with add-ons disabled, and it worked for a bit, but now I'm searching for images with AdBlock Plus REMOVED, and I'm getting the above results yet again. I noticed that the grey shield keeps appearing -- the one notifying the user that FireFox has blocked content that isn't secure. I've never noticed this shield before. I've search all over the internet and I haven't found any solutions. I've updated FireFox, cleared my history, cache, and cookies, but the issue persists.

All Replies (5)

more options

Works for me with a secure connection to Google.

Clear the cache and the cookies from websites that cause problems.

"Clear the Cache":

  • Firefox/Tools > Options > Advanced > Network > Cached Web Content: "Clear Now"

"Remove Cookies" from sites causing problems:

  • Firefox/Tools > Options > Privacy > Cookies: "Show Cookies"

Start Firefox in Safe Mode to check if one of the extensions (Firefox/Firefox/Tools > Add-ons > Extensions) or if hardware acceleration is causing the problem (switch to the DEFAULT theme: Firefox/Firefox/Tools > Add-ons > Appearance).

  • Do NOT click the Reset button on the Safe Mode start window.
more options

Thanks for the quick reply, mate.

I deleted my history and cookies, and cleared my cache. My theme has always been the FireFox default and I'm checking right now -- it still is.

I'm currently in 'safe mode' and Google Images is working fine. I've turned off hardware acceleration. All of my extensions incl. Adobe and Java are up-to-date, so I'm guessing it's an issue with AdBlock Plus?

more options

I forgot to mention, but the FireFox add-ons tab is also acting strange. I've attached a screenshot detailing the issue.

And I don't think the problem is AdBlock Plus. I removed AdBlock from FireFox and Google Image search is still giving me a blank page.

Another thing I noticed is that in safe mode, the grey shield symbol does not appear and FireFox has a secure connection with Google Image search.

more options

Make sure that you haven't enabled a High Contrast theme in the Windows/Mac Accessibility settings.

Make sure that you allow pages to choose their own colors.

  • Tools > Options > Content : Fonts & Colors > Colors : [X] "Allow pages to choose their own colors, instead of my selections above"

Note that these settings affect background images.

See also:

more options

All of that is fine. Google Images still isn't working and the FireFox add-ons page still looks strange.

I did a little more searching and I just found this topic: https://support.mozilla.org/en-US/questions/971125

There was another one with a similar issue and the same answer, but I'm at my work computer at the moment. I think I'll try the 'about:config' solution when I get home, assuming it's safe and nothing really bad will happen.