• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

WP Toolkit Times Out

GGCoffee

New Pleskian
‪CentOS 6.10 (Final)‬ | Plesk Onyx Version 17.8.11 Update #35 | WordPress Toolkit Version: 3.5.3-1312

I'm having the wordpress toolkit timeout when i click it from the sidebar. If I uninstall it and reinstall it without it having any sites scanned it works. Once I have it scan for all WP instances (~300) then it starts timing out again (503). Is anyone else having this issue? It seems to have started in the last month or so.

Performing plugin updates is so useful with the toolkit, hoping I can get this resolved.
 
Last edited:
I think that researching this unusual situation requires access to your server. Therefore, I recommend that you contact Plesk technical support. This will be the most effective way to solve the problem.
 
If the scan times out, one ore more of the Wordpress websites are infected with a malware. You can check the server's process list to see ongoing WP toolkit update/scan processes which reside in the list forever and normally use 99.9% of cpu time. By the domain names mentioned in the process commands, you may be able to quickly identify the infected sites. Else probably only a step-by-step check of the sites will help. You will normally find unusual modifications in wp-config.php or files with cryptic names like
dg3980acioxy.php
in the document root directory of infected installations. For reasons that I have never figured out, WP toolkit cannot scan such installations and does not end the scan process either.
 
Due to the holidays I was out of the office till today. I have checked up on CPU usage times and nothing appears out of the ordinary on my server lucky.

To clarify the WP toolkit instance scan is not having an issue detecting all the sites (330+). After scanning for all instances is completed, going to the wordpress toolkit menu on the left sidetoolbar directs me to the following url

https://SERVERUL:8443/modules/wp-toolkit/index.php/index/index?context=extNavButton_wp-toolkit_1

This is the page that never loads and times out.

I can manually navigate to the plugin list page (https://SERVERUL:8443/modules/wp-toolkit/index.php/index/plugins-list) directly and while it takes a while to fully load I have not received a timeout so far. I can perform the necessary plugin updates using this workaround for now.

I have also encountered a noticeable increase in URL target lookup time when using the WP Toolkit instance clone option as well.
 
Back
Top