Migration Leads to Internal Server Error

  • Resolved jules10622

    (@jules10622)


    13 years ago

    Following the instructions at http://codex.wordpress.org/Moving_WordPress, I moved my WordPress from my “blog” directory to my root directory. I got through Step 9. I was able to view my admin panel at the new location once, but when I tried to go to the Permalinks settings page, I got a “500 Internal Server Error” page instead. Now I can’t access any part of the site; I just get internal server errors.

    I moved all of the files from the old directory to the new one, and I did it in the order indicated by the codex. Any ideas of what could be causing this?

Viewing 3 replies - 1 through 3 (of 3 total)
  • amitash

    (@amitash)

    13 years ago

    Delete the .htaccess file in the root and then access the permalink page and save the settings. The .htaccess file will then be re-generated.

    Thread Starter jules10622

    (@jules10622)

    13 years ago

    Deleting the .htaccess file got rid of the 500 Internal Server Error, but now I have some new ones:

    Safari:
    Safari can’t open the page because the server unexpectedly dropped the connection. This sometimes occurs when the server is busy. Wait for a few minutes, and then try again.

    Chrome:
    This webpage is not available
    The webpage might be temporarily down or it may have moved permanently to a new web address.
    Error 324 (net::ERR_EMPTY_RESPONSE): Unknown error.

    Firefox just brought up a blank white page and said it was “done.”

    I re-uploaded the .htaccess file and continued getting those same results.

    Thread Starter jules10622

    (@jules10622)

    13 years ago

    This morning when I tried to the view the site, it came up! Apparently it fixed itself somehow, or was a hosting-side problem.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Migration Leads to Internal Server Error’ is closed to new replies.