HTTP 500 Internal Server Error

  • Resolved MediBid

    (@medibid)


    13 years, 11 months ago

    I’ve read through a dozen or so forums about this issue, but found no solid resolution and many were closed as they were 3 years old. So I know there are other people out there with this same problem, which at least keeps me from feeling hopeless.

    Yesterday, added new, scheduled posts at about 4pm. Blog was fine at 6pm. By 10pm, all pages were gone, including the /wp-admin page, so I have to get in using GoDaddy dashboard.

    Looked here on forums first, found people were suggesting that I call GoDaddy. Called GD, spoke with dedicated server department, and was told that the problem looks like a PHP version error, that the server PHP and the installed WP PHP are not the same. On the server, the version is PHP 5.2.6. Came back to forums to research this, found posts asking to add
    “AddType x-mapp-php5 .php”
    to the top line of the .htaccess script in the wp-admin section. I soon realized that while my domain has an .htaccess file, the wp-admin does not. I looked for further instruction and found that I can add my own .htaccess file and suggestions for what to add to a corrupt .htaccess file that may also be causing the 500 Internal Server Error.

    After piecing together what I have found on various forum posts related to PHP and HTTP500 errors, I’ve now added an .htaccess file to my wp-admin folder that looks like this:

    # BEGIN WordPress

    <IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteBase /
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule . /index.php [L]
    <IfModule mod_security.c>
    SecFilterInheritance Off
    </IfModule>
    <Files index-extra.php>
    SecFilterInheritance Off
    </Files>

    # END WordPress

    I also tried adding the x-mapp (AddType x-mapp-php5 .php) by removing the space before the .php, adding <> brackets around it, going without the brackets, and also in various locations. With or without the x-mapp suggestion in the .htaccess file, my blog still does not work. I’ve tried every suggestion I found on a forum board and am out of ideas. Does anyone have any suggestions? Am I doing something wrong with the .htaccess file?

    blog lives at https://www.medibid.com/blog

Viewing 11 replies - 1 through 11 (of 11 total)

  • Have you checked your database? Have you tried re-uploading all files & folders – except the wp-content folder – from a fresh download of WordPress?

    Thread Starter MediBid

    (@medibid)

    I’ve checked the database and our webmaster has as well and nothing jumps out at us as a problem. I’m currently trying to find if possibly GoDaddy upgraded the PHP to 5.2.6 and if that is possibly not compatible with wordpress at all?

    Would I lose all of my posts and scheduled posts by re-uploading all files? I’m assuming that those all live in the content folder? I am not the original installer of our WordPress, but I’m sure I can find instruction forums for a re-install. Do you think it would work? I’m trying to lose as little as possible.

    WP is compatible with PHP 5.

    Would I lose all of my posts and scheduled posts by re-uploading all files?

    No – they are in your database. The wp-content folder contains your themes, uploads & plugins.

    Thread Starter MediBid

    (@medibid)

    Ok, so here’s the big question if I re-install all the files – do I need to get new information for the wp-config.php file, or will the old data work?

    No. Leave your wp-config.php file alone.

    Thread Starter MediBid

    (@medibid)

    Ok, I’ve replaced nearly every file with a fresh download of 3.0.3 and still nothing. I think the image folders are all that I have left outside of the content file. I took out the .htaccess file as part of the deletion of all old files and I didn’t add it back in since there wasn’t a file for it in the fresh download.

    How do I check to see if the PHP version matches what is on the server (5.2.6)? I know if I call GoDaddy again, they will ask if I checked.

    The PHP version where?

    Thread Starter MediBid

    (@medibid)

    You know, I think I misunderstood the support guy. I thought he was saying that I needed to check the PHP on WordPress and on the server. You already said WP is compatible with the PHP5 on the server and that is what he was asking me to check. I’ve finished the files, and the blog is still down. I can’t even get into my admin panel. So I’m once again out of ideas and will call GoDaddy.

    From the GoDaddy Dedicated Server Support guy:

    Server Concierge: The following files work without issue in the /blog folder:
    https://medibid.com/blog/readme.html
    https://medibid.com/blog/license.txt
    As such this is an issue with the coding or WordPress requires a higher php version that what is installed on the server.

    Server Concierge: I would recommend researching the issue or referring to WordPress for assistance with this issue. I have confirmed that this directory is accessible and not experiencing any issues as you can browse to the 3 files provided above via a internet browser. I would also recommend checking to ensure that the wordpress version that you have installed is compatible with the PHP version that is installed on your server which is PHP 5.2.6.

    WordPress is compatible with PHP5 and frankly, I’d expect someone from GoDaddy to know this. They host enough WordPress sites!

    Can you try a fresh install in a sub-folder with a new database? Perhaps there is a problem in the db after all. And I’d suggest you remove that php_info file asap for security reasons.

    Thread Starter MediBid

    (@medibid)

    Oops. I thought that was a standard file. Gone now.

    Ok, new database – so install the same fresh files all over again, including new content files, but in a new subfolder, or is there another step that will involve registering a new wordpress with new admin and new passwords and recreating that whole wp-config.php file?

    Thread Starter MediBid

    (@medibid)

    OH MY GOSH! The blog is back!

    Thank you for your help, esmi.

    Spoke to a new GoDaddy guy, who knew something about wordpress. He verified that as long as I can access the reame file, it was not a server error. He said to rename all of the plugins and then open the website. Now I can systematically check the plugins until I find the one that did this to my page. 7 hours of my work day gone for this issue, whatever it is.

    So – for anyone else who finds this post because they have an error: go into your files, via GoDaddy or your own FTP client and rename all of the plugin directory folders in the wp-content/plugins/ directory. No .htaccess file needed, and possibly no need to re-install all files. See if renaming each plugin file (I just renamed the directories by adding a number to the front so that I would still know which was which as I re-enable them later) fixes your issue first.

Viewing 11 replies - 1 through 11 (of 11 total)
  • The topic ‘HTTP 500 Internal Server Error’ is closed to new replies.