Scan does not complete – not liteSpeed server

Hello,

Is there a specific file that it is getting stuck on? Telling Wordfence to ignore the file it is hanging on may allow the scan to complete.

Sounds like you’ve read this document. You may want to keep experimenting with the setting.

https://support.wordfence.com/support/solutions/articles/1000011129-my-scans-don-t-finish-what-can-i-do-

-Brian

Same here. I’m not on a Litespeed server, and after uninstalling and reinstalling Wordfence, working with my hosting company tech support, disabling mod_security and re-enabling, making every tweak I could find in Options to max_execution_time, memory, etc. I cannot get a scan to complete successfully.

It hangs anywhere between getting malicious URLs from your servers to “Analyzed XX files containing XX MB of data so far”—mostly on the latter.

I’ve got this plugin working on three other sites, and it is smooth sailing. Please advise; thank you.

Hi,

Are you completely removing Wordfence and all table data before reinstalling?

You can find instructions here: https://docs.wordfence.com/en/I%27d_like_to_reinstall_Wordfence_completely._How_do_I_do_that%3F

Are the other sites you have working on a similar server setup?

Thanks,
Brian

Thanks for the quick response.

Yes, I did the complete uninstall (twice) per those instructions.

One of the other sites is with the same hosting company (InMotion), but this site I’m having trouble with is the only VPS; both InMotion sites are running on Apache servers, though.

FYI, I did even try the .htaccess tweak for Litespeed servers just to troubleshoot, and that was a no-go as well.

Any insight into this, sir? Thank you.

Usually scans not completing comes down to running out of memory. We recommend 128GB. Do you have Live Traffic disabled? If not, you should turn it off.

https://docs.wordfence.com/en/Wordfence_system_requirements

And just to reiterate these settings…

https://support.wordfence.com/support/solutions/articles/1000011129-my-scans-don-t-finish-what-can-i-do-

-Brian

It was a memory issue with the VPS. Apparently, it was within 20-50MB of the account’s limit at most any given time.

I had the host up the limit temporarily so I could troubleshoot, and the scan completed. FINALLY. Ha.

Thanks again.

Awesome! Glad it’s working for you now and thanks for your patience troubleshooting the issue.

-Brian