FAIL Checking read permissions on content directory FAIL Checking write permissions on content directory

Permissions on the content directory and temp paths are vital for the operation of the control panel. If you see an error in your system healthcheck such as the one below, then the directories are most likely owned by an account other than root or otherwise encountering issues.

FAIL Checking read permissions on content directory
FAIL Checking write permissions on content directory

A common reason for this test to fail is if you have moved the Media Content Directory to a new location. Should these checks fail then you should ensure that all paths are owned by “mediacp” system user, by running the following command:

chown mediacp:mediacp -R /usr/local/mediacp/;

If these do not resolve the issue you can use ls -l to investigate your mediacp directories and contact our helpdesk for further assistance:

Open Support Ticket

  • 0 Users Found This Useful
Was this answer helpful?

Related Articles

Removing database table prefix to improve stability on older installations

The database table prefix has not been a default for some years now and can often cause issues...

Remove database table prefix

A database table prefix was originally used in the MediaCP software many years ago and has since...

Fast DNS resolution and connection to license server failed test

The System Health check has failed the following test: Fast DNS resolution and connection to...

Got error 28 from storage engine

You may see this error Got error 28 from storage engine when accessing the Media Control Panel....

OpenVZ virtualization

During the installation or upgrade of MediaCP you might receive the following notice: ERROR:...