WordPress.org

Support

Support » Multisite » [Resolved] Clicked Upgraded to WordPress 3.6, Got 500 Internal Server Error

[Resolved] Clicked Upgraded to WordPress 3.6, Got 500 Internal Server Error

  • I was running WordPress 3.5 multisite with no issues on a dedicated server. I clicked the upgrade WordPress to 3.6 button this morning, it started to run the updated, and I now get a 500 Internal Server Error on all of my websites.

    Please help!

Viewing 15 replies - 1 through 15 (of 18 total)
  • This is not a multisite issue.

    Since the updated and following 500 server error, I have tried to:

    1. Downgrade the files to 3.5
    2. Renaming the plugins folder to something else.
    3. Read through the known 3.6 issues.
    4. Re-updated the site files to 3.6

    I have also run the automatic updated on several other multisite installations and they updated fine. I repeat – this is not a multisite issue and has improperly marked as such.

    I have received several emails from clients complaining that their sites are down.

    Again, I could use some real help.

    I have also now:

    5. Deleted the .htaccess file.
    6. Manually updated the db_version to “24448” (it was 22442)
    7. Flushed local DNS
    8. Cleared local cache
    9. Using phpMyAdmin, set the template to twentythirteen.

    I have also now:

    10. Created an php.ini file and set the memory to 64 megs.

    I’m running out of possible solutions…

    esmi

    @esmi

    Forum Moderator

    Try checking your site’s error logs for a more specific error message instead of making wild guesses. Your hosts should be able to help you in accessing your site’s error logs.

    Brian

    @bsbriansaarcom

    I am also having this same problem.

    11. I set define(‘WP_DEBUG’, true);
    12. define(‘WP_DEBUG_LOG’, true); (No debug.log was created in the /wp-content/ folder)

    esmi

    @esmi

    Forum Moderator

    @brian: It is impolite to interrupt another poster’s ongoing thread with a question of your own. It causes significant problems for the forum’s volunteers and prevents us from being able to track issues by topic. Please post your own topic.

    13. Checked error log. My error log has no updates since 7/20/13 and only indicated that there was an issue with the WP Realtime Sitemap plugin. That plugin is deactivated, with the rest of um.

    Thank you for the suggestion Esmi. I am on hold to talk with my hosting company while I continue to look for a solution to a problem not related to multisite.

    esmi

    @esmi

    Forum Moderator

    Was this the server’s error log?

    I think so… The file is called “error_log”.

    Brian

    @bsbriansaarcom

    Sorry I didnt realize I was causing significant problems by just seconding the op problem. Ill create new post.

    Brian

    @bsbriansaarcom

    Hey troy, I tried disabling the plugins and themes as well with no luck. I was able to get it back up by deleting and re-installing themes and plugins. Not sure what was going on.

    OK. Fixed it. GoDaddy discovered that the “PHP 5 Handler” was set to “suphp” when it should have been set to “cgi”.

    I have no idea what that means but it fixed the site.

    I’m glad that you were able to find a solution to your issue also Brian!

Viewing 15 replies - 1 through 15 (of 18 total)
  • The topic ‘[Resolved] Clicked Upgraded to WordPress 3.6, Got 500 Internal Server Error’ is closed to new replies.
Skip to toolbar