Title: Scan Stage Failed
Last modified: August 4, 2026

---

# Scan Stage Failed

 *  Resolved [sierracorp](https://wordpress.org/support/users/sierracorp/)
 * (@sierracorp)
 * [4 days, 4 hours ago](https://wordpress.org/support/topic/scan-stage-failed-38/)
 * We have an issue with one of our sites we get – Scan Stage Failed – A scan stage
   has failed to start. This is often because the site either cannot make outbound
   requests or is blocked from connecting to itself. Wordfence will make up to 2
   attempts to resume each failed scan stage. This scan may recover if one of these
   attempts is successful. Click here for steps you can try.
 * Wordfence installs successfully, the Web Application Firewall loads correctly,
   and Wordfence Diagnostics reports a healthy installation. However, every attempt
   to start a scan fails almost immediately with the message:
 * “A scan stage has failed to start. This is often because the site either cannot
   make outbound requests or is blocked from connecting to itself.”
 * To rule out a corrupted installation, we performed a complete removal and reinstallation
   of Wordfence. During this process we:
 * Removed the Wordfence plugin and Web Application Firewall.
   Removed all Wordfence
   database tables.Verified the WordPress database no longer contained any Wordfence
   tables or configuration entries.Removed the remaining Wordfence-related entries
   from the wp_options table.Verified there were no remaining Wordfence files or
   configuration left behind.Installed a fresh copy of Wordfence and verified that
   the firewall is loading successfully
 * On the same server we have other websites and we have no issues with standard
   default settings.
 * Any suggestions?
 * The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fscan-stage-failed-38%2F%3Foutput_format%3Dmd&locale=en_US)
   to see the link]_

Viewing 1 replies (of 1 total)

 *  Thread Starter [sierracorp](https://wordpress.org/support/users/sierracorp/)
 * (@sierracorp)
 * [3 days, 6 hours ago](https://wordpress.org/support/topic/scan-stage-failed-38/#post-18984482)
 * We found the issue. **WP Ghost Lite** was causing the conflict.  It seems something
   to do with secondary path to WP admin. Deactivating it will fix the issue. 
   Note:
   Once deactivate the custom URL no longer works. You will need to use the default.

Viewing 1 replies (of 1 total)

You must be [logged in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fscan-stage-failed-38%2F%3Foutput_format%3Dmd&locale=en_US)
to reply to this topic.

 * ![](https://ps.w.org/wordfence/assets/icon.svg?rev=2070865)
 * [Wordfence Security - Firewall, Malware Scan, and Login Security](https://wordpress.org/plugins/wordfence/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/wordfence/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/wordfence/)
 * [Active Topics](https://wordpress.org/support/plugin/wordfence/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/wordfence/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/wordfence/reviews/)

 * 1 reply
 * 1 participant
 * Last reply from: [sierracorp](https://wordpress.org/support/users/sierracorp/)
 * Last activity: [3 days, 6 hours ago](https://wordpress.org/support/topic/scan-stage-failed-38/#post-18984482)
 * Status: resolved