Never go below 600 or you will not be able to make changes to the file yourself

“never go below 600 or you will not be able to make changes to the file yourself.”
What does it mean? I’m scared to do anything. How do I avoid running into this problem. I’ve been searching and finding answers that make no sense, like “use FTP” duhhh… Can anyone explain in plain English what it means and how to avoid it?

It is the chmod number, basically a number which determines permission (read, write, execute) for 3 type of user (owner, group and user)

600 means read and write permission only for the owner
Once the owner of file loses permission to write, nobody but the system admin can change the chmod number & make changes to the file.

A way to avoid such problem is simply not to touch the chmod number on the file manager.


“not to touch the chmod number on the file manager.”


Don’t feel too terrified on this. :sunglasses:
Although to some reason you can no longer revert once you went below 600 here(which should not be the case in most standard linux systems),you can still safely delete the file below 600(since you have full read/write access to the folder contains it!).I have tried this whole thing out and it’s ok.The file can be deleted. :grinning:
While @Ziverre do get a point:Never touch anything that you don’t know the meaning.


Thank you… I feel much better now :]


As a general piece of advice: don’t ever touch the chmod settings when using our hosting. With over seven years and millions of websites of experience on this platform, I have never encountered a single issue that could be solved with chmod settings. On our hosting, PHP code runs with the same permission as you have while managing manage your files, so PHP always has access to read and write files on the site.

If you have a case where you want to give PHP access where it doesn’t have, it means you cannot provide it. And if you have a case where you want to restrict access from PHP to certain files or directories, you can’t do it without locking out yourself.

So if you’re having an issue and you think it will be solved by it: it probably won’t be.

I have seen numerous cases where people fiddled with the chmod settings and ended up locking themselves out of their own files. So please just don’t touch the setting.


Sounds like a good plan to me thanx. I was just curious because I noticed the warning on one of the pages.

I’m curious if altering Chmod on this hosting (and probably any hosting provider based on MOFH), then why is changing it via filemanager possible? Shouldn’t it be disabled?


I’m not sure if the file manager supports disabling the chmod function, but maybe it would be better if we did. Maybe it’s possible to disable the FTP function as well. I’m going to pitch it to iFastNet and see what’s possible.


Judging from the tracker on my site, it seems like one of you is in the Philippines… that’s where I am. haha

1 Like

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.