After migration of WordPress website I can't access the admin (white page)

After migration of WordPress website I can't access the admin (white page)

  1. Blog
  2. 15 November 2026
  3. 3 min read

Stefan Bogdanescu

Founder & Senior Architect

Diagnosing the White Screen After WordPress Migration

Encountering a white screen when accessing wp-admin immediately after migrating a site from local development to production is a classic symptom of misconfigured constants or missing files, even if the front-end homepage loads correctly. The fact that your root URL (http://scorejava.com/wordpress/) works while the admin area fails suggests PHP is executing successfully but failing silently before it can render the dashboard. This often points to file permission issues or a specific configuration conflict introduced during the migration process.

The most frequent culprit in scenarios like this involves the WP_CONTENT_DIR and WP_CONTENT_URL definitions, which are critical when moving from a local environment like /var/www/wordpress to a production root directory. While your database was correctly updated using a search-and-replace script to change http://localhost/wordpress occurrences to http://scorejava.com/wordpress/, this tool only modifies the database tables. It does not alter the actual files on the server.

If your local installation relied on hard-coded paths in configuration files or if the migration involved copying a folder structure that included specific constants, those definitions might still be pointing to the old localhost environment or incorrect relative paths. When WordPress attempts to load the admin interface, it often requires different file access levels than the front end. If the wp-content directory or its subdirectories (uploads, themes, plugins) do not have the correct ownership or permissions on the new server, PHP can throw an error that gets swallowed by display_errors = Off.

To resolve this without guessing, start by enabling WordPress debug mode to surface the underlying error. Edit your wp-config.php file and ensure these lines are present at the top:

define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );

Accessing the site with these settings enabled will redirect any fatal errors to a log file, usually located in wp-content/debug.log. This is safer than displaying errors directly on a live site. Once you identify the specific error message, you can address the root cause. Common findings include "require_once() failed" for missing theme or plugin files, indicating that a file was not copied correctly or has incorrect permissions (e.g., 755 instead of 750/755 for directories and 644 for files).

Another potential issue arises from the ABSPATH constant. If your local setup placed WordPress in /var/www/wordpress, your wp-config.php might have been set to expect that specific path. When you moved it to http://scorejava.com/wordpress/, ensure that ABSPATH points strictly to the new directory on the live server:

define( 'ABSPATH', __DIR__ . '/');

If you are using a framework or if your local environment utilized a specific bootstrap mechanism that differs from standard WordPress, this mismatch could prevent the admin loader from initializing. Additionally, verify that .htaccess rules are correctly configured for the new directory structure. A 403 Forbidden error sometimes manifests as a white screen if the server strips the HTML response body before logging it.

If you encounter persistent issues after checking debug logs and permissions, consider if the migration process inadvertently left behind local-only files or configuration snippets. Ensure that no references to /var/www remain in wp-config.php or within the wp-content directory. Finally, if the site is built on a custom stack or uses a specific hosting environment, double-check that the upload limits and memory allocation are sufficient for the admin panel, which often consumes more resources than the static homepage. For complex migrations involving custom server configurations, consulting a specialized migration guide can prevent these recurring headaches.

Our network