Apache2代理重定向配置问题：外网访问内网Web应用失败

Hey there, let's get your Ampache app accessible from the public web through your server A. I'll walk you through the key fixes and checks since your current config isn't working as expected.

Step 1: Enable Required Apache Modules on Server A #

First off, make sure Apache has the proxy modules enabled—this is a super common oversight. Run these commands on server A:

# For Debian/Ubuntu systems
a2enmod proxy proxy_http
systemctl restart apache2

# For CentOS/RHEL systems
yum install mod_proxy mod_proxy_http  # If not already installed
systemctl restart httpd

Step 2: Correct Your VirtualHost Configuration #

Your current config has a couple of issues, including an outdated NameVirtualHost line (it's not needed in Apache 2.4+) and a missing trailing slash in your ProxyPass target (which causes path mapping errors). Replace your existing config with this:

<VirtualHost *:2323>
    # Replace with your server A's public domain or IP
    ServerName your-public-server-ip-or-domain.com

    # Forward all requests to your internal Ampache instance
    ProxyPass / http://192.168.1.7/ampache/
    ProxyPassReverse / http://192.168.1.7/ampache/

    # Preserve host headers to avoid redirect issues
    ProxyPreserveHost On

    # Optional: Set forwarded headers if you use HTTPS (adjust port if needed)
    RequestHeader set X-Forwarded-Proto "http"
    RequestHeader set X-Forwarded-Port "2323"
</VirtualHost>

Why the trailing slash? Without it, Apache will incorrectly concatenate paths—for example, a request to http://serverA:2323/login would get forwarded to http://192.168.1.7/ampachelogin instead of http://192.168.1.7/ampache/login.

Step 3: Verify Network & Firewall Rules #

You need to make sure traffic can flow between server A and your internal Apache server, and that public traffic can reach server A's port 2323:

• Server A Firewall: Open port 2323 for TCP traffic:

  # Ubuntu/Debian with UFW
  ufw allow 2323/tcp
  
  # CentOS/RHEL with firewalld
  firewall-cmd --add-port=2323/tcp --permanent
  firewall-cmd --reload
  

• Cloud Security Group: If server A is a cloud instance (AWS, Azure, etc.), don't forget to add an inbound rule allowing port 2323 from the internet in your cloud provider's security group dashboard.
• Internal Connectivity: On server A, test if you can reach the internal Ampache app directly:

  curl http://192.168.1.7/ampache
  

  If this fails, fix the internal network connection first (check internal firewalls, routing, etc.).

Step 4: Tweak Ampache's Internal Configuration #

Ampache might need to know it's behind a reverse proxy to work correctly:

1. Open Ampache's config file (usually /etc/ampache/ampache.cfg.php or in your web root)
2. Update these settings:

   $http_host = "your-public-server-ip-or-domain.com";
   $web_path = "/";
   

3. If Ampache has a setting to allow reverse proxy IPs, add server A's internal IP to that list to prevent access issues.

Step 5: Test & Troubleshoot #

After making these changes, restart Apache on server A. Then try accessing http://your-server-a-public-ip:2323 from an external device.

If it still doesn't work, check Apache's error logs for clues:

# Ubuntu/Debian
tail -f /var/log/apache2/error.log

# CentOS/RHEL
tail -f /var/log/httpd/error_log

Logs will tell you if modules are missing, connections are refused, or path mappings are wrong.

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