WordPress login attempts failing
]
Answer #3
I apologize for my previous information. That was the login page not the user’s IP addresses. The two IP addresses of the users who are unable to login are 167.77.0.11 and 86.28.111.31.
Answer #4
Hi there! Thanks for passing that along. I didn’t explain very well, though, it seems – can you open a ticket with our support team, via BackStage, explaining the issue and providing the IP addresses there?
]
Answer #5
Try changing the password for those users.
I’ve had a similar experience, last week, and I tracked it down to the password.
You can check it by going to the login page and entering the password in WITHOUT a User ID. If it’s the same issue that I was getting then it’ll fail in the manner you’ve described already.
If you try that again with a different value in the password field, but leaving the User ID blank, you should get the WordPress login screen with a ‘user id / password is wrong’ type message. Then change the password for the users in question and try and log in and, hopefully, it’ll work OK.
It’s happening, across the board, on s3RiverThames server (my server). I know because I checked some other WordPress sites, on that server, that are nothing to do with me and they all suffer the same fate.
Presumably it is happening on all other Site5 servers as well? It doesn’t, however, happen on other, non-site5, servers (I checked that too – because, originally, I thought I’d discovered a really bizarre bug in WordPress).
It seems to have come on around the time that Site5 mitigated the recent brute force attacks on WordPress.
FWIW, it took me a couple of days to figure this out, plenty of swearing and lots of strong coffee as there’s no help in the error logs at all (you just get a load of 403’s and that’s about it) and trying to search for this kind of error is not easy.
@Site5 – I’d be interested to know, if you figure it out, what’s causing this. Feed the geek in me 🙂
HTH.
Answer #6
Hi phil.t
I didn’t see the ticket that was created for this, and I can’t seem to find it, but if I had to guess I would assume this was caused by mod_security rules we have put in place to combat wp-login.php attacks. This is only one possible cause of this, and I am not saying definitively that this was the cause here, but it is something we’re seeing often enough to make me mention it here 🙂
Answer this Question
You must be Logged In to post an Answer.
Not a member yet? Sign Up Now »
Answer #1
There could be a few reasons for this, but to find out what is happening with any certainty we will need you to open a ticket with our support team, via BackStage. If you could provide the IP address of those connections that are seeing this error, that would be extremely helpful as well.