Articles in this section

See more

A website hosted in Plesk shows 500 Internal Server Error: Option FollowSymLinks not allowed here

Avatar
Kuzma Ivanov
Updated
Follow
Plesk for Linux kb: technical ABT: Group A

Applicable to:

  • Plesk for Linux

Symptoms

  • 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

Cause

The option Restrict the ability to follow symbolic links is enabled at Domains > example.com > Apache & nginx Settings.

Resolution

  1. Log in to Plesk.

  2. Go to Domains > example.com > 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.


    Screenshot_2020-12-10_Apache_nginx_Settings_for_example_com_-_Plesk_Obsidian_18_0_30.png

Comments

7 comments

Sort by Date Votes
  • Avatar
    A Sieber

    Solved our problem. Thank you.

    0
    Comment actions Permalink
  • Avatar
    david

    Problem Solved ! Thanks 

    0
    Comment actions Permalink
  • Avatar
    Ernesto

    Solved my problem!

    0
    Comment actions Permalink
  • Avatar
    Richard Anthony Secor

    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?

    0
    Comment actions Permalink
  • Avatar
    Deniz Mert

    This button is disabled but I still have the same problem.

    /var/www/vhosts/sitename.com/httpdocs/.htaccess: Options not allowed here

    0
    Comment actions Permalink
  • Avatar
    Kuzma Ivanov (Edited )

    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.

    0
    Comment actions Permalink
  • Avatar
    Faris Raouf

    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:

    Options +FollowSymLinks

    and replace it with:

    Options +SymLinksIfOwnerMatch

    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.

    0
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request

Related articles