Back to Community
Home / Community / Core → Networking wordpress

Fixing WordPress Multisite Subdomain Dashboard Redirects and 404 Errors

25 threads Sep 16, 2025 Core → Networking wordpress

Content

If you've set up a WordPress Multisite network with subdomains, you might encounter a frustrating issue: clicking the "Dashboard" link for a sub-site redirects you to the wrong place—often the main site's login, an unrelated site's admin, or a 404 error page. This is a common problem discussed across various support forums, including threads about 'Networking WordPress'. Let's break down why this happens and how to fix it.

Why Do Subdomain Dashboard Redirects Happen?

Based on the analysis of common user reports, this redirect issue is rarely a bug in WordPress itself. Instead, it's almost always caused by a misconfiguration in one of three areas:

  1. Server (DNS & Web Server) Configuration: The wildcard subdomain DNS record (*.yourdomain.com) is missing or incorrect, or the web server (like nginx or Apache) is not properly configured to handle requests for any subdomain.
  2. WordPress Configuration: The values for WP_HOME and WP_SITEURL in the sub-site's settings or database might be incorrect, often pointing to the main domain or localhost instead of the full subdomain URL.
  3. .htaccess Rules: The Multisite-specific rewrite rules in the .htaccess file might be missing, incomplete, or conflicting with other rules.

How to Troubleshoot and Fix the Redirects

Follow these steps to resolve the subdomain dashboard access problem.

1. Verify Your Wildcard DNS Record

The most common cause is a missing wildcard DNS record. A wildcard record (like *.yourdomain.com) ensures that any subdomain request is directed to your server. You must create an "A" record in your domain's DNS settings with the hostname * pointing to your server's IP address. Without this, subdomains like test.yourdomain.com cannot be resolved and will not load.

2. Check Your Web Server Configuration

Your server must be configured to accept requests for any subdomain.

  • For Apache: The wildcard subdomain is usually handled by the .htaccess file. Ensure your .htaccess file contains the correct Multisite rewrite rules for subdomains. The official WordPress codex provides the exact rules you need.
  • For nginx: Configuration happens at the server level. Your server_name directive must include both the main domain and the wildcard subdomain (e.g., server_name yourdomain.com *.yourdomain.com;). You may need to contact your hosting provider or server administrator to confirm this is set up correctly.

3. Review Your WordPress Settings

Log into your network admin dashboard and navigate to My Sites > Network Admin > Sites. Edit the problematic sub-site and check these two fields:

  • Site Address (URL): This must be the full subdomain URL (e.g., https://test.yourdomain.com).
  • Home: This should also be the full subdomain URL.

If these are grayed out, you may need to update them directly in the database within the wp_#_options table (or wp_options for the main site) for the specific site's siteurl and home values. Always back up your database before making changes.

4. Clear Caching and Cookies

After making configuration changes, clear your browser cache and cookies. A stubborn cached redirect or old cookie can sometimes cause persistent login loops.

When Multisite Might Not Be the Right Tool

As seen in some user reports, sometimes the underlying goal doesn't actually require a Multisite network. For example, if you simply want one domain to display the content of a page on another domain, a redirect or a simpler method might be more appropriate than creating an entirely new site within a network. The 'Networking WordPress' documentation often suggests evaluating your use case first.

Need More Help?

If you've checked all these settings and the problem persists, the issue could be more specific to your server environment. Detailed error logs from your web server can provide crucial clues. You can often find these in your hosting control panel (e.g., cPanel) or by asking your hosting provider for assistance. For further reading, the WordPress.org codex has an extensive guide on debugging a WordPress network.

Related Support Threads Support