New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Stripe AuthenticationError in Production is blocking us activating the new donations page #1081
Comments
I've ensured that our OpenSSL is up-to-date but I suspect that when we compiled Ruby it was that long ago that it was compiled against an OpenSSL without TLS 1.2 support so it's not working. Since we're already planning on upgrading Ruby (#1093), which will necessarily mean compiling it, I might do that first and see if it also fixes this. |
I've done the Ruby upgrade and sure enough it's working now:
I've tested donations on staging too and it's not affected by this error any more. |
Thanks @henare ! Big win with the Ruby upgrade too ✨ |
When you activate the new donation page and try and sign up for a donation, Stripe raises the error above.
Here's Stripe explanation of the phasing out TSL 1.1 https://stripe.com/blog/upgrading-tls
They have some instructions for identifying the issue here https://support.stripe.com/questions/how-do-i-upgrade-my-stripe-integration-from-tls-1-0-to-tls-1-2#ruby
They say the solution is to upgrade your OpenSSL version (and potentially
libssl
as well) following these instructions https://support.stripe.com/questions/how-do-i-upgrade-my-openssl-to-support-tls-1-2Kedumba, our server running PlanningAlerts, also runs a bunch of our other applications.
Upgrading this and managing the side-effects on our other projects is a bit beyond my experience, so I'm going to assign this to @henare to lead the charge on this. Feel free to delegate bits back to me 👍
The text was updated successfully, but these errors were encountered: