Internal Server error 500

i’ve been battling this same problem for the last few days…
i tried upgrading to v1.5 from 1.2.2 and it didn’t work, kept getting the Interal Server Error 500. so, i rolled back a to a backup of my v1.2.2 install.

Today i just tried to do the upgrade again, totally from scratch other than the wp-config.php and the database itself. at first everything looked to be working fine. came back to it 10 minutes later and got a freakin comment spam and the website was hosed again, back to the internal server error crap.

i just logged in and deleted that comment, turned off comment posting, and changed permissions on the index.php to 755. now the site looks normal again.

i’m still working on narrowing down the true fix for the problem and i haven’t tried to post myself yet.

the v1.5 upgrade saga continues…

A 500 error is generic error which translates as, “The actual error could not be displayed in your browser. Please check your server error log for the actual error.” We can’t do or say anything without knowing what that error is.

::blink:: Totally of a random, when I clicked over to this topic I got a 500 error!

i fixed my problem after pouring through several other threads in the forum. i had to change the permissions of the following files to 755 using chmod:
index.php
wp-blog-header.php (not sure if this one was necessary, but i did it anyways)
wp-content (chmod’d all the files inside to 755 using my ftp program)

i haven’t seen the internal 500 error since then.

We started getting the same:
Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator, [email protected] 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.
Apache/1.3.33 Server at https://www.thenextwave.biz Port 80

We get the internal 500 error in our log-
but, if we CUT the post to something short-
it posts!

We just upgraded to 1.5 to try to fix it-
same problem-
we think it may have to do with PHP execution time.

Any suggestions

well- after some sleuthing-
it was the word CD in the post-
and our server admin person told us this:
“The error you are getting while typing cd is due to the mod_security feature enabled in the server. The mod_security module does not allow users to type system level commands. The command cd is used as a change directory command. This is why the internal server error 500 occurs when typing cd in wordpress. Please try to replace the word cd with compact disk. Hope this helps. Thank you.”

Go figure- secret words that shut down wordpress.
Another guy had the word “Form” screw his up-

since this works on some servers- does anybody know what you have to do to change the server- or what a complete list of trip words is?

thanks

found some great instructions on google-
Consider setting ‘SecFilterInheritance’ to ‘Off’ for certain locations, by including it within a ‘Location’ block. For example, I have mine set up not to scan mt.cgi, because occasionally users post blog entries that contain words that are on the blacklist (e.g. ‘poker’), and I want them to be able to post whatever they want. Remember, mod_security will scan everything that gets posted to your server, whether it’s posted by a legitimate user logged in to Movable Type, or a comment spammer.

here is the link https://prwdot.org/docs/blacklist_to_modsec.html

Arg. I was getting more and more 500 errors over the last week and finally, my blog wont load at all, today. I can log into the admin side.. it just won’t display on the index. I tried updating to 1.5.1.1 but that didn’t help.

As a side note, I have found that posting amazon links in my posts causes it to take a LONG time to post… and it finally comes back with a 500 error.

i just upgraded to 1.5. from 1.2 and got the dreaded ‘Internal Server Error’ too.

for about a half a minute I had a nice neat new install and when I tried to go check my permalink structure (like it says to on the codex), that’s when the error popped up.

Now I get it everywhere… on the index.php, when I go to wp-admin, whatever. Nothing let’s me beyond that message.

I tried the chmod trick, orginally I was all 000 and I changed everything mentioned above to 755.. no luck.

Fyi – I’m on dreamhost if that mattters.

url is https://www.parmet.net/pr

HELP!!!!

I have since upgraded to 2.0.1 and I’m still getting them constantly. I started, this morning, screwing around with the php.ini to up some of the time limits and it SEEMS to be helping…

max_execution_time = 60
max_input_time = 90

up from 15 and 60. Although I have gotten 500 errors this morning, the next page loads ok whereas inthe past, once I get a 500 error, everything for the next 10 minutes or so would get a 500 error. I’m going to keep tweaking and I’ll post again if I land on something that gets rid of them altogether.

I have installed a brand new WP 2.0.1. It’s worked fine, until I have changed the permalink structure. From then I only have 500 Internal Server Error, and I can’t change this. I have taken a look to that option in the Database, and it’s correct, but I can’t run the blog.

cheito:
delete the htaccess
log into admin
remove the permalink structure that causes the error

Have you searched for your host’s name here or asked them about this ?

Update : adjusting the timeouts in the php.ini file seems to have remedied the 500 server errors I’ve been getting since upgrading to version 1.5. I upped them one more time to :

max_execution_time = 90
max_input_time = 90

I get 500 errors EVERY now and then still but its usually on a really query intensive page inside the interface rather than a page that visitors might see.

I was able to confirm with my host that the errors I was getting were due to php processing load on that server. Processing requirements seem to have gone up with WP 1.5.

I dont know what causes the error, but if you CHMOD the entire folder to 755, the error disappears… Try it out ??