Replies: 0
Hi,
I’ve upgraded v2.3.1 to v2.4 on two websites (hosted on same VPS). One site is setup to use mailer method Gmail, and the update was smooth and error free.
The second site (with v2.3.1) uses mailer method ‘Other SMTP’ and has SMTP password set in wp-config.php via ‘define WPMS_SMTP_PASS’. Upon update to v2.4 it immediately crashes and produces a 502 Bad Gateway error. The error log reads the following (domain & IP omitted):
2020/09/30 10:33:47 [error] 898#898: *7 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: xxx.xxx.xx.xxx, server: http://www.example.com, request: “GET /wp-admin/plugins.php?action=activate&plugin=wp-mail-smtp%2Fwp_mail_smtp.php&plugin_status=all&paged=1&s&_wpnonce=cf4f611b05 HTTP/2.0”, upstream: “fastcgi://127.0.0.1:9000”, host: “www.example.com”, referrer: “https://www.example.com/wp-admin/plugins.php”
2020/09/30 10:33:55 [error] 898#898: *7 FastCGI sent in stderr: “PHP message: PHP Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 62520044528 bytes) in /var/www/example.com/html/wp-content/plugins/wp-mail-smtp/wp-mail-smtp.php on line 775237173” while reading response header from upstream, client: xxx.xxx.xx.xxx, server: http://www.example.com, request: “GET /wp-admin/plugins.php?action=activate&plugin=wp-mail-smtp%2Fwp_mail_smtp.php&plugin_status=all&paged=1&s&_wpnonce=cf4f611b05 HTTP/2.0”, upstream: “fastcgi://127.0.0.1:9000”, host: “www.example.com”, referrer: “https://www.example.com/wp-admin/plugins.php”
I cannot access the site at all at this stage and had to recover from a snapshot backup. I noticed that if I comment out the password settings in wp-config.php and then retry to update 2.3.1 > 2.4, this time WordPress (v5.5) will immediately deactivate the plugin and report that it caused a fatal error, with the plugin deactivated I can continue to access the site.
Again, no such errors on the other site with this plugin, that was setup with the gmail method.