What you need to do

In order for a Responsive WordPress website to function the user the web application runs under, apache if you have the site configured to use mod_php or the FTP user if you have the site configured to use FastCGI in Plesk, must have read, write and execute permissions on some directories. While 777 permissions are not recommended they do not make your site more vulnerable, they can however make the scope of an exploit much larger as they make it possible for an exploited web application to modify more file than normally would be able to modify.

The solution is to set permissions on the wp-content directories requiring read, write and execute properly. In a Plesk managed environment the best practice for PHP WordPress based responsive web applications is to use the FastCGI support in Plesk which runs the site as the Plesk FTP user which has by default permissions but sandboxes the activity and scope of access to only the site directory since the FTP user for the site has no permissions to files outside of the site directory.

To change from the Apache module (mod_php) PHP handler,

Websites & Domains>
More link at bottom>
Hosting Settings for domain>

PHP support (Run PHP as [Apache Module] , PHP version [5.3.3] )


PHP support (Run PHP as [FastCGI Application] , PHP version [5.3.3] )

Click OK to commit the changes

Once this is done the files and subdirectories in the


need to have the ownerships set to

user and psacln

Group and all directories should have 755 permissions and files 644 permissions. This will allow the FTP user for the site to upload changes and for your responsive WordPress website to work seamlessly with no permissions or ownership conflicts.


Example of commands to properly set secure Plesk sandboxed PHP site directory using FastCGI PHP handler.

chown -R user.psacln /var/www/vhosts//httpdocs

find /var/www/vhosts//httpdocs -type d -exec chmod 755 {} \;

find /var/www/vhosts//httpdocs -type f -exec chmod 644 {} \;