Recognize Recaptcha2 not working anymore

[zenewbie]

Why isn't the "Recognize Recaptcha2" cube (in tab) not working any more? I didn't change anything, and it worked flawlessly before.
I am on ZP 7.8.15.0 and tried with capmonster cloud and 2captcha on google login, but I get the error: "sitekey not found". Like I said, it worked before, and I have capmonster-credits of course.

 

[VladZen]

I believe this is the issue on a particular website.
Please specify the site where recaptcha is not working anymore. Probably it has been updated there.

 

[zenewbie]

It's during google login.

 

[zenewbie]

So is it gonna be fixed? How should I solve recaptcha2 now?

 

[VladZen]

So is it gonna be fixed? How should I solve recaptcha2 now?

As far as I know google has updated recaptcha to enterprise version on account login.
Recaptcha cube does not support it.
I would advise you to solve this captcha via CapMonster extension.

 

[seaparadise]

I had a similar issue recently. If you are getting “sitekey not found”, it looks more like the page/integration changed rather than a problem with your CapMonster or 2Captcha balance. Google regularly changes the login flow and the way reCAPTCHA is loaded, so older recognition actions may simply fail to detect the parameters they expect.

I would first try the latest ZennoPoster build and check whether the same project works there. Also worth checking the execution log/browser console to see whether reCAPTCHA is actually present on the page at the moment the Recognize Recaptcha2 action runs.

If it works on ordinary reCAPTCHA test pages but fails specifically on Google login, I’d consider it a compatibility issue with the current Google authorization page rather than the captcha service itself.

 

[seaparadise]

I had a similar issue recently. If you are getting “sitekey not found”, it looks more like the page/integration changed rather than a problem with your CapMonster or 2Captcha balance. Google regularly changes the login flow and the way reCAPTCHA is loaded, so older recognition actions may simply fail to detect the parameters they expect.

I would first try the latest ZennoPoster build and check whether the same project works there. Also worth checking the execution log/browser console to see whether reCAPTCHA is actually present on the page at the moment the Recognize Recaptcha2 action runs.

If it works on ordinary reCAPTCHA test pages and on unrelated sites with more standard implementations, such as Golden Pokies, but fails specifically on Google login, I’d consider it a compatibility issue with the current Google authorization page rather than the captcha service itself.

Another thing worth checking is whether the Google login page is being redirected or re-rendered after the initial load. In that case the recognition action may be running against an old DOM state or before the relevant iframe/widget has finished loading.


I’d also test with a completely fresh browser profile/session, clear cookies for Google, and compare the result with extensions or custom browser settings disabled. Checking the page source/DOM at the exact moment of failure can help confirm whether the expected element still exists and whether its selector or iframe structure has changed.


If possible, add a short wait before the recognition step and log the current URL, page title and any JavaScript errors. That should help separate a timing/session problem from an actual ZennoPoster compatibility issue.


And if this is specifically for Google authentication rather than a normal website form, using Google’s supported OAuth/login flow may ultimately be more reliable than automating the authorization page itself.