• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Resolved After enabling NGINX, all posts in WordPress blogs in sub-directories are giving 404 Page Not Found

meymigrou

New Pleskian
After I enabled NGINX from Plesk (Web Pro) all my posts in my main and sub-directory blogs give 404 Page Not Found error.

I placed the following code in my "Additional NGINX Directives" in Plesk to fix all the URLS, but it only fixed the main site (example.com) while the sub-directory blogs (example.com/tech/, example.com/mag/ and example.com/dispatch/) are still giving 404 error.

Code:
# Wordpress Permalinks

if (!-e $request_filename) {

    rewrite ^(.+)$ /index.php?q=$1 last;
}

After that, I removed the code and placed the following one:

Code:
if (!-e $request_filename) {

set $test P;

}

if ($uri !~ ^/(plesk-stat|webstat|webstat-ssl|ftpstat|anon_ftpstat|awstats-icon|internal-nginx-static-location)) {

set $test "${test}C";

}

if ($test = PC) {

rewrite ^/(.*)$ /index.php?$1;

}

I found this code in one of the official Plesk pages, and it says:

If a WordPress installation is located in a subdirectory (for example, "httpdocs/sub-dir") or this is a WordPress multisite network based on subdirectories, add the /sub-dir/ before /index.php?$1 so it will look like this: rewrite ^/(.*)$ /sub-dir/index.php?$1;

Note: For WordPress multisite network based on subfolder, add the above rule for each subdirectory.

As of now I got this (which doesn't work):

Code:
if (!-e $request_filename) {

set $test P;

}

if ($uri !~ ^/(plesk-stat|webstat|webstat-ssl|ftpstat|anon_ftpstat|awstats-icon|internal-nginx-static-location)) {

set $test "${test}C";

}

if ($test = PC) {

rewrite ^/(.*)$ /index.php?$1;

rewrite ^/(.*)$ /tech/index.php?$1;

rewrite ^/(.*)$ /mag/index.php?$1;

rewrite ^/(.*)$ /dispatch/index.php?$1;

}

Any help will be much appreciated!

P.S. The main website works like a charm. In example.com/tech/ and /mag/ and /dispatch/ while the homepages are fine, the posts are giving me a 404 page error. I also updated the permalinks in WordPress and it didn't help.
 
Could anyone please take a look and provide me with the right code for Additional NGINX Directives? I'm taking for a website with thousands of visitors each month so it's super important to fix the issue. Any help will be much appreciated!
 
Good day,

have you somehow managed to solve it?

I have a similar problem. I have a wordpress multisite subdirectory and when switching php to NGINX everything works except the administration of plugins in subpages. I tried almost everything I read on the internet, but I couldn't solve it.
 
Good day,

have you somehow managed to solve it?

I have a similar problem. I have a wordpress multisite subdirectory and when switching php to NGINX everything works except the administration of plugins in subpages. I tried almost everything I read on the internet, but I couldn't solve it.

Sorry for the big delay! I've placed the following code in my main's website .htaccess file and all subdirectories started working as expected.

Code:
RewriteEngine On

RewriteBase /

RewriteRule ^index.php$ - [L]

# add a trailing slash to /wp-admin

RewriteRule ^([_0-9a-zA-Z-]+/)?wp-admin$ $1wp-admin/ [R=301,L]

RewriteCond %{REQUEST_FILENAME} -f [OR]

RewriteCond %{REQUEST_FILENAME} -d

RewriteRule ^ - [L]

RewriteRule ^([_0-9a-zA-Z-]+/)?(wp-(content|admin|includes).*) $2 [L]

RewriteRule ^([_0-9a-zA-Z-]+/)?(.*.php)$ $2 [L]

RewriteRule . index.php [L]

Solution credits goes to WPMUDEV.
 
Yes but that solution will work if you just want to use Apache as webserver and nginx as a simple proxy. It does not fix the issue for when you have proxy mode disabled and NGINX is the only one serving the content.
 
Sorry for the big delay! I've placed the following code in my main's website .htaccess file and all subdirectories started working as expected.

Code:
RewriteEngine On

RewriteBase /

RewriteRule ^index.php$ - [L]

# add a trailing slash to /wp-admin

RewriteRule ^([_0-9a-zA-Z-]+/)?wp-admin$ $1wp-admin/ [R=301,L]

RewriteCond %{REQUEST_FILENAME} -f [OR]

RewriteCond %{REQUEST_FILENAME} -d

RewriteRule ^ - [L]

RewriteRule ^([_0-9a-zA-Z-]+/)?(wp-(content|admin|includes).*) $2 [L]

RewriteRule ^([_0-9a-zA-Z-]+/)?(.*.php)$ $2 [L]

RewriteRule . index.php [L]

Solution credits goes to WPMUDEV.
 
I am using Nginx as a proxy behind Apache
I have setup my network to use sub-folders NOT sub-domains
I placed the above code into my .htaccess file and the sub-site URLS works on the front end. However, when I try to access the admin URL for a sub-site it throws a 404 error.

More guidance is required, please!
 
Back
Top