Forum Replies Created

Viewing 5 replies - 1 through 5 (of 5 total)
  • I think unfortunately you may have lumped our two posts together in the same response. My hosting provider is WPEngine. Although they assisted in providing logging for the issue the source has nothing to do with another plugin or theme. 100% the source of the issue is WP 5.5 running in the 7.4 PHP. WHen the plugin is installed and running in a WP environment that has those conditions it will spin to a timeout 502. All indications on the server point to a memory leak. The plugin and application utilize all available resources on the managed shared host. As such not only can WP Engine not provide any server tweaks to allow for the application to function but they will terminate the application and eventually request the plugin to be removed in order to prevent resource overloads on their shared managed environment.

    Indicating a plugin conflict only bears fruit if in fact conflict is a possibility. To illustrate that fact We have a bare install of WordPress – https://testmail.wpengine.com/. There are no plugins activated on this install other than WP Mail SMTP. There are no themes installed other than 2020, 2019 and 2017 which are the default WP installs. WP Mail SMTP is presently set to use office 365 as a Other SMTP the SMTP host but others including MailGun and SendGrid are failing as well. The only one that seems to work is the Default or None setting. We do not have accounts for SendinBlue, Pepipost or SMTP.com to test but we have tested Amazon SES.

    I am happy to submit a ticket and provide you direct admin access to this install so you can see the issues related to an essentially bare metal install of the plugin.

    Thanks in advance

    I am on with WPEngine as we speak. They rolled my core back to 5.5 and my PHP back to 7.3 and everything fired as it is supposed to. When I pasted your response they indicated that sounded as if there was a memory leak in the plugin. In shared managed hosting they would not want to max on the FD_SETSIZE for fear of overloading the resource calls on the server. But the point being the rollback worked so there is something amiss with 7.4 and 5.5

    Yes Indeed the only error that exists in the log is the one I shared earlier. We host at WPEngine and I have it replicated on three installs and the common factor on all is the update to 5.5. I have all themes and other plugins disabled and it still fails. We use the free version not the pro so we do not see the error log from the plugin. We have worked with WPE support. Here is a cut and paste of their response.

    “Gotcha, unfortunately we do not have any other information besides this data. Usually if a 502 is produced by a plugin, it should produce an error in the log however we’re not seeing that on our side. The requests seem to be going long enough for our automatic process killer to stop it (happens after 60 seconds)”

    Indeed. We are having the exact same issue. The plugin stopped sending emails from our Woocommerce installation one day ago after performing the WP core 5.5 update. The SMTP we are using is Office 365 but have tested it to failure with other services. I host at WPEngine and have an nginx error log relative to Uncaught Error: Class ‘WPMailSMTP\\Core’ not found and it provides the line of code wp-mail-smtp.php on line 77

    Thread Starter ejbrewer

    (@ejbrewer)

    HMMM. I did not provide the link to the site we are using. Presently there is no theme assigned. Its default out of the box WordPress currently. We have not applied themes as yet. When is your chat available to discuss?

Viewing 5 replies - 1 through 5 (of 5 total)