No Longer Pushing Info to SF
Closed this issue · 9 comments
About 14 hours ago form submissions stopped being forwarded through to SalesForce where they are normally created as Leads. I know the Forms we're successfully submitted because I still received emails and I have Flamingo installed as a third back-up. I have the most current version of WP on my site and the most current version of your plug-in.
RAW RESPONSE
Array
(
[safe_message] => error object
[object] => WP_Error Object
(
[errors] => Array
(
[http_request_failed] => Array
(
[0] => cURL error 56: SSL read: error:00000000:lib(0):func(0):reason(0), errno 104
)
)
[error_data] => Array
(
)
)
)
A couple other people have recently mentioned the same SSL error. After the POODLE and Heartbleed etc vulnerabilities, lots of sites and hosting started working on disabling "old" ssl, and we're really close to the deadline:
https://blog.pcisecuritystandards.org/are-you-ready-for-30-june-2018-sayin-goodbye-to-ssl-early-tls
Check with either Salesforce if they started requiring TLS 1.2 (or are just rejecting TLS 1.0), or if your hosting started sending 1.2 and Salesforce isn't accepting it. In either case it's probably something you'll have to check with your hosting to "correct". Google 'WordPress send tls 1.2' for more info?
I could also be mistaken - I just searched for a similar error message and found this: https://forum.ait-pro.com/forums/topic/unable-to-upgrade-bps-pro-from-13-3-3-to-13-4/ so maybe increase the timeout setting in my plugin?
It's possible, but I don't know what I would do as I'm using native wp functionality to make requests (wp_remote_post), so there shouldn't be anything for me to do.
I would suggest finding some other endpoint that can confirm you're actually sending TLS 1.2, like the suggestions at https://security.stackexchange.com/questions/127984/what-website-accepts-only-tls-1-2-so-i-can-verify-client-capability
Another step is to turn on wp_debug mode and check the logs to see if there's any more insight there. You can also try disabling all your other plugins (or one-by-one) when submitting the form to see if it's a conflict.
Sorry I don't have any better advice.
I didn't have to switch, I was just unsure if you checked closed issues. Thanks for reopening / continuing to look into this for me. I will continue the conversation on the new issue, as it has more complete information about my issue, so feel free to close this one.
I think I still get notices from comments on closed issues, I only closed it because I didn't think it was specifically my plugin.
Hello Zaus,
I followed this topic and the one opened on wordpress.com and I have the same issue that other are describing. For more than a week CF7-3rdParty Integration plugin stopped sending leads to SF and I get the same "cURL error 56: OpenSSL SSL_read: SSL_ERROR_SYSCALL, errno 104" error. There is something wrong happening with the pugin and I couldn't find any confirmed solution by the people that reported it before.
I believe I speak for everyone when I say that we would really appreciate your help for a working fix for this error we are getting.
Many thanks!