Private IP 255.255.255.255

That is not a valid IP address. It looks like a software error. Is it Wordfence reporting that address? Or another tracking package?

Regards,

Mark
PS: If you found this helpful, please rate Wordfence 5 stars.
https://www.ads-software.com/plugins/wordfence/

I guess that it is not valid however, it is the one that is reported by Wordfence.

30 invalid username login attempts by the user at this ID address and the system is not locking them out despite the setting being checked to immediately lock out invalid usernames and for 10 days.

Reluctant to block it as it is also a private network (internal) IP address.

Thanks for your help.

I still need guidance on whether to block or not? Anyone any views?

Hi,

I think this was a bug introduced in 4.0.2. Please upgrade to 4.0.3 which just went out and see if that fixes it. I think it probably will.

Regards,

Mark.

Updated and will see what happens. Cheers

Just to update you, since moving to 4.0.3, and making a few other settings changes in Wordfence (happy to explain what these are if asked to), not having the 255.255.255.255. any more and brute force attempts have dropped to a virtual zero – wonderful! Thank you.

Woohoo!! Glad to be of help and glad it’s working for you!!!

Regards,

Mark
PS: If you found this helpful, please rate Wordfence 5 stars.
https://www.ads-software.com/plugins/wordfence/

Hi,
I think it’s not resolved. My Wordfence-version is 4.0.3 an there is a livetraffic entry (or exactly 39): “An unknown location at IP 255.255.255.255 attempted a failed login using an invalid username…”
Blocking is impossible.

Regards,
Jens