Server error 60 0
Permalink Browser Info Environment
I am getting log report of Server error 60 0 I have configured the captcha setting to active captcha is Invisible Captach with the keys I have linked and generated via the link, however, I am getting "We detected that your site is not verifying reCAPTCHA solutions. This is required for the proper use of reCAPTCHA on your site. Please see our developer site for more information." I am not sure what to do to make this work
when my end users submit they get a error saying the captach failed
when my end users submit they get a error saying the captach failed
| Type: | Discussion |
|---|---|
| Status: | In Progress |
Hi,
We're experiencing the same issue. We used to have Repatcha V1 (working) but that expired by April 1st. First I thought perhaps the error occured due to both being installed, I unstalled V1 and reinstalled Invisible Captcha.
Requested new keys, installed the invisible captcha and we get the same error: "Incorrect image validation code. Please check the image and re-enter the letters or numbers as necessary."
We checked with your php snipplet and that works, we get the same output.
Any ideas?
(Site is running C5 version 5.6.2)
We're experiencing the same issue. We used to have Repatcha V1 (working) but that expired by April 1st. First I thought perhaps the error occured due to both being installed, I unstalled V1 and reinstalled Invisible Captcha.
Requested new keys, installed the invisible captcha and we get the same error: "Incorrect image validation code. Please check the image and re-enter the letters or numbers as necessary."
We checked with your php snipplet and that works, we get the same output.
Any ideas?
(Site is running C5 version 5.6.2)
"Incorrect image validation code. Please check the image and re-enter the letters or numbers as necessary."
That error makes me wonder if you've got the right CAPTCHA enabled in the dashboard.
Also, if you check in the dashboard reports->logs, you should be able to filter by 'Invisible Recaptcha' and see the actual errors being returned.
That error makes me wonder if you've got the right CAPTCHA enabled in the dashboard.
Also, if you check in the dashboard reports->logs, you should be able to filter by 'Invisible Recaptcha' and see the actual errors being returned.
Hi,
We did enable Invisible Captcha, and yes it seems to be the error code of the original SecurImage script that is send to the user. Front-end does load the 'I am not a Robot' thing though.
The server logs show e.g.:
3:13:57 PM at 2018-04-11 Invisible Recaptcha Guest Server error 60 0
We did enable Invisible Captcha, and yes it seems to be the error code of the original SecurImage script that is send to the user. Front-end does load the 'I am not a Robot' thing though.
The server logs show e.g.:
3:13:57 PM at 2018-04-11 Invisible Recaptcha Guest Server error 60 0
OK, Server error 60 is an SSL certificate issue, so make sure the validate SSL option is off.
Tried that before. Just requested new keys as I noticed that in fact the keys were v2 recaptcha keys and not 'Invisible recaptcha'.
Did turn off the SLL thing, but still unfortunately:
9:29:47 AM Invisible Recaptcha Guest Server error 60 0
Did turn off the SLL thing, but still unfortunately:
9:29:47 AM Invisible Recaptcha Guest Server error 60 0
I've uploaded a revised version that disables CURLOPT_SSL_VERIFYPEER as well as CURLOPT_SSL_VERIFYHOST. Please update and try this version. Make sure that the SSL verify option is off. There's now a warning in the log if it's off.
YES! This does the trick :-) Thanks a lot!
Great. Have a spam free day :)
Your web server needs to be able to verify the input by making a POST request tohttps://www.google.com/recaptcha/api/siteverify...
If it can't do that, that probably explains why it's not working.
There are a few reasons that this might fail:
1) Your web server can't resolve google.com to an ip address
2) outgoing web requests are firewalled or blocked
3) Your server can't verify the ssl certificate used by google.com
Try uploading this php file to your document root, and then run it in your browser:
if all is well, it should respond with