迁移至AWS后Joomla站点需加index.php才可访问，求解决方案

Hey there, I’ve run into this exact headache after migrating Joomla sites to AWS before—let’s break down the most likely fixes step by step:

1. Verify Web Server Rewrite Module is Enabled & Configured Correctly #

AWS instances often have strict default configs, so first make sure your web server (Apache or Nginx) is set up to handle URL rewrites properly:

For Apache: #

• Check if mod_rewrite is active: Run sudo apache2ctl -M (Ubuntu/Debian) or sudo httpd -M (Amazon Linux) and look for rewrite_module (shared). If missing, enable it with sudo a2enmod rewrite (Ubuntu) or uncomment the LoadModule rewrite_module line in httpd.conf (Amazon Linux), then restart Apache.
• Update your directory config to allow .htaccess overrides: Ensure the <Directory> block for your Joomla root has AllowOverride All (not None). Example:

  <Directory "/var/www/html">
      Options Indexes FollowSymLinks
      AllowOverride All
      Require all granted
  </Directory>
  

  Restart Apache after making this change.

For Nginx: #

• Add rewrite rules to your server block to route all requests through index.php:

  server {
      listen 80;
      server_name your-domain.com;
      root /var/www/html;
  
      location / {
          try_files $uri $uri/ /index.php?$args;
      }
  
      # Include PHP-FPM handling config here if needed
  }
  

  Restart Nginx to apply changes.

2. Double-Check Joomla Global Configuration #

You might need to access the admin panel temporarily via your-domain.com/index.php/administrator to tweak these settings:

• Go to System > Global Configuration > SEO Settings:
  • Set URL Rewriting to Yes
  • Leave Live Site empty (Joomla auto-detects) or set it to your exact domain (e.g., https://your-domain.com)
  • Uncheck Add Suffix to URL if you don’t need .html extensions (this can cause unexpected conflicts)
• Confirm your Joomla root .htaccess is the official default version (copy from a fresh Joomla install if yours is missing or modified). Also fix permissions: set it to 644 and ensure it’s owned by the web server user (e.g., www-data for Ubuntu, apache for Amazon Linux).

3. AWS-Specific Config Checks #

If you’re using AWS services like Elastic Beanstalk or CloudFront, there are extra tweaks needed:

Elastic Beanstalk: #

• Create an .ebextensions folder in your Joomla root, then add a config file (e.g., 01_apache_rewrite.config) to enable AllowOverride All:

  files:
    "/etc/httpd/conf.d/allow_override.conf":
      mode: "000644"
      owner: root
      group: root
      content: |
        <Directory "/var/www/html">
          AllowOverride All
        </Directory>
  

  Deploy this change to your Beanstalk environment.

CloudFront: #

• If using CloudFront as a CDN:
  • Ensure your cache behavior forwards the Host header to your origin server (Joomla relies on this to detect the correct site)
  • Clear CloudFront’s cache (old default page content often gets stuck in cache after migrations)
  • Confirm CloudFront forwards dynamic requests (those without index.php) to your origin, rather than serving cached static content.

4. Test Rewrite Functionality #

To isolate whether the issue is server-level or Joomla-specific:

• Add a simple test rule to your .htaccess (Apache) or Nginx config:

  # Add to .htaccess
  RewriteRule ^test-rewrite$ /index.php?test=1 [L]
  

• Visit your-domain.com/test-rewrite—if it loads your Joomla site with the test=1 parameter, rewrites are working at the server level, and the issue is likely in Joomla’s SEO config or .htaccess rules. If not, go back to server-level rewrite setup.

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