• Resolved pagnor

    (@pagnor)


    Ever since updating WC to v2.6 i get this message on all installs

    wp_remote_post() failed. PayPal IPN won’t work with your server. Contact your hosting provider. Error: Unsupported SSL protocol version

    I have checked the servers and all are able to use tls 1.2 all report
    PayPal_Connection_OKbool(true) when testing to paypal.

    Other software using ipn work 100% fine.

    https://wordpress.org/plugins/woocommerce/

Viewing 15 replies - 1 through 15 (of 31 total)
  • Plugin Contributor Claudio Sanches

    (@claudiosanches)

    @pagnor contact your host provider, ask to check and update cURL and OpenSSL.

    Plugin Author Mike Jolley (a11n)

    (@mikejolley)

    Doesn’t look like 1.2 is supported… “Unsupported SSL protocol version”.

    https://github.com/woothemes/woocommerce/blob/db6b6ebb5a95d6bdb09f6504e3c4ad95d1e1bdca/includes/class-wc-https.php#L118-L128

    This will soon be a hard requirement for PayPal so check your server. Running older version is insecure.

    Thread Starter pagnor

    (@pagnor)

    from every test ive done tlsv1.2 is used i have openssl 1.0.1e installed but woo is showing 1.0.0

    Plugin Author Mike Jolley (a11n)

    (@mikejolley)

    If woo shows 1.0.0, thats what is being used on your site.

    Hello Mike,

    I see you are certain that “If woo shows 1.0.0, thats what is being used on your site.” However my server says this:

    root@x [~]# openssl version
    OpenSSL 1.0.1e-fips 11 Feb 2013

    While WooCommerce Status still says this:

    cURL Version: 7.38.0, OpenSSL/1.0.0

    and gives this warning:

    wp_remote_post() failed. PayPal IPN won't work with your server. Contact your hosting provider. Error: Unsupported SSL protocol version

    Could you maybe take a second look at this?

    Thanks –

    Thread Starter pagnor

    (@pagnor)

    Thats exactly what i get yet i have another software that uses IPN and it is working fine ive tested the site and tlsv1.2 IS available.

    It was working fine yesterday until I upgraded to 2.6 lastnight.

    Do you have a link to a downgrade to test the theory?

    Plugin Author Mike Jolley (a11n)

    (@mikejolley)

    The new version forces 1.2, so logically this error would crop up now if unsupported.

    It doesn’t matter what version of OpenSSL is on your server afaik – PHP gets bundled with a version of OpenSSL.

    http://php.net/manual/en/function.curl-version.php

    ^ thats what is being used, and this won’t lie. This is telling you PHP only has access to 1.0.0.

    Contact your hosts or switch to a newer bundle of PHP if you can.

    Thanks for that Mike. After reading your reply, I set out to upgrade my PHP version from 5.6 .22 to… well whatever version it took for me to get the SSL issue resolved. I didn’t want to updated manually because my server runs on WHM and I didn’t want to break any connections between its WHM’s capabilities and PHP. That being the case, I quickly found myself in WHM / Home / Software / EasyApache 3. Unfortunately, I was only being offered 5.6.22 or lower versions.

    At that point I decided to load version 4 of EasyApache (although it is in beta). I accomplish this by taking these two steps:

    (1) Open the /etc/cpupdate.conf file and set the RPMUP key’s value to daily.

    (2) In WHM’s Update Preferences interface (Home >> Server Configuration >> Update Preferences), set the Operating System Package Updates setting to Automatic

    And then ran this script:

    /scripts/migrate_ea3_to_ea4 –run

    on my server.

    After that was done, I saw that I still had PHP version 5.6.22, but that the SSL had been updated when the EasyApache 4 script was run. The result was that WooCommerce was happy and I now have the option (in EasyApache 4) to upgrade my PHP version to any person I like up to 7.0.

    Not sure it will work that smoothly for anyone else (EasyApache 4 is beta and there may be conflicts if you have special configurations, but I thought I’d share it in case anyone wanted to try it.

    Be well –

    P.S. When I ran the “/scripts/migrate_ea3_to_ea4 –run” script it appeared to hang about midway, but I just left it and several minutes later it took off again. Just so you know, a bit of patience may be required.

    If you using WHM/Cpanel the problem woocommerce status says curl: opensslv1.0.0 however your server show

    root@x [~]# openssl version
    OpenSSL 1.0.1e-fips 11 Feb 2013

    You have to remove the curlssl from the cPanel server and recompile the php for fixing this issue as follows,

    update curl
    # yum update curlssl

    update openssl
    # yum update openssl

    remove curl and recompile the php

    # rm -rf /opt/curlssl
    # /scripts/easyapache

    refer the screenshot http://imgur.com/YBiAvgZ

    Thread Starter pagnor

    (@pagnor)

    Azli you are a star my friend worked a treat woocommerce isnt showing any error on remote post and reports to be running 1.0.1e
    Thank you

    Azli could you explain how to do the update curl and update openssl, I’m on a shared managed hosting with cPanel and my provider says the problem is developer based and doesnt come under the support scope.

    as pagnor said my host reports my version is OpenSSL 1.0.1e-fips

    and woocommerce system status says 7.38.0, OpenSSL/1.0.0

    thanks, Scott

    Plugin Author Mike Jolley (a11n)

    (@mikejolley)

    scotteh11 if this is a shared host it is unlikely you’ll be able to update it yourself as it affects all users on your server.

    I’d suggest keeping at them about it, since 1.0.0 is no longer supported.

    https://www.openssl.org/source/

    The 0.9.8 and 1.0.0 versions are now out of support and should not be used.

    If they offer the ability to switch PHP version, try a newer one.

    The version on my server is OpenSSL 1.0.1e-fips ( or so ive been informed by my host)
    Woocommerce is showing in system status 7.38.0, OpenSSL/1.0.0

    yeah my hosts claim they cant update anything else because im on shared hosting and that the version on my server is as stated above, is there another way round this? if i were to use PDT or API tokens rather than paypal IPN would it then worked? need a quick fix because im getting no love from my hosting provider
    thanks in advance, Scott

Viewing 15 replies - 1 through 15 (of 31 total)
  • The topic ‘wp_remote_post() failed. PayPal IPN won't work with your server. Contact your ho’ is closed to new replies.