Need help now? Our emergency line is open 24/7 on 0426 833 422. Tell us what you see and when it started.
Key takeaways
- Stay calm and write down what you see, when it started and what changed just before.
- Most WordPress emergencies trace back to a recent update, a plugin clash, the hosting server or an expired renewal.
- Check the simple things first: is it just you, did the domain or SSL expire, is the host having an outage?
- Take a backup before you try any fix, even of the broken site.
- If customers can’t pay or their data may be at risk, get professional help straight away.
When a WordPress site breaks, start with what you can see: the exact error message, when it started and what changed beforehand. Then check the simple causes, such as hosting outages and expired renewals, before touching plugins or code. This guide shows how to triage the most common emergencies and links to a detailed fix for each one.
First five minutes: what to check
- Is it just you? Try the site on your phone using mobile data, not your office wifi. If it loads there, the problem may be local to your network.
- Did something expire? Check your domain and SSL certificate. An expired domain stops the website and email. An expired certificate shows a security warning.
- Is your host having a problem? Check your host’s status page or support channel. If it’s a wider outage, the fix is theirs.
- What changed? Think back. An update, a new plugin, a change to settings or a new staff member are the usual suspects.
- Write it down. Note the exact error text, the time and any change. It makes the fix much faster, whoever does it.
What does the error tell you?
The message on screen is your best clue. Match it below, then follow the link for a step-by-step fix.
- Site down or very slow: see what to do in the first 30 minutes.
- “There has been a critical error”: see how to fix the critical error message.
- “Error establishing a database connection”: see fixing the database connection error.
- 500 Internal Server Error: see the step-by-step 500 error fix.
- A blank white page: see the white screen of death.
- Problems right after an update: see how to roll back a broken update.
When the checkout breaks
A broken checkout is the most expensive kind of emergency, because every hour costs sales. Australians spent $82.6 billion online in 2025, according to Australia Post. Customers who can’t pay rarely wait. They go elsewhere.
Common causes include:
- A recent update to WooCommerce, the payment plugin or the theme that no longer work together.
- Payment keys that expired, were changed or were switched to test mode.
- Caching that serves an old version of the cart or checkout page to everyone.
- A slow or overloaded database, which can make checkout time out.
If you updated something recently, rolling back that update is often the fastest fix. Then test a real order from start to finish. For ways to keep checkout fast and secure, see faster, safer WooCommerce checkouts.
Notes for your developer
If you’re handing this to a developer or your host, these details speed things up:
- The exact error text and a screenshot.
- The time it started, and anything that changed just before.
- Hosting, WordPress admin and SFTP access, sent securely, never in a plain email.
- Whether a recent backup exists, and where it’s stored.
They’ll usually start with the server error log and WordPress debug log. These show the file and line that failed, which turns guesswork into a fix.
How to avoid the next emergency
Most emergencies we fix share the same roots: updates without a backup, plugins nobody maintains, renewals that lapsed, and no one watching the site. Regular maintenance removes most of them. Our WordPress maintenance checklist lists what to check and how often.
Frequently asked questions
What should I do first when my WordPress site goes down?
Check whether it’s down for everyone by using your phone on mobile data. Then check your domain and SSL haven’t expired, and whether your host has a known outage.
Can I fix a WordPress emergency myself?
Often, yes, if you have a recent backup and the cause is a recent update. Take a backup before you try anything, and get help if payment or customer data is involved.
Why did my checkout suddenly stop working?
Common causes are a recent update to WooCommerce or the payment plugin, changed or expired payment keys, caching of checkout pages, or an overloaded database.
Do you offer 24/7 emergency WordPress support?
Yes. Our emergency line is open 24/7 on 0426 833 422.
How do I stop emergencies happening again?
Keep offsite backups, update regularly with checks afterwards, remove unused plugins and monitor uptime. A maintenance plan covers all of these.
Sources
- eCommerce industry report 2026, Australia Post, 2026
- Debugging in WordPress, WordPress.org, accessed 13 Nov 2026