Hello,
I am sorry to hear about this issue. It might be difficult to resolve if you are not used to technical issues, but unfortunately there isn’t much you can do about this; the plugin is already very optimized, and I am afraid it’s not the number of posts which cause the issue neither (that the server might be exhausted after some time analyzing).
Did you have a look at this?
https://meowapps.com/media-cleaner-debug-issues/#Timeout_Code_524
I hope it helps 🙂
Thanks for your response. I’ve modified the settings of Media Cleaner based on the link you provided. I also increased my memory allocation in wp-config.php to 2048MB. In the error logs, this poppped up before I made the changes which is why I upped the MB to 2048. PHP Fatal error: Allowed memory size of 201326592 bytes exhausted (tried to allocate 20480 bytes) in .../wp-includes/wp-db.php on line 1972
Unfortunately, it’s still getting stuck at the 67th post with the same Gateway errors. Any ideas on what could be happening? Do I just need to continue upping the allocation in wp-config.php?
You can try to allow more and more memory, but 2048MB is huge already. I am sure something else is going on. Maybe you have too many plugins, and other plugins are doing something as well? I am not sure, this kind of issue is very difficult to debug, unfortunately.
It seems like it’s breaking in WordPress itself, to run a certain query, not sure if it’s a query from Media Cleaner or another one (Media Cleaner triggers other plugins to render the data, like Page Builders and so on).
