WP Toolkit: Broken Instance

Overview

Scanning for WordPress instances within the WP 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 WP 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 Cause of your Broken Instance

1. Login to Plesk via the Conetix Control Panel.
2. Click on WordPress on the left-hand side
   
3. In this menu you can see your broken instance, usually indicated by the WP Toolkit showing no information or tools and also by the “INSTANCE BROKEN” warning.
   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.
   You can find the location of the broken installation by following the next set of steps.

Fixing your Broken Instance

1. Click File Manager on the WPToolkit broken instance to be taken directly to the directory.
   
   In the example above; we’ve been taken to a directory that contains a full copy of the site.
   
2. Navigate up one directory by clicking the Green Arrow
   
3. In the directory you’ve been taken to, select the tick box to the left of the offending folder and click Remove.
   
4. You will need to confim the removed of the Folder and if you want the folder to be moved to the Recycle Bin or deleted from the server/hosting.
   As the folder is no longer needed tick to skip the recycling Bin then click Yes,remove
   
   
5. Once removed, navigate back to the WordPress section of the Plesk Panel:
   
6. Click the options button indicated by the three stacked dots. Then click Detach.
   
7. You will be prompted by Plesk to confirm the detachment, click Detach
   
8. The Broken instance in the WP Toolkit has been removed
9. To find your working instance, you should now press scan.