WordPress and the Internal Server Error

Comments

1. Jess Planck (4 comments.) says:

   9/10/2010 at 11:58 am

   One of more unusual sources of error 500 that I’ve seen was a permissions problem. This issue I dealt with had files moved from a server where the user and group names were different and didn’t exist on the new server. Somehow the new server tried to use the old server user and groupnames. I won’t name hosting service, it was an oops moment for them This also happened once moving a site from an enterprise backup system to a new server.
2. Carrie (2 comments.) says:

   9/10/2010 at 6:36 pm

   Yep I had a weird 500 error and it suddenly went away after I changed the blog post title. And it was the only thing on the site that had that error was one lonely blog post. The good part, I only had to mess with it once to figure it out. Lucky guess.
3. cimddwc (3 comments.) says:

   9/12/2010 at 2:42 pm

   And if you didn’t change anything when these errors sometimes show up, and you’re on a really cheap shared hosting environment, they may be caused by other users using up the server resources – and resource-saving measures on your behalf might reduce the errors a little, but couldn’t prevent them.

   If, then, the support replies with text modules ignoring that you already said you didn’t change anything but giving useless advice instead, it’s really high time to find a new hoster…

Trackbacks/Pingbacks

1. WordPress Troubleshooting Series (MacManX.com) says:

   11/1/2010 at 12:03 pm

   […] WordPress and the Internal Server Error […]