@lonk Yeah I figured we had the same issue but apparently not, my bad. Didn't mean to hijack the thread earlier. haha. Mine was actually caused by v6.0 due to a breaking change in how SFTP works - by default for admins only, meaning any non-admin users are rejected out of the box. But I think yours was different as you filed it before v6.0.
Follow up from the customer: "The issue here turned out to be that in Wordpress, WP Rocket caching plugin was used. This plugin automatically starts to preload the cache of each page once something in the site has been updated. The preload itself causes some stress on the CPU and maybe some other processes. Turning off the plugin, the products were sent for less than 2 mins."
They are working with the WP Rocket team to find a workaround.
Jul 27 17:20:01 [Mon Jul 27 16:20:01.042734 2020] [php7:error] [pid 41] [client 172.18.0.1:48468] PHP Fatal error: Cannot redeclare authLdap_send_change_email() (previously declared in /app/data/wp-content/plugins/authLdap-2.4.2/authLdap.php:849) in /app/data/wp-content/plugins/authldap/authLdap.php on line 849, referer: https://my.removed/
This is the problem. I think the issue was because the LDAP plugin was updated by you (?). The fix is to remove wp-content/plugins/authldap directory using the File Browser (do not remove the authLdap-2.4.2 directory). Does that work?
I have the email partially working now: it can receive email and I can read it on thunderbird, but I haven't been able to successfully send one yet. Some of the logs say something about the domain being too new.
I'll try the wordpress built-in email for now and see how far I get
@girish I don’t know if that’s really accurate. I say that only because according to the WordPress server status page, it shows my memory set at 256M, but I don’t have that set anywhere in any files. And when I assumed it was matching the memory assigned to the whole app deployment, it was not excuse when it set it to 1 GB as a test, it still showed 256M.
Can you try with the latest redis-cache plugin or use the latest unmanaged WP package?
As far as I'm aware I was using the latest everything, but similarly to some of my other WordPress reports last night, the next time I did it out all worked fine (which doesn't help work out what the actual issue was, but nevermind)