aporter

Hi,

If your having an issue with the plugin then please open a support request, where one of our developers will be more than happy to help you.

As for admin menus being a mess, moving these around are all part of a project to improve the UI/UX of the plugin to make it modern and easier to use.

This is being done in stages so that long time users are not confused when things are suddenly moved to a new location.

This plugin does support captcha on the checkout page so if your having trouble setting that up, please open a support request so we can help.

Also if you let us know what features we are lacking, we would be more than happy to look into implementing them.

Best Wishes,

Ashley

• This reply was modified 1 year, 6 months ago by aporter.

Hi,

So the first attempt to login before they are blocked will be recorded, all attempts after that are instantly locked out and no event gets recorded.

The different attempts should be from different IP addresses and each address should automatically be blocked and appear in your locked IP address table.

Best Wishes,

Ashley

Hi all,

Very sorry about this.

Version 5.2.4 is now released which fixes this issue.

Best Wishes,

Ashley

Hi,

Yes correct them notices are not relevant to the problem.

For some reason the firewall is getting a silent error and not loading, which then causes a fatal when the plugin tries to use it.

Version 5.2.4 has just been released it fixes a different issue and removes the filter that is causing the above message.

So hopefully you can now install and use the plugin while we rework the firewall to prevent issues of this kind in future.

Let me know if theres any other issues.

Best Wishes,

Ashley

Hi,

Thanks for the report, we will look into this for you.

Will update you when I know more.

Best Wishes,

Ashley

Hi,

Version 5.2.3 now shows the correct IP.

Best Wishes,

Ashley

Hi,

Are there any other messages in your PHP Error log?

Best Wishes,

Ashley

Hi,

That message would indicate your being locked out by either the .htaccess file or PHP firewall.

You could disable the PHP firewall by adding the following constant to your wp-config.php:

define(‘AIOS_NO_FIREWALL’, true);

Best Wishes,

Ashley

Hi,

I believe we have tracked down the issue, a copy of the plugin with the fix is here:

https://gofile.io/d/FMt8GE

If the above copy does resolve the issue for you then for some reason on the sites where it doesn’t work the “aios/firewall-rules” folders did not exist in your uploads directory and that causes the firewall to fail to load.

In our test installs the folders do get created before the fatal error happens (so these may now exist for you).

Best Wishes,

Ashley

Hi,

You can use the following to disable all events from being recorded:

function aios_audit_log_record_event($record_event, $event_type, $details, $event_level, $username) {

return false;

}

add_filter(‘aios_audit_log_record_event’, ‘aios_audit_log_record_event’, 10, 5);

Please note that if you disable all events from being recorded some features of the plugin and future features will no longer work

For example the login lockdown feature will no longer work as no failed logins are being recorded.

Best Wishes,

Ashley

Hi @estalhun ,

More than happy to help, but please do open your own support requests for issues your having (I won’t respond here again not to spam the original poster whos issue has been resolved).

If you have the option “Instantly lockout invalid usernames” turned on then that is expected behaviour.

Best Wishes,

Ashley

Hi,

Ignore the above message, I believe we have tracked down the issue a copy of the plugin with the fix is here:

https://gofile.io/d/FMt8GE

If the above copy does resolve the issue for you then for some reason on the two sites where it doesn’t work the “aios/firewall-rules” folders did not exist in your uploads directory and that causes the firewall to fail to load.

In our test installs the folders do get created before the fatal error happens (so these may now exist for you).

Best Wishes,

Ashley

Hi,

We have had a look into this and it appears WP Staging has an “optimizer” feature that disables all other plugins when it runs for better performance.

But AIOS needs to be running for the salt feature to work, if AIOS doesn’t run then when ever other plugins need to access the salts they don’t get the correct values which breaks them.

We have confirmed that turning off the “optimizer” feature resolves the conflict.

Best Wishes,

Ashley

Hi,

You can just empty the table contents from phpmyadmin, but do not delete the table.

Before you remove all the rows from the table are you able to check what it’s been filled up with?

A few others have reported this and theirs are filled with failed login attempts.

Now you can either look into preventing them brute force attempts which will stop the logging.

Or if you don’t care about the attempts you can either ignore them and change the automatic cleanup time, or prevent them from logging at all.

By default logs older than 90 days are removed, you can change that time by adding this constant to your wp-config:

define(‘AIOWPSEC_PURGE_AUDIT_LOGS_AFTER_DAYS’, 10);

That will remove logs older than 10 days.

Or if you don’t want to log some or all events you can use the following filter:

‘aios_audit_log_record_event’

Best Wishes,

Ashley

Hi,

Thanks for providing all this information it was very useful.

I believe we have narrowed down the issue and we are currently testing a fix.

Can you check if in your uploads folder (wp-content/uploads) you have the “aios” folder and inside that “firewall-rules”

They may have got created for you when you got the fatal error.

If not can you create both of them so the full path would be:

“wp-content/uploads/aios/firewall-rules”

With them folders there update 5.2.2 should work for you.

I can also send a pre release copy of the plugin for you when it’s ready.

Best Wishes,

Ashley