Joomla vs. WordPress
For a blogger, any black mark on their reputation can literally bury a career, so it’s essential to get your website back up right away and prevent the problem from happening again.
|Your WordPress Blog Crashed, Now What? 4 Steps to Take Right Away: eAskme|
Other people are reading: 6 Questions to Ask a Web Hosting Provider
The most important thing to do before you start looking for restore a WordPress blog after a crash is to set up a monitoring system that will alert you when this happens. This way you will be constantly aware of website’s condition and will be able to act on a moment’s notice. You can easily set up an alert using uptime monitoring programs like DownNotifier or Pingometer.
How to Restore a WordPress Blog After a Crash (and Prevent Future Problems)
1. Find out if it’s a hosting problemThe crash is most likely caused by your hosting if:
- You see an error page with your host’s branding.
- The page times out or shows server error.
- You get alert of a non-PHP error that you don’t understand (hosts might have error codes of their own).
- You get a 500 or 404 error but the index.html, index.php, and home.html files are present in the website folder when you access it via FTP.
- You get an Error Establishing Database Connection message or a blank page.
2. Access the WordPress backendIf the issue isn’t caused by the hosting, the first step to restore a WordPress blog after a crash is to access the backend using the address example.com/wp-admin. Try to login there and if you succeed, backup all your important files before disabling all plugins and resetting the theme to WP default.
The vast majority of WordPress blog crashes are caused by plugins of themes. Usually, an updated version cannot integrate into your scheme, which brings the entire website down.
If you get a PHP error alert, look at the file paths listed. The problem plugin should be the first one. Rename it using FTP and reload your website a few times. Once it goes back online, you’ll be able to disable the faulty plugin and find a replacement.
Important Note:You’ll get a list of plugin errors the first time you visit the Plugins page after the website is back up. Make a screenshot immediately or copy it in any other way as there will be no other chance to see it. This is the list of deactivated plugins that you’ll need to get back up.
3. Update everythingIf you’re lucky and the problem is caused by having one old plugin crashing the site after an update, the Update Everything route should fix all your troubles.
Be sure to have a backup before you start updating. You might need to do it manually, depending on how much of your website crashed.