damien7

Sorry for the inconvenience this has caused you both. We will investigate this for you.

Thanks for your post. Unfortunately there is no easy way within AIOS UI to export and import the Blacklist to the permanent block list.

However, we completely agree about your concerns regarding .htaccess. We are currently reimplementing the blacklist so it no longer depends on .htaccess. It will use our PHP firewall instead of the .htaccess file. Which means your .htaccess won’t get populated with your blacklist IPs anymore and you can move to a host which doesn’t support .htaccess (e.g: an nginx web server).

Although I can’t give an exact timeline of when the switch will happen, I can say that the coding has been done for it and it’s going through our quality assurance process at the moment.

Hey pmmueller, thank you for the information you have provided. Are you able to confirm if you’re getting the same issue in the latest update which we issued last night?

In regards to the redirect to 127.0.0.1, your assessment is correct. Some features of AIOS do redirect to 127.0.0.1. “Enable Honeypot On Login Page” is one such setting.

Thank you for your help in this matter. We have just released a new version of AIOS are you able to confirm that this issue is still present?

Hi Milesbu, apologies for the inconvenience. Are you still having this issue? We have just released a new version, are you able to update to that or is this issue still preventing you?

Apologies for the delay. We have just released a new version. Are you able to confirm whether this has been fixed in that version?

If not, can you also let me know your PHP version.

Thank you for your help with resolving this issue. We have released a new version with this fix inside. I will resolve this thread, but please do let us know if the issue reoccurs.

You can reinstall AIOWPS. After you have installed it, I would advise you not to enable any of the settings and try logging out and back in and see if it works without any of AIOWPS’s settings enabled. If it does, I would then advise logging out and back in after enabling some settings — if it stops working, let us know which settings were enabled and we can investigate even further for you.

Hey, I’m glad to hear that the Unable to locate workspace is fixed. We have just released a new version. Does the new release also resolve the new issue you’re having?

Thanks. Seems to go through OK on my end.

Usually when a 403 is received in the plugin, it means a firewall rule has been triggered. Are you able to switch off the each firewall setting one by one to see if it resolves the issue? If it does, would you let me know which one was the issue? I can look into it further then.

Hello,

Apologies for the inconvenience this is causing. What version of the plugin are you using? Also are you able to give me the IP/IPs that you entered into the blacklist and I’ll see if I can recreate the issue on my end.

Hey, thanks for getting in touch. Automatic blocking is a good idea which we will look to implement in the future. However, at the moment blocking these requests can only be done manually.

I’m sure you’re already aware on how to do so manually, but just in case you’re not:

1. Go to WP Security > Firewall > 404 Detection tab.
2. Scroll to the 404 Events Log
3 Hover over the entry and select one of the blocking options.
4 Alternatively, you can select multiple entries and use the ‘Bulk Actions’ drop down to perform the blocking actions.