Title: Scans Won&#8217;t Complete
Last modified: September 8, 2016

---

# Scans Won’t Complete

 *  Resolved [Hue Marketing](https://wordpress.org/support/users/hue-marketing/)
 * (@hue-marketing)
 * [9 years, 9 months ago](https://wordpress.org/support/topic/scans-wont-complete/)
 * Hi,
 * I’ve tried every solution posted in the forums and on the help topics but I’m
   not having any success. Adjusted the max time limits and checked memory usage.
   Checked I wasn’t blocking wp-admin folder with a .htaccess… Anything and everything
   I could find relating to scans not completing.
 * (FYI. the last time the scan ran completely was on the 2nd. It’s not been able
   to finished a scan since then).
 * I’ve also tried disabling the following scan options (all at the same time) and
   it still fails to complete.
    Skipping core scan Skipping theme scan Skipping 
   plugin scan Skipping malware scan Skipping unknown core file scan
 * I’ve even uninstalled the plugin and re-installed it to see if that made a difference.
   But unfortunately no luck so far. So I’ve reached the point where I need to ask
   for help. 😉
 * I’ve included the last few lines on the scan report (in debug mode) in case that
   helps. Any help in this matter would be greatly appreciated.
 * Many Thanks
    Steve
 * [Sep 08 13:50:04:1473317404.064176:4:info] getMaxExecutionTime() returning half
   ini value: 15
    [Sep 08 13:50:04:1473317404.063802:4:info] Got max_execution_time
   value from ini: 30 [Sep 08 13:50:04:1473317404.063415:4:info] Got value from 
   wf config maxExecutionTime: [Sep 08 13:50:04:1473317404.062792:4:info] Calling
   startScan(true) [Sep 08 13:50:03:1473317403.651690:4:info] Entered fork() [Sep
   08 13:50:03:1473317403.651270:4:info] Calling fork() from wordfenceHash::processFile
   with maxExecTime: 15

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

 *  Thread Starter [Hue Marketing](https://wordpress.org/support/users/hue-marketing/)
 * (@hue-marketing)
 * [9 years, 9 months ago](https://wordpress.org/support/topic/scans-wont-complete/#post-8162767)
 * Updated to 6.1.16 and still unable to complete a scan. 🙁
 * There seems to be a coloration between the scans and the site throwing out random
   ERROR 502 – BAD GATEWAY pages.
 * Unfortunately this site is hosted on Bluehost and when I contacted support about
   it they were less than helpful.
 * Currently I have had to disable the automatic scans as a temporary stop-gap and
   hope to hear something soon. 😉
 * Many thanks
    Steve
    -  This reply was modified 9 years, 9 months ago by [Hue Marketing](https://wordpress.org/support/users/hue-marketing/).
 *  Thread Starter [Hue Marketing](https://wordpress.org/support/users/hue-marketing/)
 * (@hue-marketing)
 * [9 years, 9 months ago](https://wordpress.org/support/topic/scans-wont-complete/#post-8163350)
 * OK Guess I had not tried **everything **after all. 😉
 * SOLUTION
 * Changed the max execution time in the php.ini
 * max_execution_time = 30 **and change the value to 60.**

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

The topic ‘Scans Won’t Complete’ 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/)

## Tags

 * [incomplete](https://wordpress.org/support/topic-tag/incomplete/)
 * [scan](https://wordpress.org/support/topic-tag/scan/)
 * [solved](https://wordpress.org/support/topic-tag/solved/)

 * 2 replies
 * 1 participant
 * Last reply from: [Hue Marketing](https://wordpress.org/support/users/hue-marketing/)
 * Last activity: [9 years, 9 months ago](https://wordpress.org/support/topic/scans-wont-complete/#post-8163350)
 * Status: resolved