I have not noticed any new CAPTCHA problems in recent updates.

As a starting point, could you double-check your content blockers on pages where you see this problem:

Firefox's Tracking Protection feature, and extensions that counter ads and tracking, may break websites that embed third party content (meaning, from a secondary server).

(A) The shield icon toward the left end of the address bar usually turns a bit purplish when content is blocked. Click the icon to learn more or make an exception. See: Enhanced Tracking Protection in Firefox for desktop.

(B) Extensions such as Adblock Plus, Blur, Disconnect, DuckDuckGo Privacy Essentials, Ghostery, NoScript, Privacy Badger, uBlock Origin or uMatrix usually provide a toolbar button to manage blocked content in a page. There may or may not be a number on the icon indicating the number of blocked items; you sometimes need to click the button to see what's going on and test whether you need to make an exception for this site.

Note: Google provides the most popular CAPTCHA service. If you have any add-ons or settings directed toward isolating Google away from other sites, those may need to be adjusted to allow a bit more Google.

Hi,

Thanks for getting back to me. I turned off the Enhanced Tracking Protection from the shield icon in the address bar for the site, and still no go. For instance this site used to load the captcha fine, https://www.loopmasters.com/users/sign_in And the only ext I had was DuckDuckGo Privacy Essentials which I removed.

The 'I'm not a robot' box is actually not showing up now. I get eventually loaded: Could not connect to the reCAPTCHA service. Please check your internet connection and reload to get a reCAPTCHA challenge.

An example of another user having this issue recently, but the fix seems pretty complex: https://support.mozilla.org/en-US/questions/1321706

Thanks,

Note that this is an iframe loaded via JavaScript.

If you use extensions ("3-bar" menu button or Tools -> Add-ons -> Extensions) that can block content (Adblock Plus, NoScript, DuckDuckGo PE, Disconnect, Ghostery, Privacy Badger, uBlock Origin) always make sure such extensions do not block content.

• make sure your extensions and filters are updated to the latest version
• https://support.mozilla.org/en-US/kb/troubleshoot-extensions-themes-to-fix-problems

Firefox shows a purple shield instead of a gray shield at the left end of the location/address bar in case Enhanced Tracking Protection is blocking content. You can click shield icon for more detail and possibly disable the protection. You can check the Web Console for relevant-looking messages about blocked content.

• https://support.mozilla.org/en-US/kb/enhanced-tracking-protection-firefox-desktop
• https://support.mozilla.org/en-US/kb/smartblock-enhanced-tracking-protection
• https://support.mozilla.org/en-US/kb/trackers-and-scripts-firefox-blocks-enhanced-track

You can try these steps in case of issues with webpages:

You can reload webpage(s) and bypass the cache to refresh possibly outdated or corrupted files.

• hold down the Shift key and left-click the Reload button
• press "Ctrl + F5" or press "Ctrl + Shift + R" (Windows,Linux)
• press "Command + Shift + R" (Mac)

Clear the Cache and remove the Cookies for websites that cause problems via the "3-bar" Firefox menu button (Settings).

"Remove the Cookies" for websites that cause problems:

• Settings -> Privacy & Security
  Cookies and Site Data: "Manage Data"

"Clear the Cache":

• Settings -> Privacy & Security
  Cookies and Site Data -> Clear Data -> [X] Cached Web Content -> Clear

Start Firefox in Troubleshoot Mode to check if one of the extensions ("3-bar" menu button or Tools -> Add-ons -> Extensions) or if hardware acceleration or userChrome.css is causing the problem.

• switch to the DEFAULT theme: "3-bar" menu button or Tools -> Add-ons -> Themes
• do NOT click the "Refresh Firefox" button on the Troubleshoot Mode start window

• https://support.mozilla.org/en-US/kb/diagnose-firefox-issues-using-troubleshoot-mode
• https://support.mozilla.org/en-US/kb/troubleshoot-extensions-themes-to-fix-problems

• https://support.mozilla.org/en-US/kb/enhanced-tracking-protection-firefox-desktop
• https://support.mozilla.org/en-US/kb/smartblock-enhanced-tracking-protection
• https://support.mozilla.org/en-US/kb/trackers-and-scripts-firefox-blocks-enhanced-track

I get eventually loaded: Could not connect to the reCAPTCHA service. Please check your internet connection and reload to get a reCAPTCHA challenge.

So you do not see the box here, you see the message about not being able to connect?

Same for the test page from the other thread (https://patrickhlauke.github.io/recaptcha/)?

Could you right-click the error message, expand the "This Frame" menu, and click Open Frame in New Tab. The idea is to be able to study this problem a little better.

After opening the framed (embedded) page in a new tab, in that tab, press Ctrl+Shift+K to pop open the Web Console to check for any error messages. After this, you can reload the page in the upper part of the tab (Ctrl+R) to re-request it and check for new messages.* Does Firefox mention anything blocking the page?

* The reloading doesn't work for this frame due to being out of context.

Hi,

Thanks for your tips. I cleared the cache again, (shift > reload) I had already done that however, and cleared the site data through the settings panel. I disabled the OpenH264 Video Codec provided by Cisco Systems, Inc.

I also changed the security settings to custom, and unchecked all four options.

I closed down, tried to log in to loopmasters.com again and it worked!

So I re-added each of the four security options in custom one by one, and shutdown and relogged in each time, curious to see if one of those was causing the issue. But I added all four back and I can still log in. So I guess I'll leave it like that instead of going back to Standard or Strict.

You probably have a better idea of what did it, but thanks for the help. Another couple sites that were not logging in are working again as well.

I can't say I know what the critical thing was, but glad to hear it is working correctly now.