Magento 2 Admin White Screen After Login: How to Fix It

Your admin credentials are correct, login "succeeds," and then — nothing. A blank white page where the dashboard should be. Here's the order to check things in.

Step 1: Open the Browser Console First

Before touching any server config, open dev tools and check the Console and Network tabs. A white screen after login is almost always a JavaScript failure, and the console will usually tell you exactly which file failed to load or execute.

Look specifically for 404s on files under /static/ — that's the single most common root cause.

Step 2: Deploy Static Content

If Magento is running in production mode, admin (and storefront) JS/CSS/fonts have to be pre-compiled ahead of time. If that step was skipped or only partially completed after a deploy, the admin panel loads its HTML shell but every asset request 404s, and you get a white screen with a wall of console errors.

bin/magento setup:static-content:deploy -f
bin/magento cache:flush

If you're not sure what mode you're in:

bin/magento deploy:mode:show

Step 3: Check for a Suppressed PHP Error

If display_errors is off (correctly, for production) and something threw a fatal error, you'll get a blank page with zero visible feedback. Check the real logs instead of the browser:

tail -f var/log/exception.log
tail -f var/log/system.log

If nothing's there either, check your web server's PHP error log directly — a fatal error during early bootstrap can happen before Magento's own logging is even initialized.

tail -f /var/log/php8.2-fpm.log

Step 4: Clear Cache and Reindex

A corrupted config or ACL cache can produce a login that "succeeds" (session created) but fails silently while building the dashboard layout.

bin/magento cache:clean
bin/magento cache:flush
bin/magento indexer:reindex

Step 5: Check Cookie and Session Configuration

If your admin cookie domain, path, or lifetime settings don't match how you're actually accessing the site (e.g. accessing via an IP or a different subdomain than what's configured), the session can appear to authenticate but never persist correctly, leaving you on an empty authenticated shell.

Check admin/security/session_cookie_lifetime and cookie domain settings under Stores > Configuration > Advanced > Admin > Security, or directly in the core_config_data table if the admin UI itself is what's broken.

Step 6: Rule Out a Bad Custom Module

If this started right after installing or updating a third-party extension, disable it and retest:

bin/magento module:disable Vendor_Module
bin/magento cache:flush

If the dashboard loads with it disabled, you've found your culprit — check that module's system.log entries specifically before re-enabling.

Recap

1. Check the browser console for 404s on static assets — this alone resolves most cases.
2. Run static content deploy if you're in production mode.
3. Tail exception.log, system.log, and PHP-FPM's own log for a suppressed fatal error.
4. Clear cache and reindex.
5. Check cookie domain/session config if the above are clean.
6. Bisect by disabling recently added modules.