• Resolved wilhud

    (@wilhud)


    I am using free version of the plugin on our website and encountered an odd error. We use the Gmail OAuth 2 connection for sending mail from the site and it was working good up until around July 20th. Emails stopped sending from the site. I tried going into the plugin settings and the page just kept timing out. I also tried going to the test email page to try and send a test mail to myself but that page was timing out as well. Most other screens were working fine, it just seemed to be anything that was dealing with the Google API was causing the timeout issues.

    After trying a lot of different solutions to try and resolve the issue, this is what finally worked, in case anyone else runs into the issue. What I had to do was go into the Misc tab and scroll to the very bottom of the screen. I had to check the option to “Remove ALL WP Mail SMTP data upon plugin deletion.” and then uninstall the plugin. Once uninstalled and the data was deleted, I was then able to re-install the plugin and re-configure my Google API connection with all the same settings from before. After that, everything seems to be working fine again.

    Not sure why the screen was timing out with whatever that Curl 7 error was, but it made it more difficult to resolve the issue, since I couldn’t get any access to the settings. Not really sure what caused it, but that’s how I was able to fix it. Just figured I would share, in case someone else runs into the same problem.

    The full error message was…
    curl error 7: Failed to connect to oauth2.googleapis.com port 443: Connection timed out (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://oauth2.googleapis.com/token

    Wil

    • This topic was modified 4 months, 3 weeks ago by wilhud.
Viewing 1 replies (of 1 total)
  • Plugin Support Shawon Chowdhury

    (@shawon001)

    Hi @wilhud ,

    Thanks for reaching out.

    I am glad that it’s been resolved. However, it is possible that the issue may have been unrelated. Please monitor the situation and kindly provide additional details, such as screenshots and relevant debug logs, the next time the issue occurs. This will help us investigate the matter more effectively.

    Thanks 🙂

Viewing 1 replies (of 1 total)

You must be logged in to reply to this topic.