- Plesk for Linux
A website is not accessible with the following error message in a web-browser:
PLESK_INFO: 500 Internal Server Error.
The following error message appears on the logs page in Plesk at Domains > example.com > Logs:
CONFIG_TEXT: [core:alert] /var/www/vhosts/example.com/httpdocs/.htaccess: Option FollowSymlinks not allowed here
CONFIG_TEXT: [core:alert] /var/www/vhosts/example.com/httpdocs/.htaccess: Option All not allowed here
The option Restrict the ability to follow symbolic links is enabled at Domains > example.com > Hosting & DNS > Apache & nginx Settings.
Go to Domains > example.com > Hosting & DNS > Apache & nginx Settings and disable the option Restrict the ability to follow symbolic links.
Note: To manage this option for all domains in Plesk, visit this KB article.
Note: The option can also be adjusted in the .htaccess file. Find the .htaccess file in the httpdocs directory of the domain and change the option
Options All -Indexesto
Options -Indexesto remove the error *Option All not allowed here*
Solved our problem. Thank you.
Problem Solved ! Thanks
Solved my problem!
Changing in service plans does not appear to update all the sites connected to the service plan.
(Without looking ourselves) is there a CLI that can be used against all sites on the server?
This button is disabled but I still have the same problem.
/var/www/vhosts/sitename.com/httpdocs/.htaccess: Options not allowed here
Hi Richard Anthony Secor,
Thanks for the question!
We have the following KB article with instructions on how to manage this option for all domains:
We also added a note to the resolution section of this KB article.
Rather than NOT restricting the following of symlinks, it is better to modify the .htaccess of the site causing the problem:
For situations where the error is "Option FollowSymlinks not allowed here", look for a line in .htaccess like this:
and replace it with:
The replacement option allows symlinks to be followed but only where the owner is the same, which is safe, and does not trigger the error 500.
Thanks! Problem Solved,
and the other solution? its same?
This is wrong solution which will cause security risk
Please sign in to leave a comment.