Resolved Wordpress Toolkit "scan" feature is now broken...

[Aleksey Filatev]

Thank you for the update. If .wp-toolkit-ignore file doesn't exists in WordPress installation directory and scanning doesn't locate such instance, it worth deeper investigation. The most fast way to find the root cause on your server would be to contact Plesk support. Is this an option for you?

 

[Maarten.]

Yes, already did this. Plesk Support Team asked the development team to check up on the issue as nothing is pointing to a possible cause.

 

[Maarten.]

The scan issue as root has been solved. The problem was a few files with invalid permissions.

 

[Aleksey Filatev]

I glad to hear that, thank you! Do not hesitate to let us know in case of any issues with the toolkit.

 

[pleskuser67553]

I'm on the latest update and I'm still experiencing this as an admin. One server, two WordPress sites on different subscriptions. WPT detects one but not the other.

Tried:

• deleting .wp-toolkit-ignore from the root of the problem installation (no recycle bin)
• un/reinstalling WP Toolkit extension
• checking for instances with plesk ext wp-toolkit --list in SSH Terminal as root - it finds none
• plesk repair --fs -y via the GUI - no issues detected

OS: CentOS Linux 7.9.2009 (Core)
Product: Plesk Obsidian, Version 18.0.42 Update #1
WordPress Toolkit version: 5.10.1-6111

 

[Maarten.]

It could be the same issue I was having.

Try to manually fix the files/dirs like this as "plesk repair fs" doesn't always work:

# find /var/www/vhosts/domain/httpdocs/* -type d -exec chmod 0755 {} \;
# find /var/www/vhosts/domain/httpdocs/$* -type f -exec chmod 0644 {} \;

 

[pleskuser67553]

That sorted it, thanks @maartenv

 

[codeminer]

getting the same issue? only one wordpress installation is being detected , i tried fixing file permission from tools section too no .wp-toolkit-ignore too? is there anything else to check? thank you

 

[vbelich]

getting the same issue? only one wordpress installation is being detected , i tried fixing file permission from tools section too no .wp-toolkit-ignore too? is there anything else to check? thank you

Hi, please check following things:
1. Domain has hosting
2. WordPress Toolkit is allowed for this subscription (Service Plans -> Service plan used for this subscription -> Tab "Permissions" -> Checkbox "Access to WordPress Toolkit", if subscription is not synchronized with service plan, then you need to check this in subsription page -> Customize -> Permissions)
3. Path to this WordPress site does not starts with "{home path}/.trash" (e.g. /var/www/vhosts/example.tld/.trash/my-wordpress)
4. The file .wp-toolkit-ignore does not exist (you already checked)
5. Permissions are good enough, e.g. system user can read and execute php files and he also can read directories, you can temporary set 0644 for files and 0755 for directories and then in WordPress Toolkit apply the security measure to fix permissions, it will change them to more secure)
6. The directories "wp-content" and "wp-includes" are located in the root directory of the WordPress site
7. The file "wp-config.php" is located in the root directory of the WordPress site, or it is located on a level above
8. Check the limit of allowed WordPress sites per subscription (Service plans -> Service plan used for this subscription -> Resources -> Input "WordPress Websites" or checkbox "Unlmited")

As the last investigation step, do following:
1. Enable additional logging in panel.ini:

[log]
filter.priority = 7
show.util_exec_io = 1

2. Start "Scan" in WordPress Toolkit and wait for finish
3. Open /var/log/plesk/panel.log and find following lines:

DEBUG [util_exec] [e65cd4995e82f4e28ac0f05bca5c487a-0] Starting: vhostmng-find, stdin: {"where":{"basedir":"\/var\/www\/vhosts\/example.tld","subdirs":["\/"],"depth":127,"follow_symlinks":false,"scope":["name"]},"run_as":{"user":"user_tfewrtzbgn","group":"psacln"},"what":["wp-includes","wp-content","wp-config.php",".wp-toolkit-ignore"],"options":{"match_full":true,"match_case":true},"output":{"format":"raw"}}
...
DEBUG [util_exec] [e65cd4995e82f4e28ac0f05bca5c487a-0] Finished in 0.24903s, Error code: 0, stdout: /var/www/vhosts/example.tld/jkbvis/wp_agjmf/wp-content
/var/www/vhosts/example.tld/jkbvis/wp_agjmf/wp-includes
/var/www/vhosts/example.tld/jkbvis/wp_agjmf/wp-config.php
/var/www/vhosts/example.tld/jkbvis/wp-content
/var/www/vhosts/example.tld/jkbvis/wp-includes
/var/www/vhosts/example.tld/jkbvis/wp-config.php
, stderr:

You should see the list of files as in the second DEBUG message. If you don't see something like this, or if the "wp-content" + "wp-includes" + "wp-config.php" is not visible in this list, but in fact they are visible in file manager / "ls" output, then maybe they are symlinks or something like this. Need to check that case further

 

[codeminer]

Hi, please check following things:
1. Domain has hosting
2. WordPress Toolkit is allowed for this subscription (Service Plans -> Service plan used for this subscription -> Tab "Permissions" -> Checkbox "Access to WordPress Toolkit", if subscription is not synchronized with service plan, then you need to check this in subsription page -> Customize -> Permissions)
3. Path to this WordPress site does not starts with "{home path}/.trash" (e.g. /var/www/vhosts/example.tld/.trash/my-wordpress)
4. The file .wp-toolkit-ignore does not exist (you already checked)
5. Permissions are good enough, e.g. system user can read and execute php files and he also can read directories, you can temporary set 0644 for files and 0755 for directories and then in WordPress Toolkit apply the security measure to fix permissions, it will change them to more secure)
6. The directories "wp-content" and "wp-includes" are located in the root directory of the WordPress site
7. The file "wp-config.php" is located in the root directory of the WordPress site, or it is located on a level above
8. Check the limit of allowed WordPress sites per subscription (Service plans -> Service plan used for this subscription -> Resources -> Input "WordPress Websites" or checkbox "Unlmited")

As the last investigation step, do following:
1. Enable additional logging in panel.ini:

[log]
filter.priority = 7
show.util_exec_io = 1

2. Start "Scan" in WordPress Toolkit and wait for finish
3. Open /var/log/plesk/panel.log and find following lines:

DEBUG [util_exec] [e65cd4995e82f4e28ac0f05bca5c487a-0] Starting: vhostmng-find, stdin: {"where":{"basedir":"\/var\/www\/vhosts\/example.tld","subdirs":["\/"],"depth":127,"follow_symlinks":false,"scope":["name"]},"run_as":{"user":"user_tfewrtzbgn","group":"psacln"},"what":["wp-includes","wp-content","wp-config.php",".wp-toolkit-ignore"],"options":{"match_full":true,"match_case":true},"output":{"format":"raw"}}
...
DEBUG [util_exec] [e65cd4995e82f4e28ac0f05bca5c487a-0] Finished in 0.24903s, Error code: 0, stdout: /var/www/vhosts/example.tld/jkbvis/wp_agjmf/wp-content
/var/www/vhosts/example.tld/jkbvis/wp_agjmf/wp-includes
/var/www/vhosts/example.tld/jkbvis/wp_agjmf/wp-config.php
/var/www/vhosts/example.tld/jkbvis/wp-content
/var/www/vhosts/example.tld/jkbvis/wp-includes
/var/www/vhosts/example.tld/jkbvis/wp-config.php
, stderr:

You should see the list of files as in the second DEBUG message. If you don't see something like this, or if the "wp-content" + "wp-includes" + "wp-config.php" is not visible in this list, but in fact they are visible in file manager / "ls" output, then maybe they are symlinks or something like this. Need to check that case further

WOW, I appreciate your time to reply, thank you so much. I'll try this and let you know