HTTP 500 Error after update

  • Hi guys, this is my first post so please be gentle.

    I have just updated my WP to 3.5.1. Due to some odd behaviour regarding FTP on my Plesk Panel I have done a manual update rather than using the automatic feature.

    WP is installed in a subdomain on my server and was working fine before the update. Since the update when visiting the URL https://dev.avataruk.com I get an HTTP 500 error.

    I managed to perform the update without any problems, and I was able to run the Database update script afterwards as well. I can still log into the admin panel without any problems and all the features there appear to work.

    I reported the problem to my hosting provider and they reported back that

    When we check the domain on the server directly we can see the following error message:

    PHP Warning: require(./wp-blog-header.php): failed to open stream: No such file or directory in C:\Inetpub\vhosts\avataruk.com\subdomains\dev\httpdocs\index.php on line 17

    PHP Warning: require(./wp-blog-header.php): failed to open stream: No such file or directory in C:\Inetpub\vhosts\avataruk.com\subdomains\dev\httpdocs\index.php on line 17

    PHP Fatal error: require(): Failed opening required ‘./wp-blog-header.php’ (include_path=’.;./includes;./pear’) in C:\Inetpub\vhosts\avataruk.com\subdomains\dev\httpdocs\index.php on line 17

    We’re not sure why this would be displaying as the file it is looking for is listed within the httpdocs folder.

    They then suggested I ask you guys what you think the problem might be.

    If you need screenshots of anything or any other information please let me know. I didn’t want to get carried away and post too much on my first thread.

    Thanks

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

  • Try checking your site’s error logs for a more specific error message. Error 500 is too a generic an error message to be of any use. Your hosts should be able to help you in accessing your site’s error logs.

    Thread Starter Mudplugger

    (@mudplugger)

    I’ve asked if there are any other error messages and am being told that the ones in my original post are the ones that the hosting company is seeing.

    On the basis of those errors,. it looks like you’re missing some core WordPress files. Try re-uploading all files & folders – except the wp-content folder – from a fresh download of WordPress. Make sure that you delete the old copies of files & folder before uploading the new ones.

    Thread Starter Mudplugger

    (@mudplugger)

    OK,

    So I’ve deleted everything as per your instructions and the Detailed Upgrade Guide.

    Downloaded WP 3.5.1 again and unzipped it.

    Copied 3.5.1 back onto the server using FTP.

    Performed a Folder by Folder check that all item counts match to ensure all files have uploaded.

    The only files that I have not replaced are .htaccess, wp-config.php, web.config and a couple of items that I guess the server creates when you set up the subdomain.

    The only files that are not part of the standard WP install is a Theme called wrings but this is not yet active on the site I have been using the twentyeleven theme before the upgrade.

    I can still access the wp-admin panel but I still get the same error when I try to visit the site.

    Have you spoken to your hosts about this?

    Thread Starter Mudplugger

    (@mudplugger)

    Yes, please see first post.

    I’m thinking about setting up a new subdomain tomorrow and doing a full install from scratch just in case something has gone peculiar.

    Thread Starter Mudplugger

    (@mudplugger)

    OK so I have now tried the following.

    Created new subdomain (dev2), new database & new user.

    Copied WP3.5.1 to new sub domain and run install script.

    This all works fine.

    The next bit is guess work on my part just to see if I could narrow down the source of the problem I’m not even sure if this is possible. I tried editing the dev2 subdomain’s wp-config.php file to use the DB info for the dev subdomain and got an HTTP 500 error. I also tried the reverse but that resulted in an HTTP 500 error also. I corrected both wp-config.php files and dev continues to give the error and dev2 continues to work.

    So should it be possible swap databases between WP installations just by changing the dbname, username and pwd in the wp-config.php file?

    And does the working install in the new subdomain offer any clues to why the original install is not working?

    Thread Starter Mudplugger

    (@mudplugger)

    So I’ve played around with this a bit more while I wait for a reply from you guys. The following all applies to the original subdomain that I mentioned in my first post.

    I’ve reinstated the original index.html file that was created by the server processes when setting up the subdomain and that displays perfectly, so it’s definitely and issue between the server and WP rather than just a problem with the server displaying any webpage.

    I have created a new database, edited the wp-config file and rerun the install.php script. That allows me to see content that is in the brand new DB rather than the original one using the wp-admin panel but I still get the HTTP 500 error when visiting the page so I guess that rules out a problem with the original DB.

    I have renamed the .htaccess file (not that this should be needed as this is a windows server) and the web.config file but that doesn’t resolve the problem. I have done this as neither of those files appear in the second subdomain that I set up and that one works.

    Hopefully this rules out a few possibilities and gives you guys some more information so that you might be able to help me.

    TIA

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘HTTP 500 Error after update’ is closed to new replies.