It’s 10 p.m. on a Saturday and a customer messages you: “Is your website down?” You open it and see a blank white page, or a single line along the lines of “There has been a critical error on this website.” You try to log in to the admin, and even the login page won’t load. The developer who built the site isn’t answering, and every tutorial online is harder to follow than the last. Somehow sites always break on weekends or in the middle of the night.
At a moment like this, the biggest danger isn’t the problem itself. It’s making things worse in a panic. Get three things right first, then hand the diagnosis and the rescue plan to Roamer AI. It can investigate even when the admin is completely unreachable.
The 30-Second Overview
| What you want to know | The short answer |
|---|---|
| What to do right now | Don’t rush to reinstall, don’t start deleting files. Open Roamer AI and say, “My site won’t load. Find out why.” |
| Can it investigate if I can’t get into the admin? | Yes. The rescue tools don’t need WordPress to load normally |
| What it checks | Homepage, admin and API status; recent fatal errors and the plugins or themes involved; updates and changes from the last 72 hours |
| How it fixes things | Deactivates the problem plugin, rolls a plugin back, disables a code snippet, switches PHP, or restores a snapshot. Every action needs your confirmation |
| What if it can’t fix it | It notifies a RoamerHost engineer with the cause it found and what it has tried; outages that affect your business are flagged as urgent |
| Which sites can use it | Emergency rescue is a feature of sites hosted on RoamerHost |
Your Site Suddenly Won’t Load. What Are the Three Things to Do First?
- Don’t rush to reinstall WordPress or rebuild the site. The most common cause of a white screen or critical error is a plugin, theme or snippet of code that has failed, not a site that’s been wiped out. Reinstalling in a hurry can overwrite your existing settings and content, turning a problem that deactivating one plugin would have solved into a real disaster.
- Don’t start deleting files. Online tutorials often tell you to “rename this folder” or “delete that file.” If you’re not sure what you’re doing, it’s easy to delete the wrong thing, like uploaded images or configuration files. And once it’s gone, the clues that could have pointed to the cause go with it.
- Open Roamer AI and say, “My site won’t load. Find out why.” Roamer AI lives in your RoamerHost dashboard, not on your website, so it still opens when your site is broken. Just tell it what you see, roughly when it started, and whether you’ve changed or updated anything recently.
You just say: describe it the way you normally would, for example:
- “My site won’t load. Find out why.”
- “The site has been a white screen since this morning. I updated plugins yesterday. Find out which one did it.”
- “The homepage works, but I can’t log in to the admin. Take a look at what’s wrong.”
- “The checkout page layout has been broken since yesterday and customers can’t place orders. Find the cause first.”
What these three have in common: hold off on doing anything yourself and let someone who knows (or the AI) look first. Plenty of outages aren’t hard to recover from once you find the cause. The trouble starts when the scene gets messed up before anyone has found it.
You Can’t Even Get Into the Admin. How Does the AI Find the Cause?
Most plugins and assistant tools can only help when WordPress is running normally. Roamer AI’s rescue tools are different: they don’t need WordPress to load, so they still work when your site is broken and the admin is unreachable. It checks all of these in one pass:
- The status of the homepage, admin and API: whether the whole site is down, only the admin is unreachable, or just some features are broken. The API is the channel WordPress uses to exchange data, and the editor and many plugins depend on it.
- Recent fatal errors: when the site started throwing fatal errors, and which plugin or theme is involved.
- Whether WordPress itself works with plugins turned off: this tells it whether the problem is in a plugin or somewhere else.
- Plugins and themes updated or changed in the last 72 hours: if the site was fine yesterday and broken today, whatever changed recently is usually the prime suspect.
Once it’s done, it explains in plain language when the site started failing, which plugin or theme the error is tied to, and whether a recent update caused it.
Once It Finds the Cause, How Does It Fix Things? You Approve Every Step
| Rescue action | When it fits | What it affects |
|---|---|---|
| Deactivate the problem plugin | One plugin is causing a site-wide error | The site comes back, but that plugin’s features are gone for now (if it’s your form plugin, the form disappears until it’s back) |
| Roll the plugin back to its pre-update version | The error started after an update, and a pre-update backup exists | Features stay intact and the plugin returns to its pre-update state; you deal with the update later |
| Disable the problem code snippet | A newly added code snippet is causing errors | Whatever that snippet added stops working for now; nothing else is affected |
| Switch the PHP version | An old plugin is incompatible after a PHP version change | Switching back to a version the plugin runs on brings the site back; long term, the plugin still needs updating or replacing |
| Restore a snapshot | Content or settings got broken | Site data goes back to how it was when the snapshot was taken; before restoring, the system makes one more backup of the current state |
For every rescue action, it first explains what it will do and what it will affect, then gives you a confirmation code button. Nothing runs until you click it. This is enforced by the system: the AI has no way to confirm on your behalf, so it can’t decide on its own to deactivate your shopping cart plugin to get the site back up. The code is valid for 60 minutes and works only once, and if the action about to run differs from what was described, it won’t go through.
One more thing about restoring snapshots: a snapshot mainly holds the database (your site’s content and settings), and only some snapshots include theme files. So when the problem is in a plugin’s code, deactivating or rolling back the plugin is usually the better fix. Restoring a snapshot fits better when content or settings have been broken.
Once the site is back, it checks again to confirm the homepage and admin have actually recovered, instead of just telling you “it should be fine now.”
Three Common Scenarios: What Does It Actually Do?
Scenario 1: A plugin update leaves the whole site throwing 500 errors
You click update on a few plugins in the admin, and a few minutes later your site shows nothing but a “500” error code or “There has been a critical error on this website.”
- What it finds: the error log points to a plugin that was just updated, and that plugin is on the list of updates from the last 72 hours.
- What it recommends: if there’s a pre-update backup of that plugin, roll it back to the old version so the site comes back with its features intact. If there’s no backup to use, deactivate the plugin first to get the site back, then sort out the version issue.
- Afterward: once the plugin releases a fix, update it again using the batch update process.
Scenario 2: You added some code yourself and the site went white
You followed an online tutorial to add a small feature, pasted in some code, saved, and the site went blank.
- What it finds: the error log points to the code you just added.
- What it recommends: if the code was added as a code snippet, disable that snippet. The site comes back, and your other content and features are unaffected.
- Afterward: if you still want the feature, ask Roamer AI to build it again, and it will screenshot the result to check the layout (see adding features just by asking the AI).
Keep in mind that if the code was edited straight into a theme file instead of being added as a code snippet, fixing it isn’t this simple. That’s why one of the tips below is to avoid editing theme files directly in the admin.
Scenario 3: An old plugin starts failing after a PHP version change
PHP is the programming language WordPress runs on, and its versions get upgraded over time. After your site moves to a new environment or PHP moves to a newer version, an old plugin that hasn’t been updated in years starts throwing errors. Some pages won’t load, or the whole site goes white.
- What it finds: the error is in that old plugin, and it assesses that the plugin is incompatible with the current PHP version.
- What it recommends: switch PHP back to a version the old plugin runs on so the site comes back right away. Then check whether the plugin has an update that supports the newer PHP. If it does, update it; if not, consider replacing it with another plugin.
- Afterward: switching back to an older PHP only buys time. Long term, the plugin still needs to be updated or replaced, or your site will be stuck on an old PHP version.
All three scenarios work the same way: it explains what it found, what it plans to do and what that will affect, and it only acts once you click confirm.
What If the AI Can’t Fix It Either?
Some situations are beyond what the AI can handle, such as problems that need server-level work, data that needs recovering, or a site that still won’t come back after it has tried every reasonable fix. In those cases, Roamer AI notifies a RoamerHost engineer and includes:
- Your conversation
- Your site details
- The cause it found
- What it has already tried
The engineer doesn’t have to start by asking you everything again, and you don’t have to retype the whole story in the middle of the night. If your site is down and it’s affecting your business, it flags the case as urgent. You can also just say “get me a person” or “get me an engineer” at any time.
How Do You Keep Your Site From Breaking? Three Preventive Habits
- Regular health checks: once a month, tell it, “Check how my site is doing.” The health report lists your WordPress and PHP versions, what can be updated, the number of fatal errors in the last 24 hours, disk usage and homepage response time. Some problems show up in the error log well before the site actually goes down.
- Batch updates: don’t update everything at once, and don’t leave updates sitting either. Back up first, update 5 at a time, check each batch. See Afraid to Update Plugins? Backups, Batches, Rollbacks.
- Don’t edit theme files directly in the admin: the Theme File Editor in the WordPress admin looks convenient, but one wrong character can white-screen your whole site, and the next theme update overwrites whatever you changed. If you want to add a feature, have Roamer AI add it as a code snippet, which can be disabled on its own if something goes wrong.
Which Sites Can Use Emergency Rescue?
Emergency rescue is a feature of sites hosted on RoamerHost. The rescue tools can work while the admin is down because hosted sites live on RoamerHost itself. An external WordPress site that isn’t on RoamerHost connects to Roamer AI through WordPress’s own Application Passwords, so when the site breaks, the connection goes down with it. That’s why external sites can use Roamer AI for everyday work like content, menus, plugins, SEO and products, while emergency rescue, snapshots and restores, bulk updates and PHP version switching are only offered on RoamerHost-hosted sites. If you want the full feature set, see what to know before moving to RoamerHost. WP × Roamer AI Pro includes help migrating your existing site: contact [email protected] and we’ll help you move it over.
WP × Roamer AI Pro is NT$11,988 a year (avg. NT$999/mo, billed yearly) and includes hosting, a WordPress site and full Roamer AI access. No setup fee, no add-ons. To try it first, fill out the free trial request form. After you submit it, someone from our team will contact you to confirm what you need and then set up a trial environment (if you want to try Roamer AI, say so in the requirements field). To see what else Roamer AI can do, check out the service page.
FAQ
Q: I can’t get into the admin at all. Can the AI really still handle it?
Yes, as long as the site is hosted on RoamerHost. The rescue tools don’t need WordPress to load normally. They go straight to the status of the homepage, admin and API, recent fatal errors, and the plugins and themes changed in the last 72 hours. Just open Roamer AI in your RoamerHost dashboard and describe what’s happening.
Q: Will it deactivate my plugins on its own just to get the site back?
No. Deactivating a plugin, rolling back a plugin version, disabling a code snippet, switching PHP, restoring a snapshot: every rescue action runs only after you click the confirmation code. The AI has no way to confirm on your behalf.
Q: Will restoring a snapshot wipe out recent orders or posts?
It might. Restoring a snapshot returns your site data to how it was when the snapshot was taken, so orders, comments or posts added after that point may be affected. That’s why it explains the impact and asks for your confirmation before restoring. The system also makes one more backup of the current state first; if that backup fails, the restore doesn’t happen, and you can roll back again after restoring. If you run an online store, read the impact explanation carefully before you click confirm.
Q: Once the site is back, is the problem solved?
The site is running again, but the root cause isn’t necessarily gone. A deactivated plugin’s features stay missing for now. A plugin rolled back to an old version still needs updating later. Switching back to an older PHP only buys time. Once the site is back, just ask it, “What still needs to be handled?” and put the follow-ups into your next health check and update round.
Q: My site isn’t on RoamerHost. Can I use rescue?
No. An external WordPress site can connect to Roamer AI with Application Passwords for everyday work, but emergency rescue is only offered on RoamerHost-hosted sites. If you want that safety net, you can move your site to RoamerHost. WP × Roamer AI Pro includes help migrating your existing site. Contact [email protected] and we’ll help you move it over.
Further Reading
- Afraid to Update Plugins? Backups, Batches, Rollbacks
- Is AI Safe on Your Site? Snapshots, Confirmations and Undo
- Whoever Built Your Site Is Gone: How to Take It Over
- Can’t Find the Right Plugin? Just Ask the AI to Build It
- Moving From Shared Hosting to RoamerHost: What to Know
Need someone to build it for you?
When what you need goes beyond what plugins and code snippets can do (large custom plugins, integrations with your company’s systems, rebuilding an old site), someone has to work in the code. Roamer Tech, RoamerHost’s parent company, takes on advanced WordPress development:
