How To Resolve 500 Internal Server Fault On WordPress Later Migration?

 Migrated a WordPress site from local evolution estimator to a production server in addition to enco How to resolve 500 Internal Server Error on WordPress later migration?

Migrated a WordPress site from local evolution estimator to a production server in addition to encountering 500 Internal Server Errors when visiting posts or pages similar the fault message below:

The server encountered an internal fault or misconfiguration in addition to was unable to consummate your request.

In this post service nosotros shall reckon How to resolve 500 Internal Server Error on WordPress later migration?


The basic steps involved inwards migrating WordPress website from local server to alive sever are given below:

  1. Upload the entire WordPress website installation folder from the local server to alive server nether htdocs or httpddocs or www or public_html folder. 
    • You tin upload the files or zipped folder to the alive server via FTP or past times using the spider web host file manager interface to upload the files.
  2. Open phpMyAdmin on local server in addition to export the database used past times the WordPress website
  3. Clean upwardly the URL
    • On the local server, the URL of the website would endure something similar http://localhost or http://localhost:8080 (if using a unlike http port).
    • Open the exported mysql file inwards a notepad or ameliorate alongside notepad++ in addition to supervene upon all instances of http://localhost with http://yourdomain.com
  4. Open phpMyAdmin on the alive server in addition to create a database. 
  5. Import the database exported on the local server to the alive server using phpMyAdmin on the alive server
  6. Check wp_options tabular array inwards the alive server using phpMyAdmin if the Site URL in addition to Home are update to the alive domain URL. If non update.
  7. Open file deal 1 the spider web host or using FTP. 
    • Find wp-config.php in addition to update the database name, username, in addition to other settings if necessary every bit per your host details
  8. Open your website in addition to check.

 The to a higher house steps are basic. You may cheque out elaborate steps online.

How to resolve 500 Internal Server Error on WordPress later migration?

There may endure several reasons why nosotros reckon 500 Internal Server Error merely the close mutual drive alongside WordPress website seeing 500 fault is due to .htaccess file.

  • Open root directory where WordPress is installed using FileZilla or from whatever preferred FTP customer or from the online File Manager spider web interface provided past times the spider web host. 
  • The root directory is to a greater extent than oftentimes than non past times the elevate public_html or htdocs or httpddocs or www.
  • If y’all don’t reckon your .htaccess file or whatever files starting alongside point (.) , brand hidden files view-able past times clicking Server in addition to selecting Force Showing Hidden Files (from FTP client). If using spider web interface, cheque for similar settings to present hidden files if any.
  • Once .htaccess file is found, right-click it, in addition to rename it “.htaccess.bak” to backup the .htaccess file. This makes the site’s .htaccess file expire unavailable. We straight off involve to create a novel .htaccess file. Don’t access your site yet, at that spot volition endure errors.
  • Login to the WordPress admin in addition to navigate to Settings > Permalinks. Select Permalinks of desired permalink construction if non already. If Permalinks is already selected, allow it be. Scroll downwards to the bottom of the page, in addition to click Save Changes.
  • Open the WordPress website inwards a browser. Check if the 500 internal server fault is gone.
If the 500 Internal Server Error upshot is resolved, in addition to thus it was caused past times the .htaccess file due to approximately wrong settings which is the close mutual drive for 500 Internal Server Error. And it is easier resolved past times letting WordPress recreate the .htaccess file every bit per the steps discussed above.
If the 500 Internal Server Error nonetheless exists, in addition to thus it could endure due to another issues which y’all involve to cheque whatever Apache in addition to PHP fault logs on the server. These logs tin render valuable context related to whatever code failures or other potential causes of a site failure. Logs tin endure accessed from the command panel provided past times spider web host.

The next is the default permalink rewrite code which should endure included inwards the .htaccess file (since WordPress 3.0):

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ – [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress

More information regarding Permalinks on WordPress here.