SMF Development > Bug Reports
Using File Permissions brings down entire site?
AngelinaBelle:
I was using File Permissions to try to fix file permissions so I could install packages.
I was working on a fresh install of SMF 2.0RC3 in a subdirectory of my site --- http://rockhallsailingclub.org/smf2test
I'm using 1and1 shared hosting.
The file permission changes didn't seem to be happening, though wasn't getting any error messages from SMF.
I had a look at it from the command-line FTP client, and it looked like quote CHMOD has been disabled on my ftp server.
That seemed strange.
I then attempted to change the permissions on /smf2test/.htaccess to 0755 just to make sure it really wasn't working.
Suddenly, the entire website is down -- 403 errors on http:/index.php
And, to top it all off, my FTP password stopped working! I couldn't log in because I had no permission to view the root directory.
What happened? What could SMF have done that would have caused the top directory's permissions to go bad?
Kill Em All:
Your website seems to be working fine to me. As a general rule, all folders should be 755 and all files should be 644.
AngelinaBelle:
It's all better now. The master acount owner fixed the permission.
I am still wondering how using SMF's File PERMISSIONS in a subdirectory caused permissions to be removed from the FTP login root down.
That seems like a bug.
From now on, if I need to change permissions, I'm doing it by hand.
One file at a time.
Kill Em All:
That sounds more like a problem with the program you are using, not SMF. I don't think SMF would do that.
I am going to mark the topic solved, please feel free to unmark it solved if you have further questions. :)
AngelinaBelle:
Actually, I think SMF DID that. I didn't believe it the first time it happened. So I tried again another day. Same thing happened -- try to change the permission on a file in the SMF root, and the permissions for the entire site went to 000.
I wonder if the master account owner can change CHOWN the ftp login directory, then CHMOD to 775, to prevent this accident from ever happening again.
Nobody else has ever seen this behavior?
Navigation
[0] Message Index
[#] Next page
Go to full version