Can not see file system check report

Do you remember, were you previously running 15.09 or 15.08?

The only change from 15.09 to 15.09-2 was a bit of JavaScript. Can you tell me if there are any JavaScript errors when running a scan? You can press Command + Option + J (Mac) or Control + Shift + J (Windows/Linux) to pull up the js console in your browser.

From 15.08 to 15.09, there were a lot more changes. The two things I can think of that might hold up the results are the new file permission scanning or the building of the list of old core files (which can take a lot of time). I’m working on a way to make the latter more efficient in the next release, but in the meantime it will at least cache each old version as it is fetched, so if the results time out, you might be able to reload the page to have it work through the rest.

Do you have any errors in the server log?

I went ahead and released 15.09-3, which contains the performance improvements I mentioned regarding the building of the obsolete core file database. Can you give the new version a shot? If your server was struggling to build the list before, it should be good now.

If the scan results still aren’t working, though, please let me know if you’re getting any Javascript errors or if there is anything pertinent in your server logs.

Thanks for taking the time to help debug the plugin!

In seems to me the site checked is too big. There is error in log file:

2015/09/27 11:07:35 [error] 2699#0: *3934147 FastCGI sent in stderr: “PHP message: PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 71 bytes) in /var/www/web/www/wp-i$

Scanner uses more then 256MB memory only to scan files? Cool!!

Can you repair this behavior?

I was able to reduce the memory footprint a little bit in 15.09-4, particularly in cases where a lot of files have permissions other than the defined target.

Does this fix things for you?

If not, can you please deactivate and uninstall the plugin (through the WP plugins interface, which will remove the settings in addition to the files), then try installing a fresh copy?

After a reinstall, go to the scan settings, and enter “0” for the File Permissions (if you see the option), check “Skip Cache” (if you see the option), uncheck “Analyze Content”, and save. This combination is lightest on the server, so let’s start with that!

Then try a “Core Scan Only”. Did that work?

Then try a regular scan. Did that work?

Since Updating to 20.1.1 The scanner no longer works, I get :”The prescan was either unable to collect the official WordPress core checksums or was unable to access the file system.”
“The pre-scan could not complete.”
It was fine before the update.

I am running WordPress 4.5.2 this is on 6 sites so far.

Hi jschooper,

I apologize for the trouble! The “20” series has been completely rewritten to take advantage of more modern server environments. It allows the plugin to scan faster and provide more accurate results, but it also won’t run on as many environments.

The plugin does its best to check in advance of any scans to make sure that the server meets the minimum requirements, but that isn’t always possible.

The error you’re receiving is typically caused by one of two things:

1. If the problem is checksum-related, either the WordPress API does not maintain checksums for your particular version (which usually happens when hosting providers spin their own release), or the data was not able to be saved to the database.
2. If the checksums installed A-OK, then the problem is usually do to resource restrictions. Generating a list of files can be a bit demanding, and some hosts will kill a process that they deem destabilizing.

I’ll break down those errors in more detail in the next release, as well as see if there are any workarounds for problematic hosts like GoDaddy.

For anybody with a server unable to run the newer version, you can temporarily downgrade by uninstalling the new version and then installing the legacy version from this link:

https://blobfolio.com/repo/look-see-security-scanner-legacy.zip

The legacy version is no longer maintained, so please don’t use it indefinitely. ?? But it should be safe to use until an alternative security solution is located.

Hi jchooper,

Please give version 20.1.2 a shot. It fixes a locale compatibility issue that was preventing some installations from being able to obtain checksums from WordPress’ API.

PS Let me know if it works! Thank you!