• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Question Apache could not follow symbolic link

changer323

New Pleskian
I already configured the symlink to be owned by <user>: psacln. I want to ask if what is the global config of Apache to allow all sites to use +FollowSymLinks, I am searching for different past post but it seems to involve different Plesk user and groups especially ftp. It is also helpful to have a breakdown of this users to solve my encountered problem
 
First of all, you should _not_ enable FollowSymLinks on your webserver, as this is potentially dangerous for your webserver/customers. If you really need to access a symlink on your webpage then it's better to use "+SymLinksIfOwnerMatch" and make sure that the symlink destination is owned by the same user and subscription as the symlink source.
Note: You can not symlink files/directories across subscriptions.

If you insist on using "+FollowSymLinks" then you should update your Service Plans and uncheck the box "Restrict the ability to follow symbolic links" in your Service Plan under "Webserver". But again, I highly recommend not to do that.
 
Thank you for the response, I have already followed the to put the custom directive, also "+FollowSymLinks" and "+SymLinksIfOwnerMatch". I do this because I need to put a subdomain website into a directory. E.G. subdomain.example.com to example.com/subdomain. Is there a recommended recourse for what i want to do? Is there an alternative other than using symlinks. Thanks
 
Back
Top