cURL error 2: easy handle already used in multi handle

  • I’ve had WP Mail SMTP installed and activated on a website I manage using Google
    as a mailer for sometime, and just today I am seeing the following error:

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

    This error appears every time I try to send a test email using Google as a mailer. I have several other websites using this plugin with Google as a mailer all functioning without issue. Here is the debug error in full:

    Versions:
    WordPress: 5.4
    WordPress MS: No
    PHP: 7.3.16
    WP Mail SMTP: 1.9.0

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

    Server:
    OpenSSL: OpenSSL 1.1.1f 31 Mar 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)

    I haven’t been able to find any previous support requests or discussion topics for this specific error message, and I can’t find any information about what specifically might have caused this error message to suddenly appear in the first place.

    Thanks in advance for any help troubleshooting this issue.

Viewing 15 replies - 16 through 30 (of 44 total)
  • Plugin Author Gregor Capuder

    (@capuderg)

    Hi @dchesbro,

    thank you for the update.

    Just to be sure, which code change did you implement?

    There are a few code changes suggested in the GitHub issue you linked. I want to make sure someone else with this issue can do the same as you did.

    Thank you and have a nice day!

    Plugin Author Gregor Capuder

    (@capuderg)

    Hi,

    I’ve found another GH issue that is referencing the same error (stripe’s PHP library): https://github.com/stripe/stripe-php/issues/918

    They are “narrowing” down the cURL to be a CentOS server related. I’ve seen @bay2125 mentioning that his server is CentOS based… Can others also confirm, that they are hosting on CentOS?

    Take care!

    Thread Starter dchesbro

    (@dchesbro)

    @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.

    Thread Starter dchesbro

    (@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.

    Try POST SMTP. It worked for me.

    Turns out the server rollback to cURL 7.69.1 did nothing. Still getting the same error. Only turning the keep-alive off in XMLRPC is allowing cURL to work.

    Plugin Author Gregor Capuder

    (@capuderg)

    @dchesbro, could you please let me know, what the other plugin was that stared to fail when you made the code change?

    @bay2125 thank you for this update. Maybe this config will help someone else as well.

    Thanks and take care!

    Partially fixed : I’ve fallen into the same problem, and found a quick fix for those who have access to their server configs, and don’t need the PHP CURL extension for their sites.

    I have upgraded to php 7.3, then deactivated the php73-php-curl extension. now the plugin work fine.

    I wish this will help.

    @capuderg

    Add my name to the list. I’ve had 3 clients now that I’ve changed over to Post SMTP because the plugin started throwing the cURL error on April 17th. This is on 2 different servers. One is a GoDaddy VPS and the other is a GoDaddy Reseller VPS. I’ve tried updating all the PHP extensions on the servers and no luck. Post SMTP works fine though.

    • This reply was modified 4 years, 10 months ago by Insight Dezign. Reason: spelling
    Thread Starter dchesbro

    (@dchesbro)

    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, 10 months ago by dchesbro.
    • This reply was modified 4 years, 10 months ago by dchesbro.
    • This reply was modified 4 years, 10 months ago by dchesbro.

    I am also having this issue. For the moment, I’m running through my host’s SMTP but I hate that warning messages are added to my emails since they’re not running through gmail servers.

    My host has confirmed that I am running cURL 7.19.7 (so not the updated version mentioned above that seemed to be causing faults).

    They disabled my keep-alive. Didn’t help.

    I’m at a loss and have no idea where to turn now.

    Thread Starter dchesbro

    (@dchesbro)

    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.

    WP Mail SMTP support is now unresponsive to my emails, even though I am a paying customer.

    Tom

    Plugin Author Gregor Capuder

    (@capuderg)

    Hi @dchesbro,

    you are correct, the v2.0.0 did not contain the fix for this issue, because we still don’t know what the actual cause is, so we could fix it.

    @egs1 you said you are using the “other SMTP” mailer and are getting the same exact error: “cURL error 2: easy handle already used in multi handle”? Or is it a different cURL error?

    I still can’t replicate this issue on my test servers and there is no new info on pages that I monitor…

    Take care!

    Thread Starter dchesbro

    (@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).

Viewing 15 replies - 16 through 30 (of 44 total)
  • The topic ‘cURL error 2: easy handle already used in multi handle’ is closed to new replies.