On October 19, 2021, we have enabled single-sign-on for our Plesk Support Center to provide a seamless login/account experience. This implies that you’ll be able to use a single account across any of our web-facing properties.
If you had already registered your account at MyPlesk.com/Plesk360/Platform360 please use one for login. Otherwise please re-register it using the same email address as your existing Zendesk login (support account). It’s essential that you use the same email address on our support center to ensure that your tickets stay attached to the same account.

Articles in this section

See more

How to restore default permissions in virtual host directory on Plesk for Linux?

Avatar
Taras Ermoshin
Updated
Follow
Plesk for Linux kb: how-to ABT: Group A FR:PPM-2855

Applicable to:

  • Plesk for Linux

Question

How to restore default permissions in virtual host directory on Plesk for Linux?

Answer

Note: solution for Plesk for Windows is available in the article How to restore default permissions on a domain in Plesk for Windows?

Since Plesk Obsidian 18.0.35, it is possible to change files and directories permissions in the Plesk interface:

  1. Log into Plesk.
  2. Go to Domains > example.com > File Manager.
  3. ClickScreenshot-2017-12-30_File_Manager_for_example_com_-_Plesk_Onyx_17_5_3_1_.pngnext to a directory or a file and click Change Permissions.
  4. Set the permissions, enable the option Change permissions recursively if necessary, and click Save or Save and resume to apply the changes:
    screenshot.1.png

Note: The recommended permissions are 755 for directories (Read, Write, and Execute for owner, Read and Execute for group and others) and 644 for files (Read and Write for owner, Read for group and others).

In the command-line interface

  1. Connect to the server using SSH.

  2. Run the following commands:

    Note: substitute example.com with the real subscription name and user_example with the system user of the subscription.

    # find /var/www/vhosts/example.com/httpdocs/ -type f -exec chmod 644 {} \;
    # find /var/www/vhosts/example.com/httpdocs/ -type d -exec chmod 755 {} \;
    # find /var/www/vhosts/example.com/httpdocs/ -type f -exec chown user_example:psacln {} \;
    # find /var/www/vhosts/example.com/httpdocs/ -type d -exec chown user_example:psacln {} \;

Comments

4 comments

Sort by Date Votes
  • Avatar
    F L E X 2 0 0 0 2 1 0 3

     Why do some files lose their rights at all? What is or can be a reason?

    0
    Comment actions Permalink
  • Avatar
    Ivan Postnikov

    @F L E X 2 0 0 0 2 1 0 3

    Hi!
    Usually, this does not occur. In case you use CentOS, consider using audit.

    Also, make sure you do not have any malware on the server.

    0
    Comment actions Permalink
  • Avatar
    Mario

    Hi, 

    In case of "user_example" what would you recommend? not root right?

    Also, how to avoid this happening in new installations? We by default use a custom WordPress media uploads folder, as ~/wp-uploads/ kind of sucks (sorry Matt), and this issue always pops out on custom WP folders in brand new installations.

    Thanks

    0
    Comment actions Permalink
  • Avatar
    julian bonpland mignaquy

    @Mario

    You can find "user_example" (system user) in Domains > example.com > System user:
    As my colleague mentioned this does not happen normally. I recommend using audit to monitor permissions changes. Also, if you create custom folders make sure they have 755 permissions.

    0
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request

Related articles