FIXED: The wp-content folder does not show itself via FTP in Plesk 12 and CentOS 7

Screen Shot 2014-12-24 at 21.49.49

I’ve noticed a weird bug in Plesk 12 on CentOS 7: when you connect via FTP, the wp-content folder does not show up – all other folders can be seen as usual. It’s a rather crucial folder for WordPress users.

At first I had suspected a problem with the ProFTP service which is not the stock version, but a specially compiled version for use with Plesk, and Plesk takes care of this system services (it’s called psa-proftpd in case you’re interested). But ProFTP is not the problem.

Thanks to the amazing Sergey Lystsev from Parallels for letting me know that the issue is instead with SELinux: when it’s used in Enforcing mode (which is the default), wp-content does not show itself via FTP. Switching it to Permissive mode or disabling SELinux altogether solves the problem.

The entire issue will be fixed in the next release of Plesk, and it’s already working in the latest update to the Plesk Preview 12.1.13. CentOS 5 and 6 are not affected.

How do we fix it, Cap’m?

To disable SELinux on CentOS 7 we can use this:

setenforce 0

Or, to switch to permissive mode, use this:

setenforce permissive

Now we’ll need to restart the xinetd service as well as Plesk for the changes to take effect:

systemctl restart xinetd.service
service psa stopall
service psa restart

Connect to your site via FTP and see if the wp-content folder shows itself.

To permanently change the SELinux configuration so that it survives a server restart, check out my other article here:

Jay is founder of WP Hosting, a boutique style managed WordPress hosting and support service. He has been working with Plesk since version 9 and is a qualified Parallels Automation Professional. In his spare time he likes to develop iOS apps and WordPress plugins, or drawing on tablet devices. He blogs about his coding journey at and

You can leave a comment on my original post.