MyBB Community Forums

If you've read instructions to CHMOD everything to 777, it won't have been written by us.

I'll say the same thing I say every time someone brings this up; 666/777 is necessary on a lot of servers. 664/775 and 646/757 will not work on a lot of servers. If we tell people to try 664/775, and if that doesn't work try 646/757, and if that doesn't work try 666/777, people just get confused about having a mass of numbers thrown at them and they have no idea what any of it means. Plus, anybody who is on a server that is going to let them change the file ownership is probably competent enough with web administration to know to do that anyway.

just need to find a host that is running suhosin and suphp and will properly configure your account with openbasedir checks so that you can run 644 on files and 775 on folders under your own account name and the problem is solved.

however, as stated many times in this thread, its not very common practice for shared hosts (though they are the most likely target for exploits and vulnerabilities), a VPS is better as you should be able to setup more protections and a dedicted,there is no reasonto not be running such a setup

If your host runs PHP as the account owner (suphp, or CGI with CGIs ran with the account owner' uid) you can chmod things like inc/config.php 700, 600, 500 or 400 without issues.