All 31 Login Security answers

See every answer

Answer

My sign-in page is a 404 after moving it

Updated Login Security 1.6.0Tested with WordPress 7.1

The plugin catches the new address itself, before WordPress decides what the request is, so permalinks and rewrite rules are not involved and re-saving them changes nothing. Three things actually cause it:

  • the word you chose was refused. A word under three characters, one WordPress owns (login, admin, wp-admin, feed and a few more), or one that is already a page on your site is not accepted, and the door stays where it was. The screen says so when it happens;
  • a page cache is holding the 404 it stored from before the move. Clear it;
  • a server rule is answering first. Some hosts have a rule for /wp-login.php or for unknown paths that never reaches WordPress.

wp login-security door prints the address the plugin thinks the door is at, and the recovery link still opens the original wp-login.php from anywhere.

Still stuck? Ask the developers who wrote it. We aim to reply within one business day.

Login Security

Stop the machines guessing at your passwords, and see exactly who has been trying.

From $19 a year · every feature · 30-day refund

Buy Login SecuritySee the plugin

The Login Security dashboard in WordPress admin. A green notice reads 1 lockout this week, and the site is fine: 13 attempts were refused, from 4 addresses. Four cards show 13 refused this week, 1 locked out, 4 addresses and 1 signed in. A panel headed You cannot be locked out lists the address you are on, that signed-in administrators are never locked out, and the sign-in page, with a Never lock out the address I am on now button. Below it, Usernames being tried shows admin tried 7 times, marked a real account and no second step.