500 - Internal Server Errors (CHMOD Issue)

[DarkBlood]

I felt like putting it in the Free Hosting Discussion because it usually happens on free hosts.

On some of my hosts, I've been getting problems where when I chmod a folder to 0777 (or 0755), and I navigate to a page in that folder... I get a 500 - Internal Server Error (It also says at the bottom: "Additionally, a 404 Error Happened with ErrorDocument.")

Can someone alleviate or elaborate as to what the problem is? I can't edit templates via a forum AdminCP because of this problem.

[suraj4u]

It normally occur to the mismatch of version ..Such as mysql ,php versions......

[DarkBlood]

It normally occur to the mismatch of version ..Such as mysql ,php versions......

Thanks, but that's not all it happens on though. I'll wait for more replies on this one to better determine the problem.

[DanQ]

The host could have SuExec installed, that would cause folder's with permissions 777 to "Internal Server Error 500".

Dan

[Decker]

Could be ownership problems too, how are you chmod'ing (do you login as the actual user)?

[DarkBlood]

Could be ownership problems too, how are you chmod'ing (do you login as the actual user)?

If I chmod in CPanel or via FTP, this happens. Also, if I change the CHMOD back to the default (644) it still gives me the 500 error.

[Decker]

Sounds like ownership issues.

Does your FTP client show you a column that says 'owner' it will either have a login name or (usually) a 5 figure number?

If it does check all files say the same name/number.

[krakjoe]

my money is on phpsuexec ....

mismatched versions of php and mysql do NOTHING ... NOTHING ....

[DarkBlood]

Sounds like ownership issues.

Does your FTP client show you a column that says 'owner' it will either have a login name or (usually) a 5 figure number?

If it does check all files say the same name/number.

It has a column that says owner. But by default, the value for it is as follows


Owner Permissions
Read Write

Group Permissions
Read

User/Public Permissions
Read

Otherwise: 644 where owner is set to 6.

[Decker]

my money is on phpsuexec

Nah, or at least compiled in correctly shouldn't cause that.



mismatched versions of php and mysql do NOTHING ... NOTHING ....

Didn't want to be the first to mention it as it's a given :lol:
What the hell would be a 'matched' set of php & MySQL be anyway :confused4

[Decker]

Otherwise: 644 where owner is set to 6.

No I was hoping for another column, with actual file/folder information as to the owner not the owner permissions.

Do you have shell access?

[DarkBlood]

Do you have shell access?

If you mean terminal, no I do not.

[Decker]

What FTP clients do you have access to?

[DarkBlood]

What FTP clients do you have access to?

CPanel File Manager and FileZilla.

[krakjoe]

Nah, or at least compiled in correctly shouldn't cause that.




Didn't want to be the first to mention it as it's a given :lol:
What the hell would be a 'matched' set of php & MySQL be anyway :confused4

It would cause that decker, world writable permissions are not available with phpsuexec enabled, compatible modes include 600, 700 and 755 ... only on some files can u use 644 with phpsuexec enabled ... also .htaccess directives do not work under phpsuexec same 500 error ...

777 permissions are redundant when phpsuexec is enabled, so long as the file is writable by the owner php can read and write it anyway ....

[Decker]

He already said 755 did it too so I discounted on that mainly. Seen it happen many times where you need to redo ownership (or sysadmin does) being the most likely. If it is suexec he has a problem.

No a big fan of either cPanel file manager or FileZilla, try grabbing a trial of CuteFTP or WSFTP.

[DarkBlood]

He already said 755 did it too so I discounted on that mainly. Seen it happen many times where you need to redo ownership (or sysadmin does) being the most likely. If it is suexec he has a problem.

No a big fan of either cPanel file manager or FileZilla, try grabbing a trial of CuteFTP or WSFTP.

If it's WSFTP, it would be WS_FTP LE, the free version... not the one from the website itself. I'll check out CuteFTP, but it's likely that I'll un-install it right after I get this problem sorted out (I'm not buying anything just because of this.)

Edit: I have the free trial installed, so what should I do now?

[Decker]

Edit: I have the free trial installed, so what should I do now?

Of which one?

If it's Cute, you should see columns (or similar) for your files, name, size, type, modified, attributes, decription, owner

The last one (in bold) is the one I'm interested in.

[DarkBlood]

Of which one?

If it's Cute, you should see columns (or similar) for your files, name, size, type, modified, attributes, decription, owner

The last one (in bold) is the one I'm interested in.

iyeru42 is the owner, which is my username. Meaning that the "owner" column is not at fault. So it may be what krak said.

[Decker]

Hmm, did you try your host? Seems very strange.

With Joe on the possible but still not convinced.

[parisdns]

Upload the file(s) in binary mode...

[Decker]

I'm blinded by the obvious - NOT!

Paris in SL your okay on stuff but this is a crap one.

[DarkBlood]

Hmm, did you try your host? Seems very strange.

With Joe on the possible but still not convinced.

My host likes to idle, so I wait hours for a response via MSN.

[DarkBlood]

And aparrently my host doesn't know the problem, so he's e-mailing his own host to figure out the problem.

Also, I found this:

Debugging

Debugging a suexec problem can be frustrating, particularly since almost any problem with a CGI script in a suexec-enabled environment turns out to be related to the wrapper.

The typical warning signal of a suexec problem is a request for a CGI script that results in a '500 Internal Server Error' page. The appropriate response behaviour to such an error is to look in the server's error log. Unfortunately, because the wrapper is applying its own restrictions and rules on the script, the server log may be quite unrevealing, containing only a single line such as the following for the failed request:

[Sun Dec 26 20:02:55 1999] [error] [client n.n.n.n] Premature end of script headers: script

The real error message will be found in your suexec log (which is located at /usr/local/web/apache/logs/suexec_log, according to the assumptions section of this article). The suexec error message may look like this:

[1999-12-26 20:02:55]: uid: (user/user) gid: (group/group) cmd: test.cgi
[1999-12-26 20:02:55]: command not in docroot (/home/user/public_html/test.cgi


Here are a couple of other common suexec error messages:

directory is writable by others: (path)
target uid/gid (uid-1/gid-1) mismatch with directory (uid-2/gid-2) or program (uid-3/gid-3)
From: http://apache-server.com/tutorials/LPsuexec.html

[DarkBlood]

Also, WP-Cache plugin can give 500 Internal Server Errors, I just found it out.

[h0ster]

I've learned it's generally best to disable phpsuexec when running the first config, it can cause a lot of problems that can be hard to trace back.