dchesbro

@insightdezign @capuderg I am also using GoDaddy as my hosting provider, though with dedicated servers and not VPS.

I also reached out to GoDaddy while troubleshooting this problem and was basically told I was on my own.

@capuderg That is correct.

I began experiencing this issue while using version 1.9.0 and modified the copy of CurlFactory.php included with that versions distribution of Guzzle as a temporary fix.

I then updated to version 2.0.0 when is became available, but still saw curl error 2. I implemented the same modifications used for version 1.9.0 as a temporary fix again.

Yesterday I tried reverting to version 1.8.1 and I am no longer seeing the curl error 2 or any other errors. As of this message I’ve reverted to this version of the plugin for all of our live websites and they appear to be operating as expected.

I’m continuing to examine the issue in our development environment to see if I can figure out why this started happening in the first place, and what might resolve it. I’ve collected the following details that might be helpful to anyone trying to do the same here:

Server Details
Server OS: CentOS 6.10
WHM/cPanel: 86.0.18
OS curl: 7.69.1
OS libcurl: 7.69.1
OS OpenSSL: 1.0.1e
PHP: 7.3.17
PHP curl: 7.69.1
PHP OpenSSL: 1.1.1g
WordPress: 5.4

Plugin Email Test Results
WP Mail SMTP 1.8.1: No error messages, test email received
WP Mail SMTP 2.0.0: Error message: “There was a problem while sending the test email”, no test email received

Versions:
WordPress: 5.4
WordPress MS: No
PHP: 7.3.17
WP Mail SMTP: 2.0.0

Params:
Mailer: gmail
Constants: No
Client ID/Secret: Yes
Auth Code: Yes
Access Token: Yes

Server:
OpenSSL: OpenSSL 1.1.1g 21 Apr 2020
PHP.allow_url_fopen: Yes
PHP.stream_socket_client(): Yes
PHP.fsockopen(): Yes
PHP.curl_version(): 7.69.1

Debug:
Mailer: Gmail
cURL error 2: easy handle already used in multi handle (see https://curl.haxx.se/libcurl/c/libcurl-errors.html)

It’s an especially confusing issue, I agree. I’ll continue to post here with anything I uncover, and check in to see if anyone else has found anything helpful. Good luck!

Edit: I can also confirm that an unmodified version 1.9.0 continues to produce the same error as version 2.0.0 above.

• This reply was modified 4 years, 7 months ago by dchesbro.

I’ve found that reverting to version 1.8.1 of WP Mail SMTP has resolved the issue for me, and checking the version changelogs it seems to implicate Guzzle again as likely being involved in the overall cause of this issue. From the 1.8.1 development notes:

Fixed: Revert Guzzle version to 6.4.1 because Sendinblue and Gmail mailers may experience issues under certain circumstances while sending emails (not all sites are affected).

As of this message I can confirm that this problem persists with the lastest version of WP Mail SMTP, version 2.0.0. That changelog did not mention a fix to this issue, but I tried just in case.

Alright, this bug has become quite a ride.

@capuderg The plugin is ActiveMember360, but during the course of troubleshooting problems with it I now believe that we experienced a separate, unfortunately timed issue rather than an issue connected with cURL or the other issues being discussed here.

As of this message I’ve re-implemented the solution I used above (originally posted here: https://github.com/guzzle/guzzle/issues/2617#issuecomment-617039676) and I am again no longer seeing this error.

That said, a permenent solution, and even identifying the cause is still needed. I’m continuing to keep an eye on the issue and will report back here with any developments.

• This reply was modified 4 years, 7 months ago by dchesbro.
• This reply was modified 4 years, 7 months ago by dchesbro.
• This reply was modified 4 years, 7 months ago by dchesbro.

Unfortunately while the temporary fix I implemented yesterday appeared to resolve this error where I was seeing it, it also appears to have has some unexpected consequences. Another plugin is now generating it’s own errors.

I am now back at square one, I cannot use WP Mail SMTP with Google, and in trying to solve this issue it appears to have uncovered a larger, wide spread issue.

I’m continuing to follow this thread and any others that are related to this issue, hopefully a workable resolution will be found soon.

@capuderg Sure thing.

I implemented the code suggested in this post: https://github.com/guzzle/guzzle/issues/2617#issuecomment-617039676

And I am also running CentOS on the server showing this error. As of this message it is running CentOS 6.10.

@capuderg Thanks for checking in.

So if you run the Email test in our plugin you always get this “cURL error 2”?

Yes, starting sometime on 4/17/20 WP Mail SMTP produces this error anytime I try sending a test email with Google as a mailer. Switching to PHP causes no error.

Did you try to deactivate and activate our plugin and try the Email test again?

Yes, I tried deactivating and reacitivating, but it has made no difference so far.

As of this message I have still been unable to resolve this issue, but I am now working my way through the solutions posted that I have not yet tried.

Edit: I’ve implemented the CurlFactory.php fix posted here: https://github.com/guzzle/guzzle/issues/2617

So far this appears to have resolved the issue, though obviously modifying third-party code in this way isn’t a long-term solution. Until the root cause is definitively identified and resolved, at least I can continue to use this plugin.

• This reply was modified 4 years, 7 months ago by dchesbro.
• This reply was modified 4 years, 7 months ago by dchesbro.
• This reply was modified 4 years, 7 months ago by dchesbro.

@capuderg Thanks for your reply.

I’ve tried installing Post SMTP as an alternative, and it did not resolve my issue. I also tried contacting my hosting and they were unable to help, either by downgrading cURL/libcur or by suggesting their own solution.

Does anyone have any other suggestions? I’ve tried reprovisioning EasyApache, using different PHP versions, and checking our problematic server’s setting against our non-problematic server. So far nothing has worked.

If anyone has other suggestions, or can point me towards anything that might help, I would greatly appriciate it.

@guytimes The website exhibiting this issue is on a separate server, but that server is running the same software and is configured the same as far as I am aware.

Hello Johan,

Thanks for the suggestion — after I enabled the ‘Require 3D Secure when applicable’ option my orders started updating as shown in royho’s screenshot.

I suppose the next step would be investigating why this option disrupts order status updates/webhook messages, but for the time being this has solved my issue. Thanks again for your help!