WPPizza – A Restaurant Plugin for WordPress › Support › Add-Ons › Gateways › Stripe › Stripe Checkout returns Error: Internal Server Error
- AuthorPosts
- 24 February, 2017 at 4:16 pm #25846
Thanks, that was made by someone else, I will remove the line from WP-config
24 February, 2017 at 4:20 pm #25848dont remove it .
move it to the right place instead.24 February, 2017 at 4:39 pm #25851ok moved it up.
24 February, 2017 at 4:55 pm #25852ok, my educated guess is the following (this is admittedly difficult to find)
if you comment out approx line 11 in wppizza-gateway-stripe/ajax/ajax.php
error_reporting(0);
to read
// error_reporting(0);and do an order that throws that server error we have been talking about, you will now – most likely – find an entry in your debug.log that says
PHP Fatal error: Uncaught exception 'Stripe\Error\Authentication' with message '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.' in.......etc etci.e your ssl certificate and setup needs to be updated. you will need to speak to your host
(i’d suggest you comment out that line i mentioned above and do a test order that throws your error and check your debug log to confirm this)
24 February, 2017 at 4:57 pm #25853PS: Btw, error handling in wppizza 3.x will be handled differently to make finding these things easier
24 February, 2017 at 5:02 pm #25854This reply has been marked as private.24 February, 2017 at 5:04 pm #25855It is weird because the Stripe-Gateway of woocommerce worked with the same SSL
24 February, 2017 at 5:05 pm #25856This reply has been marked as private.24 February, 2017 at 5:05 pm #25857>It is weird because the Stripe-Gateway of woocommerce worked with the same SSL
because it’s probably still using an outdated stripe protocol/library24 February, 2017 at 5:11 pm #25858yup.
its using stripe 3.0.7
whereas wppizza stripe uses 3.20see also
https://support.stripe.com/questions/how-do-i-upgrade-my-stripe-integration-from-tls-1-0-to-tls-1-224 February, 2017 at 5:20 pm #25859Ok that makes sense. Thanks a lot Olly, I have contacted the hosting company
I will keep you updated, please don’t close topic yet.
Thanks for your work
24 February, 2017 at 6:09 pm #25862Got this reply from the hosting support:
Hi
I just checked on the server and the SSL certificate is properly installed for your client’s account.
I attached screenshots as a reference to this subject.
When we developed the website, we used stripe as a payment gateway and we have not experienced any errors, In fact all our clients have in use stripe like payment gateway.
For the error that you put me together I understand that in the pluging has to do with the redirection …. I advise you to speak with the developer of the plugin, to solve this matter.
Thank you
I told them it’s not working with stripe 3.20 and referenced them to https://www.ssllabs.com/ssltest/analyze.html?d=bellissimosg.ch&hideResults=on
will keep updated if I hear back
24 February, 2017 at 6:38 pm #25863the problem is the TLS1.1 protocol still being supported on that server (probably/perhaps open ssl version they are using, but i am not an expert)
in any event the stripe error clearly says what it isif there are issues they (that’s the host, not the website developers – unless they are one and the same) should speak to stripe.
>When we developed the website, we used stripe as a payment gateway and we have not experienced any errors,
so what. security issues change and get adapted accordingly24 February, 2017 at 6:53 pm #25864Here is the reply from the plugin developer:
Hi
We just update the curl scripting but, We recommend that the pluging developer consider making the plugin compatible with CurlSSL … Can you try it now? To see if the plugin works correctly…I tried again and get a new error:
[24-Feb-2017 18:49:11 UTC] PHP Fatal error: Uncaught exception ‘Stripe\Error\ApiConnection’ with message ‘Unexpected error communicating with Stripe. If this problem persists, let us know at [email protected].
(Network error [errno 1]: Protocol “https” not supported or disabled in libcurl)’ in /home/bellissi/public_html/wp-content/plugins/wppizza-gateway-stripe/sdk/lib/HttpClient/CurlClient.php:250
Stack trace:
#0 /home/bellissi/public_html/wp-content/plugins/wppizza-gateway-stripe/sdk/lib/HttpClient/CurlClient.php(212): Stripe\HttpClient\CurlClient->handleCurlError(‘https://api.str…’, 1, ‘Protocol “https…’)
#1 /home/bellissi/public_html/wp-content/plugins/wppizza-gateway-stripe/sdk/lib/ApiRequestor.php(189): Stripe\HttpClient\CurlClient->request(‘post’, ‘https://api.str…’, Array, Array, false)
#2 /home/bellissi/public_html/wp-content/plugins/wppizza-gateway-stripe/sdk/lib/ApiRequestor.php(64): Stripe\ApiRequestor->_requestRaw(‘post’, ‘/v1/charges’, Array, Array)
#3 /home/bellissi/public_html/wp-content/plugins/wppizza-gateway-stripe/sdk/lib/A in /home/bellissi/public_html/wp-content/plugins/wppizza-gateway-stripe/sdk/lib/HttpClient/CurlClient.php on line 250forwarded to host and awaiting reply
24 February, 2017 at 7:11 pm #25865says it all there
Protocol “https” not supported or disabled in libcurl(if the plugin did not support ssl/https it would not work for anyone, which simply is not the case)
the issue is that TLS 1.1 is still enabled (which can be disabled in the apache conf)
from the stripe sdk in use in the plugin
// Explicitly set a TLS version for cURL to use now that we’re starting
// to block 1.0 and 1.1 requests.
//
// If users are on OpenSSL >= 1.0.1, we know that they support TLS 1.2,
// so set that explicitly because on some older Linux distros, clients may
// default to TLS 1.0 even when they have TLS 1.2 available.
//
// For users on much older versions of OpenSSL, set a valid range of
// TLS 1.0 to 1.2 (CURL_SSLVERSION_TLSv1). Note that this may result in
// their requests being blocked unless they’re specially flagged into
// being able to use an old TLS version24 February, 2017 at 7:39 pm #25866worth a read too
https://stripe.com/blog/upgrading-tls24 February, 2017 at 9:15 pm #25873This reply has been marked as private.24 February, 2017 at 10:17 pm #25875This reply has been marked as private. - AuthorPosts
- The topic ‘Stripe Checkout returns Error: Internal Server Error’ is closed to new replies.