Applicable to:
- Plesk for Linux
Symptoms
-
Unable to open website pages except
.phpwhen nginx is enabled. The following error is shown in a browser:PLESK_INFO: 403 Forbidden
-
The following options are enabled at Plesk > Domains > example.com > Apache & Nginx Settings.
- Restrict the ability to follow symbolic links
- Smart static files processing
The following records can be found in domain's error log
CONFIG_TEXT: 2020/08/31 11:37:51 [error] 19701#0: *21516 open() "/var/www/vhosts/example.com/httpdocs/website/wp/wp-content/test.css" failed (13: Permission denied), client: 203.0.113.2, server: example.com, request: "GET /wp-content/test.css HTTP/2.0", upstream: "https://203.0.113.10:7081/wp-content/uploads/2015/09/menschlich1.png", host: "www.example.com", referrer: "https://www.example.com/"
Cause
This is a Plesk bug with ID PPPM-5348, which will be fixed in future product updates.
nginx is unable to access files with default permissions if the option Restrict the ability to follow symbolic links is enabled.
Resolution
Log in to Plesk web interface and apply one of the following workarounds:
-
Disable the option Restrict the ability to follow symbolic links at Plesk > Domains > example.com > Apache & Nginx Settings.
-
Disable the option Smart static files processing at Plesk > Domains > example.com > Apache & Nginx Settings.
Comments
9 comments
disable_symlinks if_not_owner from=</var/www/vhosts/example.com/httpdocs>;
I believe this is the same issue, but with a workaround included: https://support.plesk.com/hc/en-us/articles/115000263014-Static-content-CSS-and-images-is-not-loaded-by-browser-13-Permission-denied
This has not been fixed?
Having the setting enabled on Plesk 18.0.28 u3 works fine, but after updating to Plesk 18.0.29 it broke all my Wordpress sites:
https://talk.plesk.com/threads/plesk-obsidian-18-0-29-update-makes-my-wordpress-sites-malfunction.357610/
Hello Necro
Sorry for the late response. There were fixes connected with PPPM-5348 in Plesk 18.0.29. However, we haven't received similar issues so far.
The issue indeed requires deeper investigation.
Please, submit a support request to us directly or to Plesk partner, depending on where Plesk license was purchased.
Confirming that the upgrade to 18.0.29 certainly broke as it updated all of the configs (as noted in the release notes). Any systems where we had restrict symlinks enabled and were upgraded (from 18.0.28) had to be have the feature disabled again as detailed in this KB.
We didn't report the issue as this was (and still is!) marked "will be fixed in future product updates".
Hello Tim Butler
Thank you for letting us know.
Is there any way to disable either of these options in bulk across domains? For example, if I wanted to disable "Restrict the ability to follow symbolic links?" I've not bothered to check what files/database records get changed when the setting gets toggled.
Hello
in update 18.0.31, same problem
Hello Momir Krstic
It's currently expected in 18.0.32.
Please sign in to leave a comment.