XF 1.5 ReCAPTCHA (No CAPTCHA) connection error

[ActorMike]

I've recently been getting these errors in the server logs periodically, but whenever I test the Captcha box it works. Also, I checked where someone logged an error whow as registering, but they ended up registered, so they must have gotten the box checked somehow. I have my own server in a datacenter, self managed, and never have had these issues over the years. Not sure when it started happening, but possibly related to me switching the site over to https:// a few months ago.


Zend_Http_Client_Adapter_Exception: ReCAPTCHA (No CAPTCHA) connection error: Unable to Connect to ssl://www.google.com:443. Error #0: - library\Zend\Http\Client\Adapter\Socket.php:235
Generated By: Unknown Account, 6 minutes ago

Thanks for any assistance you can provide. The server error log has always been empty up until this started recently.

We are running PHP 7.1.17 and Zend Extension 320160303

 

[Ozzy47]

That simply means a connection error to the Google recaptcha service. It could be temporary or it could be being blocked upstream.
Normally it's a temporary issue - but if it continues you most likely need to contact your hosting provider.

 

[ActorMike]

That simply means a connection error to the Google recaptcha service. It could be temporary or it could be being blocked upstream.
Normally it's a temporary issue - but if it continues you most likely need to contact your hosting provider.

as noted, we are the hosting provider. The server is in a datacenter, so no reason for this to occur. Seems to be related to switching over to SSL.

 

[Ozzy47]

Have a read here, that might help.

 

[ActorMike]

Have a read here, that might help.

I did the curl -Iv https://www.google.com/ command and this was returned:



HTTP/1.1 200 OK
Date: Sun, 13 May 2018 18:26:15 GMT
Expires: -1
Cache-Control: private, max-age=0
Content-Type: text/html; charset=ISO-8859-1
P3P: CP="This is not a P3P policy! See g.co/p3phelp for more info."
Server: gws
X-XSS-Protection: 1; mode=block
X-Frame-Options: SAMEORIGIN
Set-Cookie: 1P_JAR=2018-05-13-18; expires=Tue, 12-Jun-2018 18:26:15 GMT; path=/; domain=.google.com
Set-Cookie: NID=130=l6pOvl8ICjrkGczMah-0hd1I0LCYllv3Ue6WF4YlSdXNmbUUEZmZ2RgwWdIsN7WWoMhVi_YrXEAvaE7jKzC9H-RCLvV-NdRYDzfdCl6HGGLT6qJhJ47jHTxfMK-gF2G0; expires=Mon, 12-Nov-2018 18:26:15 GMT; path=/; domain=.google.com; HttpOnly
Alt-Svc: hq=":443"; ma=2592000; quic=51303433; quic=51303432; quic=51303431; quic=51303339; quic=51303335,quic=":443"; ma=2592000; v="43,42,41,39,35"
Transfer-Encoding: chunked
Accept-Ranges: none
Vary: Accept-Encoding

 

[ActorMike]

I am wondering if this is related to any old links we have that point to the http:// version of the register page or password reset, and when it redirects to https:// that server error is logged?