dimsal

Thank you for the file, this fixed it.

OK, so what do I do while you’re working on the new version?

I have NinjaFirewall installed, could any of its policies restrict this? But they were both working together before without any issues.

I think the only other explanation is a conflict with another plugin.

In Developer tools/Network I can see 25 calls to admin-ajax.php made but they are all have 200 response code. After 25th it stops.

Yes, admin-ajax returns ‘0’ and 200 response code.

Sorry to report but this issue is back. I’m getting this error:

“The scanning process doesn’t seem to be able to start. If your website is password-protected using HTTP basic authentication, you can enter your username and password in the “Settings > Advanced Settings” section.”

It appears after hanging on Step 1/14.

I’m on PHP 7.4, NinjaScanner version is 3.0.2. Debug log file is empty. Fork change doesn’t do any good. Any suggestion on how to troubleshoot it?

Thank you.

After reinstalling the latest 3.0.2 version it’s back to normal. It scans just fine. Must have been a broken file or something.

I already did. The debug log is empty.

So you may want to roll this back to 3.0.1 which is working fine with PHP 7.4 but new version 3.0.2 is hanging at step 4 or 5 “building theme/plugin list”.
Sorry about that.

I’m sorry for confusing you, I stay corrected, my PHP version indeed is 7.2 not 7.4.

Yes, with this new scan.php file the scanning is back to normal. Confirmed.

Thank you.

When I try to run the scan it shows me this error and stops:

Fatal error: NinjaScanner files integrity check: Decoded hashes seem corrupted. Aborting.

I’m getting this error multiple times:

PHP Warning: chmod(): Operation not permitted in /var/www/mydomain.com/htdocs/wp-admin/includes/class-wp-filesystem-direct.php on line 173

I’m experiencing the same issue as original poster. Started to happen after recent update to 3.0.1. I was working fine before with 2.0.10. No JS errors. I do have NinjaFirewall installed but it was working fine with it before so it couldn’t be the reason. Had to rollback to ver 2.0.10 to make it work again. I’m using PHP 7.4.

Thank you Gaby, just filed a bug report at provided link.