not sending

Hello,

Unfortunately I am unable to reproduce the error you are experiencing. However it seems that the server that your website is running on is not able to open the url https://www.google.com/recaptcha/api/siteverify
Google captcha needs to open this url in order to verify that the captcha is correct.

I would check with your host to make sure that they have opened the relevant ports to allow you to access this url.

Sometimes hosts can change settings on the server so this may be why your site was working and it isn’t now.

Hi,

indeed: It’s hard for me to debug this (shared hosting with limited features), but I can get this result on a console:

[code]
> wget https://www.google.com/recaptcha/api/siteverify
--2015-09-07 12:00:02-- https://www.google.com/recaptcha/api/siteverify
Resolving https://www.google.com... 173.194.116.180, 173.194.116.179, 173.194.116.176, ...
Connecting to https://www.google.com|173.194.116.180|:443... connected.
ERROR: cannot verify https://www.google.com's certificate, issued by /C=US/O=Google Inc/CN=Google Internet Authority G2:
Unable to locally verify the issuer's authority.
To connect to https://www.google.com insecurely, use --no-check-certificate.
[/code]

So it seems clear, the server can’t verify Google’s SSL certificate.

Can you venture a guess as to why? Is this Google’s fault or my provider’s?

Regards

That is indeed what appears to be happening.

I don’t know how you would get around this unless your host can help.

The alternative is to disable recaptcha and turn on akismet. That way all form submissions get filtered by akismet and you shouldn’t get any spam come through.

I’ve contacted my provider on this issue.

Thanks for your help!

Regards

Hi again,

Sorry, but I have to come back on this once more:

My provider told me that the error I’ve been getting from my wget-test referred to missing parameters on the URL and/or unspecified methods (get/post). This makes sense, because a normal request will surely transmit at least the Google API-key in some way, probably as part of the URL. In any case, I get a similar error if I try the wget at home – indicating that this isn’t the problem on my server after all.

Additionally, as I just noticed the behaviour on my WordPress-site has changed: Before, the “send” button simply did nothing. Now, the message “Please solve the recaptcha to continue.” appears. This is after the reCAPTCHA has already been marked with a green check mark, indicating a successful answer.

Can I get some sort of debug log from the plugin?

Regards

PS: To make matters worse – I just tried a different contact form plugin, and it worked there. So it actually seems to be a problem with CaSCF after all.

Yes the secret key along with the IP address and the response code should be sent to google. For some reason in your setup is not doing that.

Can you give me a URL with the contact form on it?

I’m having the same issue. I presume it’s something of the host’s doing. Has there been any known fix?

No, I don’t know of a fix. The demo page I set up apparently wasn’t enough to figure out the problem.

I ended up changing to another plugin. There it worked on the first try.

Regards

I have a theory guys.

This plugin has been developed to be super lightweight. It does not load any scripts that it doesn’t need. If you don’t use recaptcha or ajax then it will not load the scripts for that.

The downside (if you can call it that) is that it must be able to load the needed scripts in the footer. Due to this plugin being a shortcode, the headers have already been sent so it is not possible to load the scripts in the header even if it tried to.

If the theme does not call <?php wp_footer(); ?> in the footer template file then none of the scripts that this plugin needs will be loaded, therefore recaptcha will not work, the form will not validate and therefore the message will not be sent. This would also cause problems for other plugins that need to load scripts or styles in the footer.

If your theme does not call wp_footer() then you must raise this issue with the theme author.