When wp-admin fails but the public site still loads, the cause is often specific to authentication, admin-only code, security rules, cookies or dashboard requests.
Symptoms
- /wp-admin/ redirects repeatedly, returns 403/404/500 or stays blank.
- Login succeeds and immediately returns to the login screen.
- The dashboard loads without styles, scripts or AJAX functionality.
- Only one administrator account is affected.
Common causes
The same visible WordPress error can have several causes. A reliable fix starts by matching the symptom to logs, request behavior and recent changes.
- Cookie/domain mismatch after HTTPS, domain or migration changes.
- Security plugin, WAF or hosting rule blocking admin requests.
- Admin-only plugin/theme PHP errors.
- Incorrect siteurl/home values or reverse-proxy configuration.
- Corrupted user capabilities or session data.
Safe diagnosis
- Check status codes and redirects for /wp-login.php and /wp-admin/.
- Test browser cookies and canonical HTTP/HTTPS/domain behavior.
- Review PHP and firewall logs for blocked or fatal admin requests.
- Isolate admin-only plugins and confirm user capabilities.
Production safety: create a recovery point before changing code, plugins, database values or server configuration. Business-critical WooCommerce sites should avoid random deactivate/update experiments during active traffic.
How the issue is fixed
- Correct URL/cookie/proxy configuration.
- Adjust the specific security rule blocking legitimate admin access.
- Repair the failing plugin or PHP code.
- Restore user roles/capabilities without creating unnecessary administrator accounts.
Avoid this shortcut: Avoid disabling all security controls permanently just to regain access. Identify the exact rule or component responsible.
When to request expert WordPress bug fixing
Professional troubleshooting is useful when the site is business-critical, the error returns after a temporary fix, wp-admin is unavailable, the failure began after a complex update/migration, or you cannot identify the responsible code from logs. WP•FIX focuses on the smallest safe change that restores the failing path and explains the root cause.
FAQ
Why can visitors see the site while wp-admin is broken?
Frontend pages may be cached or use different code paths. Admin requests load additional plugins, AJAX endpoints and authentication logic.
Can Cloudflare cause wp-admin problems?
Yes. Cache, bot protection or firewall rules can interfere with login/admin requests if configured incorrectly.
Can I regain access without creating a new admin user?
Often yes. The goal is to restore the existing authentication path rather than create extra privileged accounts.
Why does wp-admin return 403?
A WAF, security plugin, server rule or filesystem permission may be denying the request.
Need this WordPress issue fixed?
Send the URL, error message and what changed immediately before the problem started.
Request troubleshooting