• I started receiving errors today. The plugin was working before. I turned on debug emails.
    The error log is:
    There was an error when trying to integrate with the 3rd party service

    **RAW RESPONSE**
    Array
    (
    [safe_message] => error object
    [object] => WP_Error Object
    (
    [errors] => Array
    (
    [http_request_failed] => Array
    (
    [0] => cURL error 56: OpenSSL SSL_read: SSL_ERROR_SYSCALL, errno 104
    )

    )

    [error_data] => Array
    (
    )

    )

    )

    • This topic was modified 6 years, 6 months ago by anjedeska.
Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Author zaus

    (@zaus)

    It’s either something to do with your server/hosting which may have upgraded recently or with the endpoint which may have stopped allowing old SSL (TLS < 1.2) connections. You’d have to check with them.

    I am having the same issue. any ideas on how to troubleshoot this?

    Thread Starter anjedeska

    (@anjedeska)

    Hi,

    I contacted my server and he said this was done by a recent update to cPanel for the sake of site/server/user security. It is possible to enable the legacy versions of SSL/TLS, but this is strongly discouraged as it’s to a greatly detrimental impact on security. They strongly advise that any app/service that is connecting to the server or needs to be properly updated to conform to modern security practices. Will the plugin be updated to be compatible with the recent SSL/TLS update?

    Plugin Author zaus

    (@zaus)

    Apologies, let me clarify: it’s nothing specifically to do with my plugin, as it’s just using whatever wp defaults to, as determined by your hosting. It sounds like you’ve discovered your hosting updated to TLS 1.2, so the next thing to check is whether your service allows it. If it doesn’t (which it should, and the internet agrees) then you might try something like the following to force it back down?

    https://github.com/woocommerce/woocommerce-gateway-stripe/issues/45

    Thread Starter anjedeska

    (@anjedeska)

    What if my server does not have the option to downgrade?

    Plugin Author zaus

    (@zaus)

    You’ll have to find some way to make wp change the TLS version when sending, per my suggested link earlier (google ‘WordPress send tls 1.2’). Or contact your endpoint support to see why they’re not supporting modern security standards yet.

    Plugin Author zaus

    (@zaus)

    I could also be mistaken – I just searched for your original 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?

    But otherwise, it’s basically an argument between your host and their.

    Hello Zaus,
    I followed this topic and the one opened on github.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!

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘CF7-3rdParty Integration Failure’ is closed to new replies.