Full Version: PHPsuexec causing 500 errors on my site
Apparently my web host has applied the PHPSuexec to the server, and its causing numerous errors on my site. I followed the instructions I found in other threads in this forum regarding HTMLPerms, and it didn't help. The only way I could bring my site back from the dead is to manually set permissions to 644. But naturally when I post a new entry the site goes CRASH once more. Is there something I am overlooking still? Or is this strictly a problem that only my web host can resolve. I think I read something about possible missing Perl modules in certain Cpanel upgrades....could this be what's going on?
Have you tried chmod'ing your directories where you publish your blog/archive to, to 777?
Also, there's a way to get around this - try to find the mt.cfg file and look for the following lines:
#HTMLPerms 0777
#UploadPerms 0777
Delete the # sign, and try it it works for you.
Also, there's a way to get around this - try to find the mt.cfg file and look for the following lines:
#HTMLPerms 0777
#UploadPerms 0777
Delete the # sign, and try it it works for you.
Yes I've already tried that and it doesn't work. The problem is that even when I CHMOD the directories to 777, the individual entry archive files still remain broken.
I just added phpSuExec to my server and this is what I had to do to get MT to work properly:
1. open MT.cfg and find these lines:
2. Remove the "#" from the 4 settings (Starting with "DBmask 0022")
3. Save and re-upload the file.
4. Use a good FTP program (like Flash FXP or SmartFTP) to connect to your server. CHMOD the folder that has your ARCHIVES in it to 0755 (also CHMOD all the files/folders benath it to 0755).
5. Once that is done it should all work correctly. If not you might try changing the "HTMLPerms" to 0755 in the mt.cfg.
*Pretty much when you turn on phpSuExec it means that php scripts cannot run as "nobody" which in turns makes each site run their scripts as that "username", which means not "everyone" can write to all the files. Simply put, you cannot use 0777, you use 0755 instead, or you will get 500 errors.
~Riika
1. open MT.cfg and find these lines:
CODE
# When creating files and directories, Movable Type uses umask settings to
# control the permissions set on the files. The default settings for file
# creation (HTMLUmask, DBUmask, and UploadUmask) are 0111; for directory
# creation (DirUmask), the default is 0000. You should not change these
# settings unless you are running MT under cgiwrap or suexec, or some other
# scenario where the MT application runs as you; in addition, you should not
# change these settings unless you know what they mean, and what they do.
#
# DBUmask 0022
# HTMLUmask 0022
# UploadUmask 0022
# DirUmask 0022
# control the permissions set on the files. The default settings for file
# creation (HTMLUmask, DBUmask, and UploadUmask) are 0111; for directory
# creation (DirUmask), the default is 0000. You should not change these
# settings unless you are running MT under cgiwrap or suexec, or some other
# scenario where the MT application runs as you; in addition, you should not
# change these settings unless you know what they mean, and what they do.
#
# DBUmask 0022
# HTMLUmask 0022
# UploadUmask 0022
# DirUmask 0022
2. Remove the "#" from the 4 settings (Starting with "DBmask 0022")
3. Save and re-upload the file.
4. Use a good FTP program (like Flash FXP or SmartFTP) to connect to your server. CHMOD the folder that has your ARCHIVES in it to 0755 (also CHMOD all the files/folders benath it to 0755).
5. Once that is done it should all work correctly. If not you might try changing the "HTMLPerms" to 0755 in the mt.cfg.
*Pretty much when you turn on phpSuExec it means that php scripts cannot run as "nobody" which in turns makes each site run their scripts as that "username", which means not "everyone" can write to all the files. Simply put, you cannot use 0777, you use 0755 instead, or you will get 500 errors.
~Riika
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.