Same message from Stripe. I ran the test provided by Stripe using the latest Composer package and it passed. That seems to indicate something in the plugin, perhaps our older version, is the hold up because the operating system is happy with TLS 1.2.
https://support.stripe.com/questions/how-do-i-upgrade-my-stripe-integration-from-tls-1-0-to-tls-1-2
A similar WP plugin seems to have acknowledge the issue as well
https://wordpress.org/support/topic/upgrade-my-stripe-integration-from-tls-10-to-tls-12?replies=7
Is there a particular plugin version we should aim for to ensure TLS 1.2?
Thanks
I’m having the same issue – Stripe are telling me that I’m using TLS 1.0 yet everything else about my config supports 1.2
I even mocked up an WP_Http_Curl test to check that I could request HTTPS using TLS1.2 and that works fine.
Patabugen,
I’m using an older version of the plugin. Are you running a more recent version of the plugin, or even the 3.0.8 version of the plugin? I’m curious if the version of the plugin matters.
I am just starting to read up on making sure my setup is ready for TLS 1.2 (and WooCommerce/Stripe) and Google brought to this thread.
Where are you seeing these errors? I am not seeing anything here but maybe I am not looking in the right place.
Cheers
Stripe is sending the notice about TLS 1.0. I’m using an older version of the package and can upgrade, but I’m hoping to know which version will satisfy the TLS 1.2 requirement.
Hello,
Any news on this subject please? I also checked and my webesite is well secured with TLS 1.2 and i keep receiving the same error message,
thanks a lot for your help,
BR
Armand
Anyone have any solutions to this? I am testing on a dev server but getting this message even though TLS is 1.2.
We upgraded WordPress, Woocommerce, and this WooCommerce Stripe Gateway plugin and a month ago. We just checked with Stripe and they confirmed that everything is now coming over as TLS 1.2.
I’m not sure what version(s) fix it, but our setup is WordPress 4.5.3, Woocommerce 2.6.4 and WooCommerce Stripe Gateway 3.0.2.
In short, upgrading corrects this issue.
I am having the same issue. Chrome says my site is secure with TLS 1.2. Everything is 100% up-to-date. Anyone find a solution besides upgrading?
The issue is not between your web server and the end-users’ browser, it’s an issue between your webserver and Stripe’s API server.
Upgrading the WordPress software will be necessary because your server is likely already fine and the problem is the WP code.
Again, I’m not sure which version(s) are the minimum requirement but the following configuration works, whereas it did not with earlier version of WordPress plugin code.
WordPress 4.5.3, Woocommerce 2.6.4 and WooCommerce Stripe Gateway 3.0.2.
I’d start by upgrading WooCommerce Stripe Gateway and then contact Stripe to see if that fixes it.
Thanks for the reply! It looks like it may actually be an outdated version of Curl. I used this plugin: https://wordpress.org/plugins/tls-1-2-compatibility-test/
True, if you’re on an older server (CentOS 5, RedHat 5) then Curl could be the issue, but I suspect the plugin will still be a problem even if curl is also a problem.
