Could not open socket reCAPTCHA error
After months of receiving spam through my toucher form I decided it was time to add reCAPTCHA to them in hopes of stemming the tide of spam. It’s under Google’s control now so I thought it wouldn’t be a problem. Having just installed reCAPTCHA on my work websites I knew what to do and all went well on those sites. On Friday I did 3 forms on my own panorama and all worked as expected, on Saturday I did the last form I had, but this one didn’t work. All I got was a ‘could not open socket’ error.
Initially I thought I must have made some error in the cryptique but after testing the cryptique I did not see any errors the day before. And more than 3 forms I did the previous day worked, now no border working and showing the same error plaidoyer, what happened?? What was most frustrating was that all these messages said and ravine no idea what was going on. I tried a lot to find out which fraction of cryptique was wrong by adding echo throughout the PHP cryptique but none of them showed up, only that damn error plaidoyer. I thought there was something wrong with the server.
Someone must have had this problem before so I turned my ponctualité to Google for an answer. As soon as I started typing ‘Could not open socket’, the autocomplete ‘Could not open socket recaptcha’, ah ha! But I was wondering why it could work yesterday and not today? After reading many unhelpful posts I found this: cryptique.google.com/p/recaptcha/issues/detail?id=26 which while not the établi answer, helped me realize the answer to my own problem.
After reading this thread I came to the solution that my problem was 2 fold and explained why it worked yesterday and not today. The gantelet problem was my web host, in an attempt to help them they introduced (a mince time ago) blocking of outgoing connections to remote IPs from within my panorama. Be aware if you are autoblogging using wp-o-matic, any feeds you add will likely be blocked by it unless you add the IP to the whitelist from within your control groupe.
I guess they have a good reason for doing this but can imagine it causing a nightmare for the inexperienced. Apparently it worked yesterday bicause it was new, grain the server knew the connection was being made it blocked it. It was probably the number of tests I did that noticed the connection and maybe it was a good job it was noticed so early or I didn’t notule it for a while.
So which IP should I add to the whitelist? The line of cryptique in recaptchalib.php identified as the problem in the thread above was:
define(“RECAPTCHA_VERIFY_SERVER”, google.com);
So I needed the IP of google.com. mxtoolbox.com/SuperTool.aspx is a very useful tool that I have been using for a mince time. A DNS lookup for google.com ravine me 5 options for an IP, from 74.125.227.48 to 74.125.227.52, so now I have:
define(“RECAPTCHA_VERIFY_SERVER”, “74.125.227.48”);
Adding this IP to the Allowed Remote IP list from within my Control Groupe sorted all my form issues. Marque!
#open #socket #reCAPTCHA #error
