Error in Checkout TLS 1.0

  • I am still running in test mode, but when I try and test checkout I get the following error on the Thank You Page. My site is using TLS 1.2 via Let’s Encrypt, so I’m puzzled.

    System was not able to complete the payment. Stripe no longer supports API requests made with TLS 1.0. Please initiate HTTPS connections with TLS 1.2 or later. You can learn more about this at https://stripe.com/blog/upgrading-tls.

    The page I need help with: [log in to see the link]

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Contributor Alexander C.

    (@alexanderfoxc)

    Hi @rsather.

    It looks like your website has some issues with SSL certificates.

    From linux console, issue the following command and check its output. It connects to your website via SSL port (443) specifically using TLS v1.2:

    openssl s_client -connect mnissa.org:443 -tls1_2

    I’m specifically referring to these lines:

    depth=0 C = US, ST = Washington, L = Seattle, O = Odin, OU = Plesk, CN = Plesk, emailAddress = [email protected]
    verify error:num=18:self signed certificate
    verify return:1
    depth=0 C = US, ST = Washington, L = Seattle, O = Odin, OU = Plesk, CN = Plesk, emailAddress = [email protected]
    verify error:num=10:certificate has expired

    To check how the proper output should look like, you can check www.ads-software.com for example:

    openssl s_client -connect www.ads-software.com:443 -tls1_2

    And here’s how valid Let’s Encrypt certificate output looks like:

    openssl s_client -connect stripe-plugins.com:443 -tls1_2

    • This reply was modified 7 years, 2 months ago by Alexander C..
    Thread Starter rsather

    (@rsather)

    I have fixed the expired cert however I still have the issue

    Plugin Contributor Alexander C.

    (@alexanderfoxc)

    Looks like your website in unavailable in some ports of the world – https://www.host-tracker.com/InstantCheck/2/ba557e67-26fb-e711-8968-0003ff7328cc

    If you changed nameservers recently, that could be the case. If not – I guess there’s another issue to fix ??

    Thread Starter rsather

    (@rsather)

    Site appears down because we geoblock some countries. Name servers have not changed in over a year.

    Neither of those things should affect the fact that the plugin is trying to communicate with stripe using the wrong version of TLS.

    Other plugins work, I like the way this one operates better though, but if you don’t have interest in trying to fix the issue I’ll move on and use a different stripe plugin.

    Plugin Contributor Alexander C.

    (@alexanderfoxc)

    The problem is that I can’t even visit your site to be able to make some tests ?? Probably you’re blocking my country as well.

    If you want me to take a closer look, can you please contact me at alexanderfoxc at @gmail.com and provide WP Admin access to your site? You would also have to unblock my IP (which I’m going to provide).

    Thread Starter rsather

    (@rsather)

    Does the plugin use cURL?

    Plugin Contributor Alexander C.

    (@alexanderfoxc)

    Yep. It uses official Stripe PHP library, which is using cURL to make API requests.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Error in Checkout TLS 1.0’ is closed to new replies.