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

[timpea-splat]

Preconditions and environment

• Magento Version: 2.4.6-p3, issue also occurred on earlier versions

Steps to reproduce

Not found a way to reproduce the error every time.

1. Configuration > Security > Google ReCaptcha StoreFront
2. Enable reCaptcha v2 Invisible

We are receiving this error roughly 2-3 times a day. ReCaptcha works correctly when testing with no error.

Expected result

No error

Actual result

Error in exception.log:
[2023-10-19T09:31:16.313374+00:00] main.ERROR: Magento\Framework\Exception\InputException: Can not resolve reCAPTCHA parameter. in /data/web/public/vendor/magento/module-re-captcha-ui/Model/CaptchaResponseResolver.php:25
Stack trace:
#0 /data/web/public/vendor/magento/module-re-captcha-ui/Model/RequestHandler.php(112): Magento\ReCaptchaUi\Model\CaptchaResponseResolver->resolve()
#1 /data/web/public/vendor/magento/module-re-captcha-customer/Observer/CreateCustomerObserver.php(67): Magento\ReCaptchaUi\Model\RequestHandler->execute()
#2 /data/web/public/vendor/magento/framework/Event/Invoker/InvokerDefault.php(88): Magento\ReCaptchaCustomer\Observer\CreateCustomerObserver->execute()
#3 /data/web/public/vendor/magento/framework/Event/Invoker/InvokerDefault.php(74): Magento\Framework\Event\Invoker\InvokerDefault->_callObserverMethod()
#4 /data/web/public/vendor/magento/framework/Event/Manager.php(65): Magento\Framework\Event\Invoker\InvokerDefault->dispatch()
#5 /data/web/public/generated/code/Magento/Framework/Event/Manager/Proxy.php(95): Magento\Framework\Event\Manager->dispatch()
#6 /data/web/public/vendor/magento/framework/App/FrontController.php(279): Magento\Framework\Event\Manager\Proxy->dispatch()
#7 /data/web/public/vendor/magento/framework/App/FrontController.php(211): Magento\Framework\App\FrontController->dispatchPreDispatchEvents()
#8 /data/web/public/vendor/magento/framework/App/FrontController.php(147): Magento\Framework\App\FrontController->processRequest()
#9 /data/web/public/vendor/magento/framework/Interception/Interceptor.php(58): Magento\Framework\App\FrontController->dispatch()
#10 /data/web/public/vendor/magento/framework/Interception/Interceptor.php(138): Magento\Framework\App\FrontController\Interceptor->___callParent()
#11 /data/web/public/vendor/magento/module-store/App/FrontController/Plugin/RequestPreprocessor.php(99): Magento\Framework\App\FrontController\Interceptor->Magento\Framework\Interception\{closure}()
#12 /data/web/public/vendor/magento/framework/Interception/Interceptor.php(135): Magento\Store\App\FrontController\Plugin\RequestPreprocessor->aroundDispatch()
#13 /data/web/public/vendor/magento/module-page-cache/Model/App/FrontController/BuiltinPlugin.php(71): Magento\Framework\App\FrontController\Interceptor->Magento\Framework\Interception\{closure}()
#14 /data/web/public/vendor/magento/framework/Interception/Interceptor.php(135): Magento\PageCache\Model\App\FrontController\BuiltinPlugin->aroundDispatch()
#8730 /public/vendor/magento/framework/Interception/Interceptor.php(153): Magento\Framework\App\FrontController\Interceptor->Magento\Framework\Interception\{closure}()
#16 /data/web/public/generated/code/Magento/Framework/App/FrontController/Interceptor.php(23): Magento\Framework\App\FrontController\Interceptor->___callPlugins()
#17 /data/web/public/vendor/magento/framework/App/Http.php(116): Magento\Framework\App\FrontController\Interceptor->dispatch()
#18 /data/web/public/vendor/magento/framework/App/Bootstrap.php(264): Magento\Framework\App\Http->launch()
#19 /data/web/public/pub/index.php(30): Magento\Framework\App\Bootstrap->run()

Additional information

Related issue: #34975

Release note

No response

Triage and priority

• 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]

Hi @timpea-splat. Thank you for your report.
To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

• @magento give me 2.4-develop instance - upcoming 2.4.x release
• For more details, review the Magento Contributor Assistant documentation.
• Add a comment to assign the issue: @magento I am working on this
• To learn more about issue processing workflow, refer to the Code Contributions.

---

Join Magento Community Engineering Slack and ask your questions in #github channel.
⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
🕙 You can find the schedule on the Magento Community Calendar page.
📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

[m2-assistant]

Hi @engcom-Bravo. 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).
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• 3. Add Area: XXXXX label to the ticket, indicating the functional areas 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.

[p24-max]

Facing same issue with Magento 2.4.4-p6, is there any fix for it?

[engcom-Bravo]

Hi @timpea-splat,

Thank you for reporting and collaboration.
Verified the issue on Magento 2.4-develop instance and the issue is not reproducible.Kindly refer the screenshots.

Steps to reproduce

• Configuration > Security > Google ReCaptcha StoreFront
• Enable reCaptcha v2 Invisible

There is no error in exception.log.

Kindly recheck the behaviour on Magento 2.4-develop instance and elaborate steps to reproduce if the issue is still reproducible.

Thanks.

[engcom-Bravo]

Hi @timpea-splat,

We have noticed that this issue has not been updated since long time.
Hence we assume that this issue is fixed now, so we are closing it. Please feel to raise a fresh ticket or reopen this ticket if you need more assistance on this.

Thanks.

[rejith7]

Hi, i've faced the same issue on 2.4.5-p4 EE and my recaptcha on frontend customer account create page fails mostly. I tested on both V2 invisible and V3 invisible, but both gave same listed error

[rejith7]

@p24-max we're you able to resolve this issue ?

[p24-max]

@rejith7 I disabled the recaptcha as its not working properly :/

[minhluan259]

Facing same issue with Magento Magento 2.4.6-p3, 2.4.7-beta1, 2.4.7-beta2
any update on this?

[minhluan259]

@engcom-Bravo the exception.log appear when a bot attack (tool) create a post request without recaptcha param.

Here the debug info:

[2024-01-30T05:39:37.024093+00:00] main.INFO: createpost [] []
[2024-01-30T05:39:37.027508+00:00] main.INFO: customer [] []
[2024-01-30T05:39:37.027721+00:00] main.INFO: success_url=&error_url=&firstname=https://jmybd.blogspot.sg/ - 517610 RUB GAZPROM&lastname=https://jmybd.blogspot.sg/ - 517610 RUB GAZPROM&email=1661919960751685@facebook.com&password=d263sqeR4ha5BXr&confirmation=d263sqeR4ha5BXr&form_key=baEtSv32jdr55xaZ [] []
[2024-01-30T05:39:37.027863+00:00] main.INFO: Array
(
    [success_url] => 
    [error_url] => 
    [firstname] => https://jmybd.blogspot.sg/ - 517610 RUB GAZPROM
    [lastname] => https://jmybd.blogspot.sg/ - 517610 RUB GAZPROM
    [email] => 1661919960751685@facebook.com
    [password] => d263sqeR4ha5BXr
    [confirmation] => d263sqeR4ha5BXr
    [form_key] => baEtSv32jdr55xaZ
)
 [] []

[davirs]

same problem here. I can simulate this error on the standard Magento registration screen /customer/account/create/
So it's not something specific caused by "bots"...

I also noticed that it is random, filling out the form with exactly the same data sometimes works and other times it doesn't.

I believe it could be a problem with sessions/cache, since we use varnish+redis... If it were a fault in the code or in the captcha settings, all attempts should fail, right?

[kennylawrence]

Apparently I have been getting this for some time, I just missed it in a sea of unrelated exceptions.
I am using 2.4.6-p1. @davirs I'm also using varnish+redis

[jorgb90]

Same issue here with recaptcha enabled!

Same #34975

[chrisoliver90]

We have the same issue on 2.4.7-p1
It seems very intermittent in the logs and I am unable to replicate. Is this believed to be to do with customer account creation?
Seems somewhat related to 34975 from a couple years ago.
Possibly to do with bots trying to create customer accounts?

[indrisepos]

I have the same problem. We are using 2.4.7-p2

[arvind-curotec]

same issue

[bolasevich]

same issue