The 404 is intentional. When you change the wp-admin path and switch on Hide the New Admin Path at WP Ghost > Change Paths > Admin Security, the new admin URL returns a 404 to anyone who isn’t already logged in. This is the point of the option: it makes your custom admin path look like a non-existent URL to bots, scanners, and casual visitors, not just like a renamed login page. The fix is to go to your custom login path (not the new admin path) to log in first. After you log in, you’ll be redirected to your WordPress dashboard on the new admin path. If you’d rather not see a 404 at all, you can either switch off Hide the New Admin Path, or redirect hidden paths to your front page from WP Ghost > Tweaks > Redirects.
Why This Happens: It’s a Feature, Not a Bug
The 404 error you’re seeing is the correct, intended behavior when Hide the New Admin Path is enabled. Here’s what the option actually does and why it exists.
When you change the wp-admin path (for example, from /wp-admin to /mysecretpanel), you’ve replaced a well-known URL with a custom one. That’s a solid first step, but any bot that discovers your custom path through a leak, a log, or guessing, can then attempt brute force attacks against it just as easily as they would against /wp-admin.
Hide the New Admin Path closes that door too. With it enabled, the custom admin URL itself returns a 404 to non-logged-in visitors. There’s no login form on the custom path. There’s nothing to brute force. The path appears to simply not exist. Bots and scanners hit a dead end.
Only users who first log in through the custom login path (a different URL) can reach the dashboard. After logging in, they’re automatically redirected to the dashboard on the new admin path.
How to Access Your Dashboard Correctly
The workflow with Hide the New Admin Path enabled:
- Go to your custom login path, not the custom admin path. These are two separate custom URLs that you configured in WP Ghost.
- Enter your WordPress username and password on the login form.
- After successful login, WP Ghost redirects you to the WordPress dashboard on the new admin path automatically.
If you’re not sure what your custom login and admin paths are, check WP Ghost > Change Paths > Login Security and WP Ghost > Change Paths > Admin Security. For the full setup guide, see Change and Hide wp-admin Path.
How to Stop Seeing the 404 Error
If the 404 bothers you (for example, you’ve shared the admin URL with another administrator and they’re confused by the error), you have two options:
Option 1: Switch Off Hide the New Admin Path
- Go to WP Ghost > Change Paths > Admin Security.
- Switch off Hide the New Admin Path.
- Click Save.
After saving, the new admin URL will redirect non-logged-in visitors to the login page instead of returning a 404. This is easier for administrators to navigate but gives bots a login form to target if they discover the custom path.
Option 2: Change the 404 to a Front Page Redirect
If you want to keep the security benefit of hiding the admin path but replace the bare 404 with a friendlier response (like a redirect to your homepage), configure it at WP Ghost > Tweaks > Redirects.
- Go to WP Ghost > Tweaks > Redirects > Redirect Hidden Paths.
- Select the redirection type. Options documented in the KB are: 404 error (default), 403 error, or redirect to a specific page.
- Click Save.
Full setup in the Redirects guide.
Which Option Should You Choose?
| Option | Best For | Security Trade-off |
|---|---|---|
| Keep Hide the New Admin Path enabled (404) | Maximum hack prevention. Bots see a dead end. | Most effective against automated attacks |
| Switch off Hide the New Admin Path | Simpler access for multiple admins who aren’t technical | Slightly weaker, the custom path shows a login form to anyone who finds it |
| Redirect hidden paths to front page | Client-facing sites where a 404 looks unprofessional | Similar to the 404 option, the admin path still appears to not exist as an admin URL |
For most sites focused on hack prevention, keeping Hide the New Admin Path enabled and getting used to logging in through the custom login path is the best approach. The 404 is the security feature working as intended.
Frequently Asked Questions
Why do I get a 404 error when I access my new admin URL?
Because you have the Hide the New Admin Path option enabled in WP Ghost > Change Paths > Admin Security. This option intentionally returns a 404 to anyone who isn’t logged in, so that the custom admin URL doesn’t look like a reachable login target to bots or scanners. To access the dashboard, go to your custom login path first (not the custom admin path). After logging in, you’ll be redirected to the dashboard on the new admin path.
What’s the difference between the custom admin path and the custom login path?
They’re two separate custom URLs. The custom admin path replaces /wp-admin (the dashboard directory). The custom login path replaces /wp-login.php (the login form URL). With Hide the New Admin Path enabled, you log in through the custom login path, and you’re then redirected to the custom admin path for the dashboard.
Can I turn off the 404 without losing security?
Yes. Instead of switching off Hide the New Admin Path (which makes the custom admin URL show a login form), configure WP Ghost > Tweaks > Redirects > Redirect Hidden Paths to send visitors to your front page or another URL. The admin path still appears to not exist as an admin URL, but visitors see a friendlier response than a raw 404.
What if I forgot my custom login URL?
You can check the URL at WP Ghost > Change Paths > Login Security if you still have access to the dashboard through another device or session. If you’ve lost all access, see the emergency disable guide for recovery via FTP.
Does the 404 affect SEO?
No. Search engine crawlers don’t try to index /wp-admin or your custom admin URL. Admin paths are not indexed, and returning a 404 on the admin URL has no impact on your public content’s search rankings.
Does WP Ghost modify WordPress core files?
No. All path changes and the Hide the New Admin Path behavior are handled through URL rewrite rules and WordPress filters. No files are moved, renamed, or modified. Deactivating WP Ghost restores default paths instantly.