Nginx - wordpress in a subdirectory, what data should be passed?

📝 Title: Troubleshooting Nginx - Wordpress Subdirectory Issues: What Data Should be Passed?

Introduction: Hey there tech enthusiasts! Are you facing issues with your Nginx and Wordpress setup in a subdirectory? 😕 Don't worry, we've got your back! In this blog post, we'll dive into a specific problem where Wordpress in a subdirectory throws a "page not found" error, and we'll provide you with easy solutions to tackle this. So, let's get started! 💪

🤔 Problem Description:

Our reader has tried various approaches, but currently, their Nginx configuration for the subdirectory looks like this:

location ^~ /wordpress {
    alias /var/www/example.com/wordpress;
    index index.php index.html index.htm;
    try_files $uri $uri/ /wordpress/index.php;

    location ~ \.php$ {
        include fastcgi_params;
        fastcgi_pass 127.0.0.1:9000;
        fastcgi_split_path_info ^(/wordpress)(/.*)$;
        fastcgi_param SCRIPT_FILENAME /var/www/example.com/wordpress/index.php;
        fastcgi_param PATH_INFO $fastcgi_path_info;
    }
}

The issue they're facing is "page not found" when visiting http://www.example.com/wordpress or any post URLs. They suspect that Wordpress isn't correctly obtaining data about the path, and they also noticed that running example.com/wp-admin.php executes index.php.

👨‍💻 Analyzing the Issue:

The problem seems to stem from the Nginx configuration and its interaction with the Wordpress installation. To resolve it, we should investigate what data needs to be passed and identify potential misconfigurations.

🔍 Solution: What Data Should be Passed?

1. Verify the FastCGI Path Info:

   • In your Nginx configuration, locate the line fastcgi_split_path_info ^(/wordpress)(/.*)$;.

   • Confirm that the fastcgi_split_path_info argument is using the correct path for your Wordpress installation. Double-check the path, including trailing slashes, capitalization, and spelling.

2. Ensure Correct SCRIPT_FILENAME:

   • Examine the line fastcgi_param SCRIPT_FILENAME /var/www/example.com/wordpress/index.php;.

   • Confirm that the SCRIPT_FILENAME parameter points to the correct path of the index.php file within your Wordpress subdirectory.

3. Check the PATH_INFO parameter:

   • Look at the line fastcgi_param PATH_INFO $fastcgi_path_info;.

   • Verify that the PATH_INFO parameter is correctly configured to pass the path information to Wordpress. If needed, change $fastcgi_path_info to $path_info.

4. Restart Nginx and Test:

   • After making any configuration changes, restart Nginx using sudo service nginx restart.

   • Visit http://www.example.com/wordpress and test if the "page not found" error persists. Repeat the process for post URLs and the wp-admin.php file.

🙌 Call-to-Action:

Great job troubleshooting the Nginx and Wordpress subdirectory issue! We hope our solutions resolved the "page not found" error for you. If you found this guide helpful, consider sharing it with fellow tech enthusiasts who might be facing similar problems. If you have any questions or need further assistance, don't hesitate to leave a comment below. Let's build a supportive tech community! 🌟