Title: Scan not running
Last modified: August 21, 2016

---

# Scan not running

 *  Resolved [webkiwi](https://wordpress.org/support/users/webkiwi/)
 * (@webkiwi)
 * [11 years, 11 months ago](https://wordpress.org/support/topic/scan-not-running/)
 * Select to run scan, and it says it is Requesting New Scan, then after about 5
   seconds – times out.
    Have read the default page on the wordfence site about 
   cache, htaccess, don’t have any blocking in place on my site, yet it won’t run.
   Where else to check, what could be causing it to not run?
 * [https://wordpress.org/plugins/wordfence/](https://wordpress.org/plugins/wordfence/)

Viewing 2 replies - 1 through 2 (of 2 total)

 *  Thread Starter [webkiwi](https://wordpress.org/support/users/webkiwi/)
 * (@webkiwi)
 * [11 years, 11 months ago](https://wordpress.org/support/topic/scan-not-running/#post-5005654)
 * Never mind, the hosting company had messed with my htaccess file, putting a redirect
   in it!
 *  Thread Starter [webkiwi](https://wordpress.org/support/users/webkiwi/)
 * (@webkiwi)
 * [11 years, 11 months ago](https://wordpress.org/support/topic/scan-not-running/#post-5005655)
 * Resolved, sorry about that.

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘Scan not running’ is closed to new replies.

 * ![](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/)

 * 2 replies
 * 1 participant
 * Last reply from: [webkiwi](https://wordpress.org/support/users/webkiwi/)
 * Last activity: [11 years, 11 months ago](https://wordpress.org/support/topic/scan-not-running/#post-5005655)
 * Status: resolved