Resolved WP Toolkit - Bulk Remove Error

[PrimeSites]

Hi Folks,

Every so often I need to completely clear out all existing WP installations on one of our back-up servers. When I'm in the WordPress Toolkit interface, then multi-select just a few installations and then hit the remove button, I get the following error:

Request to backend API failed with error: Request failed with status code 500

Removing installations individually always succeeds, but trying to remove any number of multiple-selected installations consistently fails with this error.

Are you perhaps able to shed any light on the reason behind this?

Thanks

OS: ‪Ubuntu 20.04.2 LTS‬
Product: Plesk Obsidian 18.0.33

 

[Aleksey Filatev]

An actual error could be found in /var/log/plesk/panel/log. You can check ERR entries, but if this information will not be enough, there is a way to increase the logging level to debug and check details and error stack trace. You can post logs here (but do not forget to anonymise any sensitive data) or submit a support request.

 

[PrimeSites]

Thanks, Aleksey.

The verbose log level is what caught us out. We enabled that by following the below instructions:

How to enable/disable Plesk debug mode

Applicable to: Plesk for Linux Plesk for Windows Question How to enable/disable debug logging in Plesk? Answer The debug mode can be enabled either via the Plesk Panel.ini Editor extension in Pl...

support.plesk.com

​

It turned out that is was a memory error, which we got around by following the advice in this article:

Operations in Plesk fail: Allowed memory size of X bytes exhausted (tried to allocate Y bytes)

Applicable to: Plesk for Linux Plesk for Windows Symptoms Any of the following operations in Plesk: Accessing the Plesk interface Accessing Domains > example.com > File Manager > any...

support.plesk.com

​

That got around the memory error, but next we started hitting a 524 timeout issue, which turned out to be related to Cloudflare closing the connection after 100 seconds:

Community Tip - Fixing Error 524: A timeout occurred

Error Try the suggestions in this Community Tip to help you fix Error 524: A timeout occurred. Background Error 524 error indicates that Cloudflare made a successful TCP connection to the origin web server, but the origin did not reply with an HTTP response before the connection timed out...

community.cloudflare.com

​

We temporarily bypassed Cloudflare for the domain via which we accessed the Plesk back-end and that got us around that issue.

All sorted now. Thanks again for the tip about the logging verbosity level.

PS: We've subsequently reverted the verbosity level changes in the panel.ini file.

 

[Aleksey Filatev]

Thank you for sorting out and summarizing all these steps that helped you! This could be extremely helpful for other Plesk users in similar situations.