本地Nginx多路径配置下PHP论坛index.php报502错误求助

Hey there, let's dig into why your PHP forum is throwing a 502 Bad Gateway when accessing index.php—especially since your static index.html works and phpMyAdmin is running smoothly. The issue almost certainly lies in how Nginx is routing PHP requests to your PHP processing backend (usually PHP-FPM) for the forum path. Here's a step-by-step troubleshooting plan:

1. Compare Forum PHP Configuration to phpMyAdmin's Working Setup #

Since phpMyAdmin handles PHP requests correctly, use it as a reference:

• Check the fastcgi_pass directive in both location blocks. Did you accidentally use a wrong Unix socket path (e.g., /run/php/php7.4-fpm.sock instead of /run/php/php8.2-fpm.sock) or an incorrect TCP port (like 127.0.0.1:9001 when PHP-FPM listens on 9000)?
• Verify the fastcgi_param SCRIPT_FILENAME value. For your forum, it should point to the correct document root, e.g., $document_root$fastcgi_script_name;—if you hardcoded a path that doesn't match your forum's actual directory (like /var/www/other-site instead of /var/www/forum), PHP-FPM can't find the script and returns an error.

2. Validate PHP-FPM Status and Permissions #

• First, confirm PHP-FPM is running:

  sudo systemctl status php<your-version>-fpm
  

  If it's stopped, start it with sudo systemctl start php<your-version>-fpm and enable auto-start with sudo systemctl enable php<your-version>-fpm.
• Check file/directory permissions for your forum:
  Ensure the Nginx user (typically www-data) has read access to your forum's PHP files and execute access to parent directories. Run:

  ls -l /path/to/your/forum/index.php
  ls -ld /path/to/your/forum
  

  Permissions should be at least 644 for files and 755 for directories, with the owner/group including www-data (or the Nginx user you're using).
• If using a Unix socket for PHP-FPM, verify the socket's permissions:

  ls -l /run/php/php<your-version>-fpm.sock
  

  The socket should be readable/writable by www-data—if not, adjust permissions or update the PHP-FPM pool config to set the correct user/group.

3. Check Error Logs for Specific Clues #

Logs will tell you exactly what's failing:

• Nginx Error Log: Look in /var/log/nginx/error.log (or your custom log path) for entries related to 502 errors. You might see messages like:

  connect() to unix:/run/php/php8.2-fpm.sock failed (13: Permission denied) while connecting to upstream
  no such file or directory while connecting to upstream
  These directly point to permission issues or incorrect socket/path settings.

• PHP-FPM Log: Check /var/log/php<your-version>-fpm.log for errors like connection refusals, pool configuration issues, or script execution failures.

4. Test PHP-FPM Directly #

Bypass Nginx to confirm PHP-FPM can handle the forum's index.php:
Use curl to send a request directly to the PHP-FPM socket (run as the Nginx user to mimic real requests):

sudo -u www-data curl --unix-socket /run/php/php<your-version>-fpm.sock http://localhost/path/to/forum/index.php

If this returns a valid HTML response, the problem is in Nginx's configuration. If it returns an error or nothing, PHP-FPM isn't processing the script correctly.

5. Verify Location Block Matching Priority #

Make sure no conflicting location blocks are intercepting your forum's PHP requests:

• If you have a global location ~ \.php$ block, ensure your forum's location block properly handles PHP requests (either by nesting a PHP-specific location inside /forum/ or adjusting regex priority with ^~ to prioritize the forum path over global rules).
• Avoid overlapping regex patterns that might route forum PHP requests to the wrong backend.

内容的提问来源于stack exchange，提问作者f.c