How to debug 500 Internal Server Error
3 posts
• Page 1 of 1
How to debug 500 Internal Server Error
I have a PHP app that I am running in Visual Studio 2013 and am using PHP Tools.
The app starts up, runs several PHP pages and then errors out with an Internal Server Error (500).
I have not been able to debug this. Is there a way to see more detailed information about the error?
When I put a breakpoint on the page, the breakpoint is never hit. So I think that somehow, IIS Express is not able to find the page. But the page is in the directory so it doesn't make any sense.
So is there any way to find out what the error was exactly?
Greg
The app starts up, runs several PHP pages and then errors out with an Internal Server Error (500).
I have not been able to debug this. Is there a way to see more detailed information about the error?
When I put a breakpoint on the page, the breakpoint is never hit. So I think that somehow, IIS Express is not able to find the page. But the page is in the directory so it doesn't make any sense.
So is there any way to find out what the error was exactly?
Greg
- gregoryagu
- Posts: 9
- Joined: October 4th, 2013, 10:31 am
Re: How to debug 500 Internal Server Error
Here is how I found the exact error:
Run Phpinfo.php
Look under the "error_log" for the error log location.
Open error log and find error.
In other words, the built-in PHP server uses the same log as PHP.
Run Phpinfo.php
Look under the "error_log" for the error log location.
Open error log and find error.
In other words, the built-in PHP server uses the same log as PHP.
- gregoryagu
- Posts: 9
- Joined: October 4th, 2013, 10:31 am
Re: How to debug 500 Internal Server Error
Hi Greg,
Thanks for the question and providing the answer as well. Most of the fatal exceptions/errors break by the debugger by default. But some of them happen even before the debugger is initialized. e.g. parse error on first page.
Thanks,
Thanks for the question and providing the answer as well. Most of the fatal exceptions/errors break by the debugger by default. But some of them happen even before the debugger is initialized. e.g. parse error on first page.
Thanks,
Miloslav Beno │ DEVSENSE s.r.o. │ @miloslavbeno │ miloslav@devsense.com
-
Miloslav Beno - Posts: 1252
- Joined: January 7th, 2012, 8:36 pm
3 posts
• Page 1 of 1
Who is online
Users browsing this forum: No registered users and 112 guests