joelsawyer Posted October 1, 2018 Share Posted October 1, 2018 Having issues with reCAPTCHA. This is a new installation on a new server (AWS EC2) using the latest cubecart code (6.2.2) with the foundation skin. When attempting to checkout, I keep getting the following error: The verification code was incorrect. Please try again. - I tried to delete my Google reCAPTCHA keys and start again (thinking it was a configuration error the first time around) but that didn't seem to make any difference. - The cubecart admin setting is for `Invisible reCAPTCHA (Recommended)` - The reCAPTCHA admin is also set for Invisible and has the correct domain settings (even added the public EC2 address for good measure) Really puzzled why this isn't working. Any suggestions? Anything I missed? Also worth noting that I do see this badge in the bottom right corner... saying that this site is protected by reCAPTCHA. Link to comment Share on other sites More sharing options...
Al Brookbanks Posted October 1, 2018 Share Posted October 1, 2018 Check the request log in the admin control panel as the cURL request to verify the data with Google may be failing due to firewall or something. Link to comment Share on other sites More sharing options...
joelsawyer Posted October 1, 2018 Author Share Posted October 1, 2018 Looks like the Request log is showing timeout errors. Any idea how to address these timeouts? Request Sent - https://www.google.com/recaptcha/api/siteverify?secret=6LeE93IUAAAAAAcPSniZ87iFANQlbZaiWxJTw7kA&response=03AL4dnxrR8P5aW37oLzCkR_HAU5upJRDSP0dLuRBuNIdgKovpRtioS_qPdGxfrDZgbmtflPikG8nhn1NtHXluzGDcgAy5IjCItQSUuzV66KQgn4SLBwWygcOv_GgtTkbsOcKp26cwxTLiQaNh-Vnisecret=6LeE93IUAAAAAAcPSniZ87iFANQlbZaiWxJTw7kA&response=03AL4dnxrR8P5aW37oLzCkR_HAU5upJRDSP0dLuRBuNIdgKovpRtioS_qPdGxfrDZgbmtflPikG8nhn1NtHXluzGDcgAy5IjCItQSUuzV66KQgn4SLBwWygcOv_GgtTkbsOcKp26cwxTLiQaNh-Vnim1W6Wm_6asVDdYzhH2av4vQqzcjSYPscwdLsABRiaVqspTBcn2DOXVMp9rHEzJ7sdmqzNB2yLA55gthZsgudMVf4NuPByWoi6X4HzPh9ElL4czEZuzbd2SM6_9aCdb-ICzn3GhECJIUYpkEDKmwLZ5t89ZFX37tF0Zg&remoteip=***.***.***.*** Error:cURL Error (28): Connection timed out after 15000 milliseconds Response received Link to comment Share on other sites More sharing options...
Al Brookbanks Posted October 1, 2018 Share Posted October 1, 2018 It will be AWS firewall I expect. Link to comment Share on other sites More sharing options...
joelsawyer Posted October 1, 2018 Author Share Posted October 1, 2018 Brilliant! That was it. Just had to add an exception for outgoing traffic via HTTPS. Thanks for the clue! Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.