10.4 sets user as apache

[scottdave]

Hi Since I have upgraded to the latest version 10.4, evertime i load a new wordpress site and domain through the panel the site user is set to apache and i cannot have any file permissions.
Also I have to restart apache webserver to see the site.
If i change anything it says it will come into effect after 16660 minutes.
I have to get a server guy to change the user everytime, he said it is a bug in plesk.

Parallels Plesk Panel v10.4.4_build1013111102.18 os_CentOS 5

Linux 2.6.18-194.26.1.el5

 

[EdwardDekker]

Use chmod to change user permissions.

chmod ftpuser:psacln /var/www/vhost/domain.tld/httpdocs/*

 

[StefanStone]

And for the 16666 minutes problem do this:

Go to admin panel -> Tools & Settings -> Server Settings. Here is an "Apache restart interval" setting. Change it to 0.

 

[scottdave]

Thanks for replies still need to know the main thing though everytime I setup a new domain it sets Apache as the user??
I don't know ssh at all really so cant just go and change these things.

Would of rather stayed with the previous version if this one has problems.

Can this one be fixed by me for good or is it waiting for an update?

Regards Scott

 

[EdwardDekker]

Thanks for replies still need to know the main thing though everytime I setup a new domain it sets Apache as the user??
I don't know ssh at all really so cant just go and change these things.

Would of rather stayed with the previous version if this one has problems.

Can this one be fixed by me for good or is it waiting for an update?

Regards Scott

Set FastCGI mode as environment of your domain at your general preferences.
Creates more isolation and allowed the domain not to use Apache as user.

 

[scottdave]

Thanks for the help your answers were spot on.
Cheers Scott

 

[SibProgrammer]

If i change anything it says it will come into effect after 16660 minutes.

I want to understand the root cause of this particular problem. Did you use "migration manager" before?

 

[StefanStone]

I want to understand the root cause of this particular problem. Did you use "migration manager" before?

I had this problem too. I migrated from Plesk 10.2 (without transfering server settings)