Can you temporarily enable “Enable debugging mode” (on the Wordfence Options page, fairly near the bottom) and try a scan again, then post about the last 10 lines of what you see in the yellow “Scan detailed activity” box?
If nothing is in the box, there may be a javascript problem preventing the scan from even being requested properly. Usually you can see errors like this in the javascript console — if you haven’t used the javascript console before, here are some instructions:
How to open the javascript console
(Make sure to turn this back off after resolving the issue — it does slow down scans and take up more space in your database.)
There are also a few troubleshooting steps you can try, but I don’t think any are related to CloudFlare — but it may be possible that other differences between your sites/plugins/etc. are causing the trouble:
My scans aren’t starting
Thread Starter
Anonymous User 13711045
(@anonymized-13711045)
[Sep 23 10:38:15] Ajax request received to start scan.
[Sep 23 10:38:15] Entering start scan routine
[Sep 23 10:38:15] Got value from wf config maxExecutionTime:
[Sep 23 10:38:15] Got max_execution_time value from ini: 30
[Sep 23 10:38:15] getMaxExecutionTime() returning half ini value: 15
[Sep 23 10:38:16] Test result of scan start URL fetch: array ( ‘headers’ => array ( ‘date’ => ‘Wed, 23 Sep 2015 17:38:16 GMT’, ‘content-type’ => ‘text/html; charset=UTF-8’, ‘connection’ => ‘close’, ‘set-cookie’ => ‘nf_wp_session=cba10cc39b81187231c01c899b43879a%7C%7C1443031335%7C%7C1443031275; expires=Wed, 23-Sep-2015 18:02:15 GMT; path=/’, ‘x-cf-powered-by’ => ‘WP 1.3.18’, ‘x-pingback’ => ‘http://www.yourwesterndecor.com/xmlrpc.php’, ‘link’ => ‘; rel=shortlink’, ‘x-newrelic-app-data’ => ‘PxQAVVFXCQoTVVFbBwcCUlwTGhE1AwE2QgNWEVlbQFtcC2VOcAJHCwtYa04WAl9WHQYNA1laGgULX0JSCwgGEBJOCEwICAQCA0kJTwJVBVtWGhpQSkEKVwdcBAAGUwMCUgVVBFJQQU5WA1QRXWU=’, ‘vary’ => ‘Accept-Encoding,User-Agent’, ‘server’ => ‘cloudflare-nginx’, ‘cf-ray’ => ’22a805b2bccd099a-ORD’, ‘content-encoding’ => ‘gzip’, ), ‘body’ => ‘ <!–[if (gte
[Sep 23 10:38:16] Starting cron via proxy at URL http://noc1.wordfence.com/scanp/www.yourwesterndecor.com/wp-admin/admin-ajax.php?action=wordfence_doScan&isFork=0&cronKey=4202a779581d82df14edcbb5
[Sep 23 10:38:17] Scan process ended after forking.
If you have added any code in your .htaccess file to block wp-admin, you might need to disable that, or at least allow requests to admin-ajax.php through.
When getting stuck at that point, some people have had success turning on “Disable config caching” on the Wordfence Options page, but I’m not sure if that will help in your case.
Usually you can also disable “Start all scans remotely”, unless you needed to turn that on for another reason.
You might want to check on the other items in the “My scans aren’t starting” link above, too — and if you know where to find your site’s error log, there may be an error message that will help there.
Thread Starter
Anonymous User 13711045
(@anonymized-13711045)
I figured out the issue. It was something stupid on my part. Thanks for the help though!
I have the same problem. So thekendog, I am interested in what stupid thing you did.
