搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

Firefox 125.0.3 block submit with Google Recaptcha

more options

After updating Firefox to Firefox 125.0.3, Google ReCaptcha2 stopped working on my sites (I use the invisible version). Then I checked the version from the official website and it doesn’t work either.

I read about self = this on stackoverflow, but this also does not help on my sites. After clicking, nothing happens, and there is an error in the console.

Has anyone encountered this?

The same behavior here https://www.google.com/recaptcha/api2/demo, an error is displayed and loading... loading... loading.

Error in console is like: UncaughtObject { stack: "z<@https://www.gstatic.com/recaptcha/releases/WQcDpAcHn0sjM6ZiVkU8JwNH/recaptcha__ru.js:470:201\nH<@https://www.gstatic.com/recaptcha/releases/WQcDpAcHn0sjM6ZiVkU8JwNH/recaptcha__ru.js:258:...

from https://www.gstatic.com/recaptcha/releases/WQcDpAcHn0sjM6ZiVkU8JwNH/recaptcha__ru.js line 448:1

Tested on absolutely clean Firefox without plugins, with security turned off, without cookies and account.

When i start browsing from Holland IP via VPN the problem are solving. In Chrome, Edge ReCaptcha2 working fine.

After updating Firefox to Firefox 125.0.3, Google ReCaptcha2 stopped working on my sites (I use the invisible version). Then I checked the version from the official website and it doesn’t work either. I read about self = this on stackoverflow, but this also does not help on my sites. After clicking, nothing happens, and there is an error in the console. Has anyone encountered this? The same behavior here https://www.google.com/recaptcha/api2/demo, an error is displayed and loading... loading... loading. Error in console is like: UncaughtObject { stack: "z<@https://www.gstatic.com/recaptcha/releases/WQcDpAcHn0sjM6ZiVkU8JwNH/recaptcha__ru.js:470:201\nH<@https://www.gstatic.com/recaptcha/releases/WQcDpAcHn0sjM6ZiVkU8JwNH/recaptcha__ru.js:258:... from https://www.gstatic.com/recaptcha/releases/WQcDpAcHn0sjM6ZiVkU8JwNH/recaptcha__ru.js line 448:1 Tested on absolutely clean Firefox without plugins, with security turned off, without cookies and account. When i start browsing from Holland IP via VPN the problem are solving. In Chrome, Edge ReCaptcha2 working fine.
已附加屏幕截图

被采纳的解决方案

Hi

This is an issue that Google are looking into and we hope to have an update for you very soon.

定位到答案原位置 👍 0

所有回复 (8)

more options

When you used VPN, did a different script file load, or was it the same script file?

more options

Same issue! randomly started happening yesterday, spent hours and literally tried everything. It works fine on microsoft Edge! Please tell me there's a solution for this.

more options

Temporary fix but good work around for now- As another user instructed, download the following extension. User-Agent Switcher by Erin Schlarb Set the default to windows/chrome 123 Recaptcha all work normally now. Looks like firefox is getting blocked somehow.

more options

Workaround Until this is Fixed. By the way, this is a Google issue not really a Firefox issue.

1. In the address bar, type: about:config 2. Search for: general.useragent.override 3. Select "String" and then the + button 4. Copy and Paste this into the field: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:125.0) AppleWebKit Gecko/20100101 Firefox/125.0 5. Click the Checkmark Blue button. You're done. 6. Now Bookmark this setting so you can delete it when this issue is fixed. Don't forget

more options

Obviously, when you developer it is not a solution for end-users to change user-agent...

jscher2000 - Support Volunteer said

When you used VPN, did a different script file load, or was it the same script file?
For now it's the same. And when I used VPN the behavior is repeated.

由Федор于修改

more options

选择的解决方案

Hi

This is an issue that Google are looking into and we hope to have an update for you very soon.

more options

The error has been fixed. It’s as if Google fixed it, since I didn’t do anything and the FireFox version didn’t change.

more options

Федор said

The error has been fixed. It’s as if Google fixed it, since I didn’t do anything and the FireFox version didn’t change.

Yes, it appears they rolled back to last week's script, or at least the same URL as last week's script.