I've been getting quite a few internal server errors when I post lately. Usually the post goes through and the Watch burps when it tries to send me the confirmation, but this time I'm not sure my post worked at all. Here's the text of the error message:
Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator, webmaster@kevinswatch.ihugny.com and inform them of the time the error occurred, and anything you might have done that may have caused the error.
More information about this error may be available in the server error log.
Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.
I almost always use the Quick Reply box, in case that has anything to do with it.
EZ Board Survivor
"Dreaming isn't good for you unless you do the things it tells you to." -- Three Dog Night (via the GI)
I've been getting them sometimes too. And the "critical error: could not connect to php database" or something. Far as I know there's nothing to be done. Server hiccups.
Quite often my browser's hanging and coming up "couldn't find server" on the Watch, and I have to refresh a few times before it loads the site. Been doing it for about a week.
Murrin wrote:Quite often my browser's hanging and coming up "couldn't find server" on the Watch, and I have to refresh a few times before it loads the site. Been doing it for about a week.
same here.
Avatar wrote:But then, the answers provided by your imagination are not only sometimes best, but have the added advantage of being unable to be wrong.
Murrin, cannot find server errors are rarely if ever a problem with the site. They are a problem with your network. Possibly due to a DNS error, or possibly due to a connection timeout.
Hrm. Any suggestions then on what can be done to deal with such problems? Nothing changed in my router or computer settings, it just started acting funny suddenly.
I also get these server not found errors from time to time.
I think it has to do, not with the network router you own, or even your modem, but your internet service provider. They are the ones who provide you with (local) internet name resolution, and my theory is that the process that performs this action can time out.
Comcast is my ISP. I have notices that it happens most often during what I assume are peak usage times for cable in general, 7-10 PM weekdays.
I blame the server. I think they've tightened up on some settings so it may get frazzled at busy times for the server.
If it stays a problem then I'll check into it and ask them what's happening but I still think they're a bit pissy for the last two times I nearly destroyed their server (haha)
haha I use the Royal "I"....which means Avatar as well
I've had a look at the most recent error logs and I can't see anything specific - in fact there's hardly an error linked to KW.
I'm beginning to wonder if our 900 meg database isn't beginning to crack under the load.
We probably really do need to move to Phpbb3 - I just don't know how we're going to manage that considering I couldn't sort out the database the last time. Maybe we need professionals haha