[#5858] Impossible to register wrong captcha

Ok, have made some error output improvements for next nightly release for reCaptcha usage. Not sure where it's failing, but this should help find what exactly is going wrong.

It's possible they're taking too long to complete registration, they complete captcha, and before it's verified it expired. reCaptcha doesn't work so great for long forms as it only lasts about 2 minutes I believe. This issue also works in reverse. They complete the captcha, take too long completing the form, and the captcha session expires. It appears to be a commonly reported problem depending on the usage.

It maybe possible to force the captcha to reset using API as there is a callback event for expiry in reCaptcha API. Have added a bug ticket to monitor this issue further and see if I can track down a cause. If an error is thrown during your tests please let me know what it is so can further track down what's going on.

forge.joomlapolis.com/issues/5858

After checking with recaptcha and latest build, I get error : cURL error 77:

Reverting back to internal code for now.

Do you know where it could come from ?

cURL error 77 means your server isn't setup for outbound HTTPS cURL calls due to certificate not working. The verify server at Google is HTTPS and is setup to set an HTTPS cURL call per Google documentation. You'll need to contact your host to have them fix this. Below is the error specifically.

curl.haxx.se/libcurl/c/libcurl-errors.html#CURLESSLCACERTBADFILE

You can try changing it to HTTP below, but I've no idea if it'll work.

IN: components/com_comprofiler/plugin/user/plug_cbantispam/cbantispam.php
ON: Line 1050
FROM: TO:
Your other usages maybe validating the captcha in browser using JS. Don't know for sure as I didn't write those usages.

Thanks a lot for this
I did not check that curl needed a CA for ssl

So for people with the same kind of problem, I just added a line in the php.ini file like
curl.cainfo = pathTO/AddTrustExternalCARoot.crt

pointing to a decent Certificate Authority and restart http

Strange that we did not get the problem before as we used this for some months before seing this problem. Maybe an upgrade in ssl libraries ?

The HTTP request was changed to our Guzzle library usage instead of our old usage that was using fopen most likely.