Few questions about Simple Firewall and multisite
-
Hi Paul,
I never thought I’d move away from Wordfence, but I read a lot about Simple Firewall, liked the sound, your article on the misinformation virus makes a lot of sense and I wanted 2-factor authentication for all, but subscribers, so I gave your plugin a try.
There is a lot I like about the plugin, but on multisite it requires to authenticate for every site separately. That is a bit of a problem.
— 1. Is there a way to avoid this?Also, when trying to login again through the main site instead “Firewall Trigger: Leading Schema” was triggered due to “offending parameter redirect_to”. The same happened when saving changes to a page. It’s stated to be prone to problems, but it would not have been clear without the audit trail viewer. Suggestion: Perhaps something like “When you get locked out, this should be the first to turn off” would be helpful to others.
Either way, it leads to a feature request.
— 2. The error message when getting locked out is not very helpful to members. It would be great to be able to change that and totally awesome if it would be possible to add some style to it too.While I’m at it, one more question…
— 3. I noticed you are very familiar with Cloudflare. Cloudflare recommends to whitelist their IP’s. Is it indeed recommended to do so in the firewall?
Thank you for your help!
- The topic ‘Few questions about Simple Firewall and multisite’ is closed to new replies.