• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Fix file owner/group post migration from Plesk 10

Chris1

Regular Pleskian
Hello,

We have recently migrated some web hosting accounts from Plesk 10 server where quite a few accounts were using PHP via the Apache module whereas now on the Plesk 12.5 server they are using either FastCGI or FPM.

Some users files and folders are still owned by the Apache user after migration which causes problems when our customers try and update their software such as Wordpress.

Is there a way to fix file owner/groups across the whole server so that all users files are owned by the system user and not the Apache user?
 
Ahh excellent, I didn't know that tool existed. Is it possible to do it on just one vhost to test?
No, this is not possible with that command.

If you wish to "test" that on one (sub)domain, you have to use a command like:

Code:
chown -R SYSTEM-USER-OF-THE_DOMAIN:psacln /var/www/vhosts/YOUR-DOMAIN.COM/httpdocs

or

chown -R SYSTEM-USER-OF-THE_DOMAIN:psacln /var/www/vhosts/YOUR-DOMAIN.COM/subdomain.YOUR-DOMAIN.COM

Pls. change "SYSTEM-USER-OF-THE_DOMAIN" to the correct system-user of the domain.​
 
No, this is not possible with that command.

If you wish to "test" that on one (sub)domain, you have to use a command like:

Code:
chown -R SYSTEM-USER-OF-THE_DOMAIN:psacln /var/www/vhosts/YOUR-DOMAIN.COM/httpdocs

or

chown -R SYSTEM-USER-OF-THE_DOMAIN:psacln /var/www/vhosts/YOUR-DOMAIN.COM/subdomain.YOUR-DOMAIN.COM

Pls. change "SYSTEM-USER-OF-THE_DOMAIN" to the correct system-user of the domain.​

Hi @UFHH01,

I find that when I run the above commands, it will change the group of the "httpdocs" directory to "psacln" which causes a problem when trying to load their website. I needed to change the group on the "httpdocs" directory back to "psaserv" for the website to be accessible.
 
Hi Chris1,

sorry... yes... I didn't mention, that "psaserv" should be still the owner of the documentroot. Pls. add as second command to the above line:

Code:
&& chown SYSTEM-USER-OF-THE_DOMAIN:psaserv /var/www/vhosts/YOUR-DOMAIN.COM/httpdocs
 
Back
Top