如何为所有子域名配置统一的.htaccess ErrorDocument 404页面？

Hey there, let’s work through this frustrating 404 configuration issue you’re dealing with. It sounds like you’ve got a great-looking custom 404 page, but getting it to work across all subdomains is throwing errors—either showing the raw path text or that annoying nested 404 error. Let’s break down what’s going wrong and how to fix it.

First, Why That Nested 404 Error Happens #

Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.

This error pops up because Apache can’t find the ErrorDocument file you specified. When it tries to serve your custom 404 page for a missing resource, it can’t locate /error/404.html relative to the subdomain’s document root, so it throws a second error. Relative paths in .htaccess are tricky here because each subdomain likely has its own separate document root (not inheriting /var/www by default).

Solutions for Unified Subdomain 404 Handling #

1. Use an Absolute URL (Simplest Approach) #

Instead of a relative path, point the ErrorDocument to a full URL that’s accessible to all subdomains. This ensures every subdomain redirects to the same working 404 page, no matter their document root.

Add this to your Apache main configuration (like httpd.conf or a virtual host config file) or a global .htaccess if you must:

ErrorDocument 404 https://your-main-domain.com/error/404.html

Pro tip: Test the URL first in your browser to make sure it loads correctly—this eliminates path-related issues entirely.

2. Configure a Shared Error Directory (For Local File Access) #

If you want the 404 page to load from a shared location instead of redirecting, use an Alias in your Apache virtual host config to map /error paths across all subdomains to a single shared directory.

1. Create a shared error directory (e.g., /var/www/shared/error) and place your 404.html there.
2. Update your wildcard subdomain virtual host config:

<VirtualHost *:80>
    ServerName *.your-domain.com
    # Map /error requests to the shared directory
    Alias /error /var/www/shared/error
    # Point ErrorDocument to the aliased path
    ErrorDocument 404 /error/404.html
    # Rest of your subdomain config (document root, etc.)
    DocumentRoot /var/www/subdomains/%1/htdocs
</VirtualHost>

3. Ensure the shared directory and file have proper permissions for Apache to read them:

chmod -R 755 /var/www/shared/error
chown -R www-data:www-data /var/www/shared/error # Use apache:apache on RHEL/CentOS

3. Fix .htaccess Inheritance Issues #

If you’re dead-set on using .htaccess, avoid relying on inheritance from /var/www—most subdomains have their own document roots outside of this directory, so the path won’t resolve. Instead:

• Copy the error/404.html folder to each subdomain’s document root, or
• Use an absolute filesystem path in the ErrorDocument (note: this works in Apache 2.4+):

  ErrorDocument 404 /var/www/shared/error/404.html
  

  Warning: Filesystem paths can cause permission issues if Apache doesn’t have access to the directory.

Final Checks #

• After making changes, restart Apache to apply them:

  sudo systemctl restart apache2 # Or httpd on RHEL/CentOS
  

• Test a non-existent URL on any subdomain to confirm the custom 404 page loads correctly.

内容的提问来源于stack exchange，提问作者TECHNOFAB