Activates Limit Login attempts after up grade to V 1.5

Hi,

We don’t touch any other plugins with our plugin so our plugin wont be affecting the limit login attempts plugin.

Unless you’re referring to the Login Protect feature of our plugin being active – it shouldn’t be as it’s defaulted to Off on a fresh installation.

Can you elaborate a bit more on what’s happening. Perhaps there’s a bug… the more info I have, the better I can track it down.

Cheers!
Paul.

Hi Paul
This is what I did (happened on about 4 of the 6 sites I updated WSF on)

1 – I logged into my WP dashboard and the WSF updated automatically to ver 1.5.

2 – I deactivated the automatic upgrade function, saved settings and logged out.

3 – When I logged in again the Limit Login Attempts plugin kicked in and said my username or password was incorrect and said I had ## more attempts.

4 – When I logged in a few minites later all was OK.

Like I say – it happened on enough sites to say that the upgrade to WSF 1.5 caused it.

All sites are OK tonight.

I’m running on WP 3.6 and Genesis

That’s really well laid out… I should be able to find the quirk that’s going on here.

My question is… do you need limit login attempts plugin when you have WPSF running? The reason is Limit Login goes by IP address, while WPSF doesn’t need that.
I’ve talked a little about this here:
https://www.icontrolwp.com/2013/08/wordpress-login-cool-down-stops-brute-force-attacks-wordpress/

What feature in LLAs plugin is there that you’d like to see in WPSF?

Let me know your opinion on this.
Cheers,
Paul.

Good question Paul
With the GASP and cooldown periods activated I probably don’t need the LLA plugin.

What time period do you think would be best for the cooldown setting?

The cooldown period is best set to however high you can set it. Remember though, that if you do set it too high and you can’t login, you can manually turn the firewall off (and on) using FTP – this is there so you don’t get locked out of your own site! ??

Check out the FAQ for that one ??

Cheers,
Paul.

I’m going to set this as resolved… I’ve tweaked the login protection code a fair bit to optimize this and play nice, and as we said, there’s probably no need to have other login protection plugins running alongside this.

Cheers,
Paul.

I’m using WordPress Simple Firewall on three sites. All of the them use the Limit Login Attempts plugin and I’m not seeing any conflicts.