"Can not resolve reCAPTCHA parameter" entries in exception.log for Google reCAPTCHA Admin Panel #34975

stevekem · 2022-01-14T23:10:14Z

Preconditions (*)

Magento 2.4.3-p1

Steps to reproduce (*)

Go to Configuration > Security > Google reCAPTCHA Admin Panel
Add your Google API Website Key & Google API Secret Key to any reCAPTCHA below:

reCAPTCHA v2 ("I am not a robot")
reCAPTCHA v2 Invisible
reCAPTCHA v3 Invisible

Select your reCAPTCHA version (with API keys above) for either below:

Enable for Login
Enable for Forgot Password

Save config
Flush cache

Expected result (*)

No entry in var/log/exception.log file

Actual result (*)

Below entry every few seconds/minutes constantly with no traffic:

main.ERROR: Can not resolve reCAPTCHA parameter. {"exception":"[object] (Magento\Framework\Exception\InputException(code: 0): Can not resolve reCAPTCHA parameter. at /home/xxxxxxx/public_html/vendor/magento/module-re-captcha-ui/Model/CaptchaResponseResolver.php:25)"} []

Getting around 12,000 entry lines every 24 hours in exception.log file which is getting huge in a short period of time.
Keys have been triple checked to make sure correct, even created new ones with no change in behavior.
reCAPTCHA for both Admin and Frontend seems to be working.
Only known way to stop entries is disable both "Enable for Login" and "Enable for Forgot Password" for Admin Storefront.
reCAPTCHA for Frontend storefront isn't experiencing this issue for us for all enabled areas.

Please provide Severity assessment for the Issue as Reporter. This information will help during Confirmation and Issue triage processes.

Severity: S0 - Affects critical data or functionality and leaves users without workaround.
Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

m2-assistant · 2022-01-18T06:01:38Z

Hi @engcom-Hotel. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
Details
If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.
2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.
3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.
4. Verify that the issue is reproducible on 2.4-develop branch
Details
- Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
- If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
- If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
5. Add label Issue: Confirmed once verification is complete.
6. Make sure that automatic system confirms that report has been added to the backlog.

0xMatt · 2022-01-19T13:49:56Z

Same issue. Happens all the time.

[2022-01-17 14:31:45] main.ERROR: Can not resolve reCAPTCHA parameter. {"exception":"[object] (Magento\\Framework\\Exception\\InputException(code: 0): Can not resolve reCAPTCHA parameter. at /var/www/html/magento/vendor/magento/module-re-captcha-ui/Model/CaptchaResponseResolver.php:25)"} []

[2022-01-17 16:21:40] main.ERROR: Can not resolve reCAPTCHA parameter. {"exception":"[object] (Magento\\Framework\\Exception\\InputException(code: 0): Can not resolve reCAPTCHA parameter. at /var/www/html/magento/vendor/magento/module-re-captcha-ui/Model/CaptchaResponseResolver.php:25)"} []

Captcha works. The badge is loaded and visible. When I go to log in, I'll get an error message saying something went wrong. I'll have to log in 2-3 times and around the third time it'll let me in. No javascript console errors are present during this issue.

stevekem · 2022-01-20T01:38:49Z

Captcha works. The badge is loaded and visible. When I go to log in, I'll get an error message saying something went wrong. I'll have to log in 2-3 times and around the third time it'll let me in. No javascript console errors are present during this issue.

Yes this happens as well, I forgot to mention that. Thank you!

stevekem · 2022-01-20T19:14:46Z

Just wanted to note that we are getting the "Something went wrong with reCAPTCHA. Please contact the store owner." error on frontend too, not just on Admin. The 12,000+ daily log entries are happening with Admin module though.

ihor-sviziev · 2022-01-26T15:20:50Z

We got the same issue, but after analyzing it - it looks like we're getting a lot of such messages because some bot(s) are trying to create a customer, and captcha validation fails for them. We weren't able to reproduce this issue ourselves.

stevekem · 2022-01-26T16:20:01Z

We got the same issue, but after analyzing it - it looks like we're getting a lot of such messages because some bot(s) are trying to create a customer, and captcha validation fails for them. We weren't able to reproduce this issue ourselves.

Thanks for the info! How could we verify if that is the case for us as well?

ihor-sviziev · 2022-01-26T16:25:56Z

@stevekem, we analyzed logs, the interval between requests from the same IP address was ~0-3 sec (usually people don't do requests so quickly), the requests were to /customer/account/create/, /customer/account/createpost/ and to /customer/account/create/<product_url_path>/.
The last case links are not available on the website, so that's some bot for sure.

stevekem · 2022-01-26T16:32:30Z

@ihor-sviziev Ok gotcha! If it is the bots, just block them in robots? Did that resolve the issue for you?

ihor-sviziev · 2022-01-26T16:45:37Z

@stevekem that looks like bots that are trying to hack or do something similar by creating a new customer

stevekem · 2022-01-26T16:51:49Z

@ihor-sviziev In your case, did you block the bots in robots.txt to resolve the issue?

ihor-sviziev · 2022-01-26T16:57:23Z

@stevekem yes, the requests starting with /customer/ are blocked by default and we're not removed that.

stevekem · 2022-01-26T17:01:17Z

@ihor-sviziev Thank you, appreciate it! Will check our logs and see if that's the case for us as well.

m2-assistant · 2022-03-01T06:40:19Z

Hi @engcom-Delta. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
Details
If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.
2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.
3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.
4. Verify that the issue is reproducible on 2.4-develop branch
Details
- Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
- If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
- If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
5. Add label Issue: Confirmed once verification is complete.
6. Make sure that automatic system confirms that report has been added to the backlog.

engcom-Delta · 2022-03-03T08:58:12Z

Hi @stevekem ,
Thank you for reporting the issue,We are unable to reproduce the issue on Magento 2.4 develop branch.Please review provided steps.
Steps Followed:

1.Login to admin Panel
2.Go to Stores-->Configuration-->Security-->Google Recaptcha Admin Panel-->reCAPTCHA v2("I am not a robot)
3.Added Google API Website Key and Google API Secret Key to reCAPTCHA v2("I am not a robot)
4.Enabled for Login
Enabled for Forgot Password
5.Saved the configuration
6.Flush Cache

Actual Results
1.No entry in var/log/exception.log file

Hence Adding the label "Needs Update"

engcom-Delta · 2022-03-21T09:43:46Z

We have noticed that this issue has not been updated for a period of more than 14 Days.
Hence we assume that this issue is fixed now, so we are closing it. Please raise a fresh ticket or reopen this ticket if you need more assistance on this.

knoorani-ijona · 2022-04-13T13:19:37Z

We are still facing this issue. In my case, a captcha is needed for the newsletter subscription form. Same error.
[2022-04-13 13:13:03] main.ERROR: Can not resolve reCAPTCHA parameter. {"exception":"[object] (Magento\\Framework\\Exception\\InputException(code: 0): Can not resolve reCAPTCHA parameter. at /home/xxxxxx/public_html/vendor/magento/module-re-captcha-ui/Model/CaptchaResponseResolver.php:25)"} []

Hanhan1989 · 2022-04-17T05:55:53Z

@engcom-Delta @knoorani-ijona Same problem in Magento 2.4.4 in admin loggin page. it seems that the error is reproduced only in production mode
main.ERROR: Magento\Framework\Exception\InputException: Can not resolve reCAPTCHA parameter. in vendor/magento/module-re-captcha-ui/Model/CaptchaResponseResolver.php:25

Hanhan1989 · 2022-04-17T22:20:48Z

In my case, there were two javascript errors that caused me to not be able to log in. These errors are due to the minification of the collapse.js and tab.js files in the lib/web/jquery/bootstrap/ path.

So the solution to this problem has been to exclude those files from the minification.

<?xml version="1.0"?>
<config xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="urn:magento:module:Magento_Store:etc/config.xsd">
    <default>
        <dev>
            <js>
                <minify_exclude>
                    <collapse>/jquery/bootstrap/collapse</collapse>
                    <tab>/jquery/bootstrap/tab</tab>
                </minify_exclude>
            </js>
        </dev>
    </default>
</config>

Themageguru · 2022-04-28T07:41:13Z

Hello, We got the same issue in magento version 2.4.3. lot of exception errors in log file. Also, I did try above all solution but didn't work any one. Any update on this issue.

mikeastral · 2022-04-30T01:45:23Z

@engcom-Delta @knoorani-ijona I am having the same problem in Magento 2.4.4.
I'll have to log in 2-3 times before it allows me to log in. This issue is not occurring on frontend side.

Minification of the collapse.js and tab.js files in the lib/web/jquery/bootstrap/ path is not fixing the issue.

Hanhan1989 · 2022-05-04T21:30:38Z

@engcom-Delta @knoorani-ijona I am having the same problem in Magento 2.4.4.

I'll have to log in 2-3 times before it allows me to log in. This issue is not occurring on frontend side.

Minification of the collapse.js and tab.js files in the lib/web/jquery/bootstrap/ path is not fixing the issue.

I have to disable recaptcha for admin login。I hope magento open this issue and review the problem。thanks

benediktblank · 2022-05-23T17:20:06Z

I'm having the same issue. On Friday I upgraded from Magento 2.4.3-p1 to 2.4.4 and today I'm unable to log in to the Backend/Admin. I had to disable Admin Login Recaptcha in the Database to be able to login again.

I have no idea what is going on and have to keep recaptcha disabled in the Admin login for now.

Stack trace is:

[2022-05-23T17:10:05.800157+00:00] main.ERROR: Magento\Framework\Exception\InputException: Can not resolve reCAPTCHA parameter. in /var/www/html/vendor/magento/module-re-captcha-ui/Model/CaptchaResponseResolver.php:25
Stack trace:
#0 /var/www/html/vendor/magento/module-re-captcha-user/Observer/LoginObserver.php(125): Magento\ReCaptchaUi\Model\CaptchaResponseResolver->resolve(Object(Magento\Framework\App\Request\Http))
#1 /var/www/html/vendor/magento/framework/Event/Invoker/InvokerDefault.php(88): Magento\ReCaptchaUser\Observer\LoginObserver->execute(Object(Magento\Framework\Event\Observer))
#2 /var/www/html/vendor/magento/framework/Event/Invoker/InvokerDefault.php(74): Magento\Framework\Event\Invoker\InvokerDefault->_callObserverMethod(Object(Magento\ReCaptchaUser\Observer\LoginObserver), Object(Magento\Framework\Event\Observer))
#3 /var/www/html/vendor/magento/framework/Event/Manager.php(66): Magento\Framework\Event\Invoker\InvokerDefault->dispatch(Array, Object(Magento\Framework\Event\Observer))
#4 /var/www/html/generated/code/Magento/Framework/Event/Manager/Proxy.php(95): Magento\Framework\Event\Manager->dispatch('admin_user_auth...', Array)
#5 /var/www/html/vendor/magento/module-user/Model/User.php(589): Magento\Framework\Event\Manager\Proxy->dispatch('admin_user_auth...', Array)
#6 /var/www/html/generated/code/Magento/User/Model/User/Interceptor.php(140): Magento\User\Model\User->authenticate('dsadsadasdds', 'asdasdsasdasd')
#7 /var/www/html/vendor/magento/module-user/Model/User.php(649): Magento\User\Model\User\Interceptor->authenticate('dsadasd', 'dsadasd')
#8 /var/www/html/generated/code/Magento/User/Model/User/Interceptor.php(158): Magento\User\Model\User->login('dsadasd', 'dsadasd')
#9 /var/www/html/vendor/magento/module-backend/Model/Auth.php(162): Magento\User\Model\User\Interceptor->login('dsadsadasdds', 'asdasdasdd')
#10 /var/www/html/vendor/magento/framework/Interception/Interceptor.php(58): Magento\Backend\Model\Auth->login('dsadasd', 'dsadasd')
#11 /var/www/html/vendor/magento/framework/Interception/Interceptor.php(138): Magento\Backend\Model\Auth\Interceptor->___callParent('login', Array)
#12 /var/www/html/vendor/magento/framework/Interception/Interceptor.php(153): Magento\Backend\Model\Auth\Interceptor->Magento\Framework\Interception\{closure}('sdfsdfdfdfsdf, 'fdsfdsdfsdfsdfsdfsdfsdfdfsfdfsd')
#13 /var/www/html/generated/code/Magento/Backend/Model/Auth/Interceptor.php(59): Magento\Backend\Model\Auth\Interceptor->___callPlugins('login', Array, Array)
#14 /var/www/html/vendor/magento/module-backend/App/Action/Plugin/Authentication.php(207): Magento\Backend\Model\Auth\Interceptor->login('dsadsadasdds', 'asdasdasdasd')
#15 /var/www/html/vendor/magento/module-backend/App/Action/Plugin/Authentication.php(159): Magento\Backend\App\Action\Plugin\Authentication->_performLogin(Object(Magento\Framework\App\Request\Http))
#16 /var/www/html/vendor/magento/module-backend/App/Action/Plugin/Authentication.php(127): Magento\Backend\App\Action\Plugin\Authentication->_processNotLoggedInUser(Object(Magento\Framework\App\Request\Http))
#17 /var/www/html/vendor/magento/framework/Interception/Interceptor.php(135): Magento\Backend\App\Action\Plugin\Authentication->aroundDispatch(Object(Magento\Backend\Controller\Adminhtml\Index\Index\Interceptor), Object(Closure), Object(Magento\Framework\App\Request\Http))
#18 /var/www/html/vendor/magento/framework/Interception/Interceptor.php(153): Magento\Backend\Controller\Adminhtml\Index\Index\Interceptor->Magento\Framework\Interception\{closure}(Object(Magento\Framework\App\Request\Http))
#19 /var/www/html/generated/code/Magento/Backend/Controller/Adminhtml/Index/Index/Interceptor.php(32): Magento\Backend\Controller\Adminhtml\Index\Index\Interceptor->___callPlugins('dispatch', Array, Array)
#20 /var/www/html/vendor/magento/framework/App/FrontController.php(245): Magento\Backend\Controller\Adminhtml\Index\Index\Interceptor->dispatch(Object(Magento\Framework\App\Request\Http))
#21 /var/www/html/vendor/magento/framework/App/FrontController.php(212): Magento\Framework\App\FrontController->getActionResponse(Object(Magento\Backend\Controller\Adminhtml\Index\Index\Interceptor), Object(Magento\Framework\App\Request\Http))
#22 /var/www/html/vendor/magento/framework/App/FrontController.php(147): Magento\Framework\App\FrontController->processRequest(Object(Magento\Framework\App\Request\Http), Object(Magento\Backend\Controller\Adminhtml\Index\Index\Interceptor))
#23 /var/www/html/vendor/magento/framework/Interception/Interceptor.php(58): Magento\Framework\App\FrontController->dispatch(Object(Magento\Framework\App\Request\Http))
#24 /var/www/html/vendor/magento/framework/Interception/Interceptor.php(138): Magento\Framework\App\FrontController\Interceptor->___callParent('dispatch', Array)
#25 /var/www/html/vendor/magento/framework/Interception/Interceptor.php(153): Magento\Framework\App\FrontController\Interceptor->Magento\Framework\Interception\{closure}(Object(Magento\Framework\App\Request\Http))
#26 /var/www/html/generated/code/Magento/Framework/App/FrontController/Interceptor.php(23): Magento\Framework\App\FrontController\Interceptor->___callPlugins('dispatch', Array, Array)
#27 /var/www/html/vendor/magento/framework/App/Http.php(116): Magento\Framework\App\FrontController\Interceptor->dispatch(Object(Magento\Framework\App\Request\Http))
#28 /var/www/html/generated/code/Magento/Framework/App/Http/Interceptor.php(23): Magento\Framework\App\Http->launch()
#29 /var/www/html/vendor/magento/framework/App/Bootstrap.php(264): Magento\Framework\App\Http\Interceptor->launch()
#30 /var/www/html/pub/index.php(30): Magento\Framework\App\Bootstrap->run(Object(Magento\Framework\App\Http\Interceptor))
#31 {main} [] []````

engcom-Hotel · 2024-11-14T08:22:19Z

Hello @mcspronko,

This issue has been created for the recaptcha bug and is no longer reproducible. Please create a new issue and explain the bug with the Cart price rules there.

Thanks

mcspronko · 2024-11-14T08:50:24Z

@engcom-Hotel you asked me to update to the latest stable version where i replied that 2.4.7-p3 is not stable due to a bug with price cart rules. I am fully aware that the current issue is about captcha.

mostafa-elkholy · 2024-11-15T22:56:00Z

I have the same issue with Magento 2.4.6-p3 updated to 2.4.6-p8 & 2.4.7-p3 and have the same issue of the reCAPTCHA

[2024-11-14T22:29:28.584459+00:00] main.ERROR: Magento\Framework\Exception\InputException: Can not resolve reCAPTCHA parameter. in /home/1218041.cloudwaysapps.com/rrkkmbpnmd/public_html/vendor/magento/module-re-captcha-ui/Model/CaptchaResponseResolver.php:25
Stack trace:
#0 vendor/magento/module-re-captcha-ui/Model/RequestHandler.php(112): Magento\ReCaptchaUi\Model\CaptchaResponseResolver->resolve()
#1 vendor/magento/module-re-captcha-customer/Observer/CreateCustomerObserver.php(67): Magento\ReCaptchaUi\Model\RequestHandler->execute()
#2 vendor/magento/framework/Event/Invoker/InvokerDefault.php(88): Magento\ReCaptchaCustomer\Observer\CreateCustomerObserver->execute()
#3 vendor/magento/framework/Event/Invoker/InvokerDefault.php(74): Magento\Framework\Event\Invoker\InvokerDefault->_callObserverMethod()
#4 vendor/magento/framework/Event/Manager.php(65): Magento\Framework\Event\Invoker\InvokerDefault->dispatch()
#5 generated/code/Magento/Framework/Event/Manager/Proxy.php(95): Magento\Framework\Event\Manager->dispatch()
#6 vendor/magento/framework/App/FrontController.php(279): Magento\Framework\Event\Manager\Proxy->dispatch()
#7 vendor/magento/framework/App/FrontController.php(211): Magento\Framework\App\FrontController->dispatchPreDispatchEvents()
#8 vendor/magento/framework/App/FrontController.php(147): Magento\Framework\App\FrontController->processRequest()
#9 vendor/magento/framework/Interception/Interceptor.php(58): Magento\Framework\App\FrontController->dispatch()
#10 vendor/magento/framework/Interception/Interceptor.php(138): Magento\Framework\App\FrontController\Interceptor->___callParent()
#11 vendor/nitropack/magento2-extension/Plugin/CacheDelivery/LocalCachePlugin.php(183): Magento\Framework\App\FrontController\Interceptor->Magento\Framework\Interception{closure}()
#12 vendor/magento/framework/Interception/Interceptor.php(135): NitroPack\NitroPack\Plugin\CacheDelivery\LocalCachePlugin->aroundDispatch()
#13 vendor/magento/module-store/App/FrontController/Plugin/RequestPreprocessor.php(99): Magento\Framework\App\FrontController\Interceptor->Magento\Framework\Interception{closure}()
#14 vendor/magento/framework/Interception/Interceptor.php(135): Magento\Store\App\FrontController\Plugin\RequestPreprocessor->aroundDispatch()
#15 vendor/magento/module-page-cache/Model/App/FrontController/BuiltinPlugin.php(71): Magento\Framework\App\FrontController\Interceptor->Magento\Framework\Interception{closure}()
#16 vendor/magento/framework/Interception/Interceptor.php(135): Magento\PageCache\Model\App\FrontController\BuiltinPlugin->aroundDispatch()
#17 vendor/magento/framework/Interception/Interceptor.php(153): Magento\Framework\App\FrontController\Interceptor->Magento\Framework\Interception{closure}()
#18 generated/code/Magento/Framework/App/FrontController/Interceptor.php(23): Magento\Framework\App\FrontController\Interceptor->___callPlugins()
#19 vendor/magento/framework/App/Http.php(116): Magento\Framework\App\FrontController\Interceptor->dispatch()
#20 generated/code/Magento/Framework/App/Http/Interceptor.php(23): Magento\Framework\App\Http->launch()
#21 vendor/magento/framework/App/Bootstrap.php(264): Magento\Framework\App\Http\Interceptor->launch()
#22 pub/index.php(30): Magento\Framework\App\Bootstrap->run()

bjolysharp · 2025-01-03T15:06:20Z

Why is this issue closed? We're still seeing the issue on Magento 2.4.7-p3:

[2025-01-03T13:21:50.059509+00:00] main.ERROR: Magento\Framework\Exception\InputException: Can not resolve reCAPTCHA parameter. in /chroot/home/.../html/vendor/magento/module-re-captcha-ui/Model/CaptchaResponseResolver.php:25

alexandresoaresramos · 2025-01-27T17:15:17Z

2.4.7 p3

{main} {"exception":"[object] (Magento\Framework\Exception\InputException(code: 0): Can not resolve reCAPTCHA parameter. at /home/viprac/public_html/vendor/magento/module-re-captcha-ui/Model/CaptchaResponseResolver.php:25)"} []

drabikowy · 2025-01-28T07:33:42Z

We have the same issue, I don't know why this ticket was closed with so many reports about issue existence.
Logs are spammed for us with the same errors.

engcom-Delta · 2025-01-29T12:56:03Z

Hi @stevekem ,

Thanks for your reporting and collaboration.
We have tried to reproduce the issue in 2.4.7-p3 instance and the issue is reproducible. Kindly refer the screenshots.

Steps to reproduce

Go to Configuration > Security > Google reCAPTCHA Admin Panel
Add your Google API Website Key & Google API Secret Key to any reCAPTCHA below:
reCAPTCHA v2 ("I am not a robot")
reCAPTCHA v2 Invisible
reCAPTCHA v3 Invisible
3.Select your reCAPTCHA version (with API keys above) for either below:
Enable for Login
Enable for Forgot Password
Save config
Flush cache
Observe exception.log
error displays - (Magento\Framework\Exception\InputException(code: 0): Can not resolve reCAPTCHA parameter. at C:\xampp8.2php\htdocs\magento247p3\vendor\magento\module-re-captcha-ui\Model\CaptchaResponseResolver.php:25)"} []

Thanks.

github-jira-sync-bot · 2025-01-29T12:57:59Z

❌ Cannot export the issue. This GitHub issue is already linked to Jira issue(s): https://jira.corp.adobe.com/browse/AC-3179

hardikkukadiya · 2025-03-19T10:36:25Z

Give me solution for stop generating error log

PieterCappelle · 2025-03-19T14:47:47Z

Any update about this or a solution?

gntlby · 2025-03-20T09:01:08Z

main.ERROR: Magento\Framework\Exception\InputException: Can not resolve reCAPTCHA parameter. in .../vendor/magento/module-re-captcha-ui/Model/CaptchaResponseResolver.php:25

We are experiencing the same issue on Magento 2.4.7-p4.

We would appreciate support regarding the solution.

hostep · 2025-03-24T10:59:55Z

Would patch MDVA-39305(or -V2 or -V3) help out here?
One of the errors they associate with that patch is the same as the one reported here. See: https://github.com/magento/quality-patches/blob/73ae870025d694cf39e2de6ffa3f63f24ca9efc8/tests/metadata/MDVA-39305-V3/var/log/support_report.log

Just guessing here ...

devchris79 · 2025-03-24T11:42:58Z

@hostep Thanks for that, we have seen this error and it was definitely correlating with a customer struggling to login, oddly switching browser sorted the issue at the time.
I have applied the quality patch and will see if the error is resolved.

frostitution · 2025-03-26T05:10:03Z

@devchris79 Hello, any update on your end?

devchris79 · 2025-03-26T10:28:11Z

@frostitution we had a couple more stamps on the evening after applying the patch, they were 28 seconds apart, so I would assume it was a result of a login attempt failure.
Our site has a low traffic level, so its hard to get a feel for if there has been a reduction in errors or no effect at all.

It may be a case that there is multiple ways that this error is being triggered.

devchris79 · 2025-03-31T12:58:03Z

There has been no further errors after appying patch MDVA-39305-V3 as suggested above by @hostep. I am wondering if the errors that I saw on the same day as applying the patch were the result of an old cache data.
I will post if we get any more errors, but I think the possible fix needs checking by others.
Given the fact the patch fixes login errors, it seems a no brainer to install.

devchris79 · 2025-04-01T12:43:32Z

Unfortunately the stamp has occured in the exception log again this morning:

[2025-04-01T06:23:45.675148+00:00] main.ERROR: Magento\Framework\Exception\InputException: Can not resolve reCAPTCHA parameter. in ../vendor/magento/module-re-captcha-ui/Model/CaptchaResponseResolver.php:25

bolasevich · 2025-04-02T20:22:13Z

i also have this issue

hewgim · 2025-04-09T17:44:26Z

Hi @devchris79, Are you seeing issues on the frontend because this ticket is specifically about trouble with google recaptcha when logging into the backend, which the @tschirmer code seems to have fixed and as far as I can see. And this code has been incorporated into the 2.4.6 branch as far as I can see.

Are people are still having issues with Google Recacptcha when logging into the backend ? If not then this ticket should probably be closed.

Regards

Mark

devchris79 · 2025-04-14T09:29:49Z

@hewgim The @tschirmer code seemed to fix the admin panel login errors for us. I can't speak for the main branch code fix as its not something we have tested.

If this ticket is to be closed a new one opened for the frontend issues, a link for users with the frontend ReCaptcha errors would be appreciated.

bolasevich · 2025-04-14T13:12:29Z

yes im still having frontend issues as well

…

On Mon, Apr 14, 2025 at 5:30 AM devchris79 ***@***.***> wrote: @hewgim <https://github.com/hewgim> The @tschirmer <https://github.com/tschirmer> code seemed to fix the admin panel login errors for us. I can't speak for the main branch code fix as its not something we have tested. If this ticket is to be closed a new one opened for the frontend issues, a link for users with the frontend ReCaptcha errors would be appreciated. — Reply to this email directly, view it on GitHub <#34975 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BKZRGSAY5SEMCPWTNOEZ2RL2ZN52XAVCNFSM5L76MJ72U5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TEOBQGEYDOOJRGM4Q> . You are receiving this because you commented.Message ID: ***@***.***> *devchris79* left a comment (magento/magento2#34975) <#34975 (comment)> @hewgim <https://github.com/hewgim> The @tschirmer <https://github.com/tschirmer> code seemed to fix the admin panel login errors for us. I can't speak for the main branch code fix as its not something we have tested. If this ticket is to be closed a new one opened for the frontend issues, a link for users with the frontend ReCaptcha errors would be appreciated. — Reply to this email directly, view it on GitHub <#34975 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BKZRGSAY5SEMCPWTNOEZ2RL2ZN52XAVCNFSM5L76MJ72U5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TEOBQGEYDOOJRGM4Q> . You are receiving this because you commented.Message ID: ***@***.***>

m2-community-project bot added the Issue: ready for confirmation label Jan 14, 2022

engcom-Hotel self-assigned this Jan 18, 2022

engcom-Hotel removed their assignment Jan 21, 2022

engcom-Delta self-assigned this Mar 1, 2022

engcom-Delta added Issue: needs update Additional information is require, waiting for response Area: Admin UI and removed Issue: ready for confirmation labels Mar 3, 2022

engcom-Delta closed this as completed Mar 21, 2022

engcom-Hotel added the Component: Captcha label Nov 14, 2024

engcom-Delta reopened this Jan 29, 2025

devchris79 mentioned this issue Mar 19, 2025

Can not resolve reCAPTCHA parameter. in vendor/magento/module-re-captcha-ui/Model/CaptchaResponseResolver.php:25 #39749

Closed

5 tasks

"Can not resolve reCAPTCHA parameter" entries in exception.log for Google reCAPTCHA Admin Panel #34975

"Can not resolve reCAPTCHA parameter" entries in exception.log for Google reCAPTCHA Admin Panel #34975

Comments

stevekem commented Jan 14, 2022 • edited Loading

Preconditions (*)

Steps to reproduce (*)

Expected result (*)

Actual result (*)

m2-assistant bot commented Jan 18, 2022

0xMatt commented Jan 19, 2022

stevekem commented Jan 20, 2022

stevekem commented Jan 20, 2022

ihor-sviziev commented Jan 26, 2022

stevekem commented Jan 26, 2022

ihor-sviziev commented Jan 26, 2022

stevekem commented Jan 26, 2022

ihor-sviziev commented Jan 26, 2022 • edited Loading

stevekem commented Jan 26, 2022

ihor-sviziev commented Jan 26, 2022

stevekem commented Jan 26, 2022

m2-assistant bot commented Mar 1, 2022

engcom-Delta commented Mar 3, 2022

engcom-Delta commented Mar 21, 2022

knoorani-ijona commented Apr 13, 2022

Hanhan1989 commented Apr 17, 2022 • edited Loading

Hanhan1989 commented Apr 17, 2022 • edited Loading

Themageguru commented Apr 28, 2022 • edited Loading

mikeastral commented Apr 30, 2022

Hanhan1989 commented May 4, 2022

benediktblank commented May 23, 2022 • edited Loading

engcom-Hotel commented Nov 14, 2024

mcspronko commented Nov 14, 2024

mostafa-elkholy commented Nov 15, 2024 • edited Loading

bjolysharp commented Jan 3, 2025

alexandresoaresramos commented Jan 27, 2025

drabikowy commented Jan 28, 2025

engcom-Delta commented Jan 29, 2025

github-jira-sync-bot commented Jan 29, 2025

hardikkukadiya commented Mar 19, 2025

PieterCappelle commented Mar 19, 2025

gntlby commented Mar 20, 2025

hostep commented Mar 24, 2025 • edited Loading

devchris79 commented Mar 24, 2025

frostitution commented Mar 26, 2025

devchris79 commented Mar 26, 2025

devchris79 commented Mar 31, 2025

devchris79 commented Apr 1, 2025

bolasevich commented Apr 2, 2025

hewgim commented Apr 9, 2025

devchris79 commented Apr 14, 2025

bolasevich commented Apr 14, 2025 via email

stevekem commented Jan 14, 2022 •

edited

Loading

ihor-sviziev commented Jan 26, 2022 •

edited

Loading

Hanhan1989 commented Apr 17, 2022 •

edited

Loading

Hanhan1989 commented Apr 17, 2022 •

edited

Loading

Themageguru commented Apr 28, 2022 •

edited

Loading

benediktblank commented May 23, 2022 •

edited

Loading

mostafa-elkholy commented Nov 15, 2024 •

edited

Loading

hostep commented Mar 24, 2025 •

edited

Loading