Internal Server Error after migrating localhost to live site

  • Resolved awhitesell

    (@awhitesell)


    9 years, 2 months ago

    Each time I migrate my localhost to my live site my links return a “Internal Server Error” for the next 24+ hours. They eventually fix themselves, but this is a very long time for my live site to be in a broken state.

    I would like to ask if there is an issue with my workflow. I have been manually doing the migration to get an understanding of it by following this guide. The guide walks me through the steps of exporting my database, copying over the data, creating a new database, and then importing the database.

    Is there something I can do reduce my downtime?

Viewing 5 replies - 1 through 5 (of 5 total)
  • Moderator James Huff

    (@macmanx)

    Internal server errors (error 500) are often caused by plugin or theme function conflicts, so if you have access to your admin panel, try deactivating all plugins. If you don’t have access to your admin panel, try manually resetting your plugins (no Dashboard access required). If that resolves the issue, reactivate each one individually until you find the cause.

    If that does not resolve the issue, try switching to the Twenty Fifteen theme to rule-out a theme-specific issue. If you don’t have access to your admin panel, access your server via FTP or SFTP, navigate to /wp-content/themes/ and rename the directory of your currently active theme. This will force the default theme to activate and hopefully rule-out a theme-specific issue.

    If that does not resolve the issue, it’s possible that a .htaccess rule could be the source of the problem. To check for this, access your server via FTP or SFTP and rename the .htaccess file. If you can’t find a .htaccess file, make sure that you have set your FTP or SFTP client to view invisible files.

    If you weren’t able to resolve the issue by either resetting your plugins and theme or renaming your .htaccess file, we may be able to help, but we’ll need a more detailed error message. Internal server errors are usually described in more detail in the server error log. If you have access to your server error log, generate the error again, note the date and time, then immediately check your server error log for any errors that occurred during that time period. If you don’t have access to your server error log, ask your hosting provider to look for you.

    Thread Starter awhitesell

    (@awhitesell)

    It looks like I need to deactivate and activate a specific plugin each time I migrate my work. Thanks for the suggestions.

    Moderator James Huff

    (@macmanx)

    You’re welcome!

    Hi James, I know this is an older thread so I hope that you get notified that I am posting. Thank you for your advice for solving the error 500 issue after migrating to a bew server and new domain. The .htaccess file solution was my problem. I addeded a few zzz onto the file name and bingo! …the links are now working. That was after tryng the Velvet Blue plugin and someother things before I found this thread. So first of all, THANK YOU! I was getting ver frustrated. But I also have a question. Now what? Do I just leave that file renamed? Is it an important file that is going to cause a problem somewhere else? Any insights or suggestion or just simple clarification would be greatly appreciated.

    Gregg

    I tried changing both. it still shows error. I changed my php settings to lower version then it shows

    Parse error: syntax error, unexpected T_FUNCTION in C:\Inetpub\vhosts\mekhridzz.com\httpdocs\wp-content\themes\landscaper\inc\acf.php on line 21

    Before migration it worked fine in cpanel.

    Help required…

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Internal Server Error after migrating localhost to live site’ is closed to new replies.

Tags