Scanning for WordPress instances within the WordPress Toolkit can sometimes result in a broken instance being detected over your working instance.
While there are many reasons for this, we will be covering the most common reason the for the WordPress Toolkit finding a broken instance of WordPress. This article aims to take you through how to troubleshoot these broken instances and repair them.
Finding the reason for your broken instance
- Log into your Plesk Panel directly or via your Conetix Control Panel
- You should now see multiple tabs at the top of the Plesk Panel. Click "WordPress"
- In this menu you can see your broken instance, usually indicated by the WordPress Toolkit showing no information or tools and also by the "INSTANCE BROKEN" warning on the top right.
Usually a broken instance can be attributed to a broken installation of WordPress or in most cases a second development copy is present in httpdocs as in our above screenshot. These files are preventing the WordPress Toolkit from finding your working copy of WordPress.
You can find the location of the broken installation by following the next set of steps.
Fixing your broken instance
- Click "Manage Files" on the WordPress Toolkit broken instance to be taken directly to the directory.
- Navigate up one directory by clicking the Green Arrow
- In the directory you've been taken to, select the tick box to the left of the offending folder
Once removed, navigate back to the "WordPress" section of the Plesk Panel
Click the options button indicated by the three lines above each other. Then click Detach.
You will be prompted by Plesk to confirm the detachment, click Yes
The Broken instance in the WordPress Toolkit has been removed
To find your working instance, you should now press scan.