impress-org / givewp

GiveWP - The #1 Donation Plugin for WordPress. Easily accept donations and fundraise using your WordPress website.
https://givewp.com/
GNU General Public License v3.0
345 stars 191 forks source link

Stripe Payment Gateway; Critical error on servers running CentOS #4652

Closed Gaffen closed 2 years ago

Gaffen commented 4 years ago

Bug Report

User Story

As an administrator, I want to enable Stripe payments so that users can make payments to my system.

Details

Stipe currently doesn't manage to process transactions on certain CentOS systems.

Current Behavior

Something within the Stripe php client has broken on CentOS servers which causes the payment process not to be completed. The error is along the lines of Network error [errno 2]: easy handle already used in multi handle.

Expected Behavior

For the stripe payment gateway to complete the transaction successfully.

Bug Type

Steps to Reproduce

  1. Install GiveWP and configure Stripe
  2. Attempt to complete any donation

Related

I have already let the stripe developers know; issue can be found here: https://github.com/stripe/stripe-php/issues/918

Possible Solution

One of the maintainers made the suggestion of this coe as a work around:

$curl = new \Stripe\HttpClient\CurlClient();
$curl->setEnablePersistentConnections(false);
\Stripe\ApiRequestor::setHttpClient($curl);

Acceptance Criteria

Environment

Operating System
  • CentOS 6.10
  • Version: Give 2.6.2
Browser
  • All Browsers
WordPress System Info WordPress 5.4 running on php 7.3
rickalday commented 4 years ago

Related: https://secure.helpscout.net/conversation/1153991680/64451?folderId=3400524

jonwaldstein commented 2 years ago

@Gaffen checking in here, was this ever resolved? Seems like a very specific server issue that would be a little difficult for us to replicate.

Gaffen commented 2 years ago

Hey @jonwaldstein, unfortunately I moved on from the project so I don't really have access to it anymore. However we did implement the temporary fix given here. It worked, so in that sense my problem was resolved!

And yes, I agree it does seem like a very specific issue. I'm not sure if there's much else I can provide that might help with this, but I'm happy to answer any questions you might have!

jonwaldstein commented 2 years ago

@Gaffen thanks! we appreciate you reporting this and providing your workaround. It will help for any future debugging. I'm going to close this for now until someone encounters this again. ✌️