• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Resolved New Wordpress Site

NevilleM

New Pleskian
Since upgrading to Plesk Onyx, we noticed that when creating a wordpress site, the default folder permissions are nor right and when trying to upload a new theme, we get the following message:

Code:
The uploaded file could not be moved to wp-content/uploads/2017/04

When trying to install a plugin, the Connection Information window is loaded - we included
define('FS_METHOD', 'direct'); in the wp-config (as per Wordpress asking for my FTP credentials to install plugins) but still we got the error:

Code:
Installation failed: Could not create directory

In both cases, these are related to permissions and ownership of files. Any ideas why this is happening or is this a bug?
 
Hi NevilleM,

pls. note that additional informations are needed for investigations:

YOUR operating system
YOUR current Plesk version ( incl. #MU )

( hint: both could be easily shown with the output of the command "plesk version" over your command line! )

when trying to upload a new theme
It is recommended to use the "Plesk Wordpress - Toolkit" by now...

HOW did YOU upload the new theme? With which user? What is the output of the command:
Code:
ls -ld /var/www/vhosts/YOUR-DOMAIN.COM /var/www/vhosts/YOUR-DOMAIN.COM/httpdocs /var/www/vhosts/YOUR-DOMAIN.COM/httpdocs/wp-content

Consider to use the Pleks Repair Utility, if you would like to correct permissions:


Example:
Code:
plesk repair fs YOUR-DOMAIN.COM -y -v
 
Some more info to this post

1) We have Workpress Toolkit v 2.03 - release 327 installed.
2) The WP site was created from Domain > Wordpress > Install (Custom)
3) We tried to upload the new theme & plugins directly from WP admin

Product version: Plesk Onyx 17.0.17 Update #23
Update date: 2017/04/17 17:20
Build date: 2017/03/22 17:00
OS version: CentOS 6.4
Revision: ab6766191d3ba26e7b21255ab007fc7fc56d84c6
Architecture: 64-bit
Wrapper version: 1.2

In the meantime, we deleted the WP site and tried to recreate it. Same problem.

We also run the command
plesk repair fs YOUR-DOMAIN.COM -y -v
Same problem

the wp-content directory is 755 with owner ftpuser and Group psacln
 
Hi NevilleM,

3) We tried to upload the new theme & plugins directly from WP admin
Pls. consider to investigate your issues then with the help of the domain - specific apache+nginx - log - files, located at: => /var/www/vhosts/system/YOUR-DOMAIN.COM/logs

What happens, if you use the Plesk - Wordpress - Toolkit ( => Wordpress - Instance => "Manage Themes" ) ?


Pls. note, that some plugins and themes for Wordpress NEED additional rewrites ( either for apache and/or nginx ), when you use the combination apache2+nginx+php-fpm, which is the Plesk - recommended configuration bundle. ;) If you need help here, pls. include all of your current configuration files for the domain with issues.

In addition, pls. note as well, that even if you installed a Wordpress instance with Plesk and the Plesk Wordpress - Toolkit, managing the content and using Wordpress is not really a Plesk - related issue. ;)
 
What happens, if you use the Plesk - Wordpress - Toolkit ( => Wordpress - Instance => "Manage Themes" ) ?

Well I get a window to search for the theme but there is no option to upload the theme.

In any case, I changed from php vendor mod_php to FastCGI and WP is working correctly now.
 
Hi NevilleM,

I changed from php vendor mod_php to FastCGI and WP is working correctly now.
Just for your informations:

If you use the ( insecure! ) "mod_php" module from the PHP version of your vendor for your apache - webserver, you should be aware, that used permissions are the ones from your webserver - user/group. To be able to use this PHP-Handler without issues/errors/problems, you have to add the system - user www-data ( on Debian/Ubuntu - based systems - or "apache" on CentOS/RHEL - based systems ) to the group "psacln", because the folders INSIDE your "document root" of your vhost are set to: domain-system-user : psacln
 
plesk repair fs YOUR-DOMAIN.COM -y -v

this command fixed my two weeks old problem. thanks guys.
 
Back
Top