Changing to DSO handler does not allows php to write anything

[shojib]

Hi ,
Recently I was trying to run php and apache as nobody as I have installed cloudlinux on my server .
And due to some processing limitations , many websites are running slow and some php processes are taking longer to finish , which makes the load average go up .
But with DSO I could make all the websites faster and have isolated environment from cloudlinux without mod_ruid2 , I was using suPHP on my production server .

After changing , I was getting several issues like wp media upload error , plugins, themes , core updates error (Asking for FTP) , And timthumb errors .

Is it possible to fix all the files and folders permissions on my server to use DSO module without any problems ?
Waiting for replies .
Shahriar

 

[cPanelMichael]

Hello,

What specific error messages do you see in /usr/local/apache/logs/error_log regarding this account?

Thank you.

 

[shojib]

What would be the best practice on file permissions ?
user:nobody and 755 ?

 

[cPanelMichael]

It depends on the file and your PHP handler, but generally file ownership should be "user:user" with 0644 permissions (with exceptions such as CGI/Perl files).

Thank you.

 

[24x7ss]

Hello,

Did you try changing enabling the FTP access and changing the permissions to 777 to required folders? With DSO you need to have 777 permissions to uploads folder to make it work. But you increase the chances of your website being vulnerable with this.

 

[shojib]

Hello,

Did you try changing enabling the FTP access and changing the permissions to 777 to required folders? With DSO you need to have 777 permissions to uploads folder to make it work. But you increase the chances of your website being vulnerable with this.

Unfortunately I can't connect to every ftp and change the permissions accordingly on every user account .
Any command from SSH or shell script that can do the trick ?

 

[shojib]

Guys,
I just found that recompiling with apache mod_ruid2 fixed everything !

 

[cPanelMichael]

I am happy to see the issue is now resolved. Thank you for updating us with the outcome.