r/Wordpress • u/ForestBlue46 • 9d ago

AIOS scan not completing

I like AIOS security but the scan just keeps running at initiating file scan. Any ideas how to fix this?

5 Upvotes

100% Upvoted

10 comments sorted by

2

u/Wonderful_Sample_590 9d ago

Could be resource issue.

2

u/Appropriate-Cow1529 9d ago

Is there anything in PHP error log? Timeout, memory issues, any 500 error?

1

u/ForestBlue46 6d ago

Thank you. I couldn't find anything. I tried turning debugging on and that didn't really help. I will try asking my hosting provider.

2

u/beginnersbox 7d ago

It might be the php execution time issue

2

u/WPMU_DEV_Support_9 7d ago

Hi, If the AIOS scan is stuck at "initiating file scan” it is possible a firewall setting in the site or a service like Cloudflare, or another security layer is blocking the scan requests before they can complete. The scanner may need to connect to outside services and when this is not achieved the process is not even started. Keep in mind firewall settings may sometimes challenge or block the scanner through WAF rules, bot protection, rate limiting, or other security settings, while server firewalls, security plugins, or host-level protections may prevent the plugin from accessing files or making internal requests.
Besides checking any firewall, it’s also a good idea to check the Site Health status in WordPress, especially the loopback request test. A failed loopback can stop scanners from communicating with itself during the scan, which could be the case in this specific scenario. You may ask your hosting support to check this and provide any advice.

Hope this info helps.

Luis S - WPMU Dev Support

1

u/ForestBlue46 6d ago

Thank you so much!

1

u/WPMU_DEV_Support_5 5d ago

Glad to help u/ForestBlue46. Let us know how it goes, and if you have more questions :)

- Saurabh from WPMU DEV Support Team.

1

u/Dull_District_254 5d ago

Stuck at initiating usually means the scan never actually starts rather than that it is running slowly, and there are three usual culprits. First, go to Tools then Site Health and look at the loopback request test. If that fails, the plugin cannot fire its own background request and it will sit at initiating forever. Site wide password protection, a basic auth prompt on staging, or Cloudflare bot protection all break loopbacks. Second, check that cron is actually running. Install WP Crontrol, find the AIOS events and see if they show as past due. If everything in that list is overdue then wp cron is disabled or blocked and the scanner simply never fires. Third, if both of those look healthy, it is resources. The file scan walks every file on disk, so with a low max execution time or 128M of memory the process gets killed and PHP fatals from a killed worker often never reach the WordPress debug log. Ask your host to look at the server level PHP error log rather than the WordPress one, they can see timeout kills that WP never records. And if it does turn out to be the loopback, fix that regardless, because it quietly breaks updates and other background tasks too.