[Solved] 500 Error Handling

[Guest Geoff]

Sometimes, every now and then I get a 500 error on my site. It is due to some htaccess file not being right, some script not configured correctly, and thats expected.

 

Whats really annoying, though, is that when a 500 error comes up, there is really no way to find out what caused it. I even look at my error logs in cpanel, and it seems that they are just fine. This is quite frustrating, as I would like to know what is causing the error.

 

Is there any way that I could find out what causes a 500?

[Wizard]

Pretty sure there's nothing you can do from your end. This support request is being escalated to our root admin.

[Fernando Ferenz]

site: http://www.orkuttools.heliohost.org/

User : ferenz

 

Orkut Tools site has several daily visits and depending on how many visitors enter the server error 500 how can I solve this problem.

sorry for the misunderstanding I am Brazilian aew speak half wrong

[Wizard]

site: http://www.orkuttools.heliohost.org/

User : ferenz

 

Orkut Tools site has several daily visits and depending on how many visitors enter the server error 500 how can I solve this problem.

sorry for the misunderstanding I am Brazilian aew speak half wrong

Stop posting everywhere. Stick to here: http://www.helionet.org/index/index.php?showtopic=7534

[Guest Geoff]

Well, right now the page that is giving me the error:

http://geoffish.heliohost.org/search/admin/setup.php

 

Ill tell you the application that I am using is still in beta, so It might have some problems, that is OK. But what I would expect is a PHP error message telling me what line of code is causing the error, not a 500 Error.

 

I don't even know where to begin, as there is 50 possible files the error could be triggered in. All that I am asking for is a somewhat helpful error message, hinting at what to fix, rather than just leaving me clueless.

 

Thanks for all your help in making this the best hosting available!

 

Geoff

 

[Ashoat]

Sorry, but there's no way we can do that

 

All errors are written to a global error_log on our system. The cPanel "Error Log" just searches this log for messages it knows are directed at you. However, 500 errors are usually split up across a couple lines, and the important lines don't have the identifying information. It's the fault of cPanel's search for not being able to pick those up, but the only way you can get access to them is to ask me to take a look.

[Guest Geoff]

--Comment Removed by User--

[Ashoat]

Closing due to inactivity.