swordspres

my fix was suggested by my host: while the domains in the wp network worked for years without adding child sites domains to cpanel, after a cpanel update i had to add them as addon domains in order to have them work, and fix the “bug”. I understand this is not WP related, and may not be your problem, but felt obliged to report it.

in my case, wp 3.9 auto update also broke my wp multisite install, and i have subsites on subdomains. Now subsites redirects to default cpanel page, and subsites can’t be accessed from the admin area as /wp-admin/ for subsites brings:

404 Not Found
The server can not find the requested page:
/wp-admin/ (port 80)

same here

update: developer has updated the plugin a few hours later. Excellent work, i confirm it now works flawlessly.

…insanely fast solution! A big thanks, a very small tip sent.

I use a renamed wp-login.php from months with great satisfaction. It’s easy just google it.

But today i was spending time hardening my WP, and i had a very dumb doubt: what happens if i type “mydomain.com/wp-admin/” only? You get redirected to “mydomain.com/wp-admin/your-secret-login.php”!

So i ask myself… what is the advantage in renaming wp-login? It’s placebo!

So Chris is right… but i can’t understand why WordPress doesn’t introduce a native brute-force feature. I hate editing core files to increase security or running external plugins.