Emergency
WordPress site down: emergency recovery the same afternoon
A consultancy’s WordPress site returned DNS errors and SSL warnings in the middle of client meetings. BugShield restored availability before the end of the day.
Industry
Professional services
Service
Emergency site recovery
Confirmed price
£49.99
Time to resolve
Same afternoon
The challenge
Visitors to the site encountered browser SSL errors and intermittent DNS failures. Hosting status looked green while the domain still pointed at a retired server IP from an incomplete migration earlier that week.
The in-house team had changed nameservers and assumed propagation would finish quietly. When email and the brochure site both looked unstable mid-workshop with clients in the room, they needed a developer who could untangle DNS, SSL, and WordPress without more downtime theatre.
They did not want a full redesign or a multi-week migration project. They wanted the existing WordPress site reachable on HTTPS with the correct host, that afternoon, at a confirmed price.
What ‘site down’ looked like from the outside
-
Browser NET::ERR_CERT or privacy warnings on the apex domain.
-
Intermittent NXDOMAIN or wrong-IP responses depending on DNS resolver.
-
Hosting dashboard still showed the WordPress files healthy on the new server.
-
www and non-www disagreed on certificate coverage.
-
Office Wi-Fi appeared fine for other sites, so staff assumed ‘the website is broken’ not ‘DNS is mid-flight’.
-
Email delivery to the same domain looked flaky after related MX records were touched.
How BugShield approached it
The emergency request got a confirmed quote and a BugShield developer in chat. DNS records at the registrar, SSL certificates on the new host, and WordPress siteurl/home values were checked against where traffic actually needed to land.
Wrong A records were corrected, SSL was reissued and verified for apex and www, HTTPS redirects were confirmed, and key landing pages were smoke-tested from mobile and desktop networks with flushed local DNS where needed.
Mail records that had been altered by accident were called out clearly so the consultancy’s email provider could finish that piece. BugShield did not silently take over the registrar account beyond the Vault session required for the repair.
Timeline
Midday emergency
Site unreachable for visitors during client meetings. Emergency fix requested with screenshot of the SSL warning.
Assignment
Developer assigned within an hour. Vault held registrar and hosting access for a limited session.
DNS and SSL
A records pointed at the live host. Certificates reissued. Mixed content and redirects verified on key pages.
Close-out
Same-afternoon confirmation from multiple networks. Short clear step-by-step recovery checklist provided for any future host migration.
Technical findings
-
WordPress core on the new host was largely fine; traffic never consistently arrived there.
-
A records still referenced a decommissioned VPS from the previous host for the apex domain.
-
Certificate matched the wrong hostname combination after www was added mid-migration.
-
siteurl in WordPress already showed HTTPS on the new domain, which hid the DNS problem from people only checking inside wp-admin when it briefly resolved.
-
One mail TXT record had been overwritten while editing DNS, which explained separate email complaints.
The result
-
The domain resolved to the correct host with a valid certificate.
-
Homepage, contact, and service pages loaded over HTTPS without warnings.
-
Email DNS records that had been accidentally altered were flagged for the client’s mail provider.
-
A short checklist listed what to verify after any future host or DNS change.
-
Shield monitoring was added afterwards so outages would alert before clients in the room did.
The site was reachable again the same afternoon. Workshops continued without sending visitors to a certificate warning. The consultancy stopped treating DNS edits as a ‘set and forget’ task after migrations.
What this prevented next time
Incomplete migrations fail outside WordPress. Always verify A/AAAA, www, SSL SAN coverage, and redirects from an outside network before decommissioning the old host.
When the panel says the site is healthy but browsers disagree, check DNS first. Not every WordPress site down event is a plugin fatal.
WordPress website down is not always WordPress
Visitors describe everything from DNS failure to SSL warnings as ‘the site is down’. Inside hosting, PHP and MySQL can look perfect. Emergency recovery has to start with where the name resolves, whether the certificate matches, and only then whether WordPress itself is fatal.
BugShield’s fixed-price emergency recovery for this engagement covered getting traffic to the right host securely, not rebuilding the brand site from scratch.
-
Stale A records after a host move
-
Certificate missing www or apex
-
Propagation lag mistaken for a code outage
-
siteurl already correct while DNS still wrong
-
Collateral MX or TXT edits during DNS surgery
Working mid-migration without making it worse
The worst outcome would have been another half-finished DNS change that broke email for longer. The developer documented every record touched, kept credentials in the Vault for the session only, and left the registrar account with the client.
That discipline matters when a consultancy’s domain is also their mailbox and meeting invites.
FAQs
Was WordPress itself broken?
Core WordPress was largely fine. The outage came from DNS pointing at the wrong host and an SSL mismatch after a partial migration.
How quickly was a developer assigned?
The emergency request was assigned within 2 hours and restored the same afternoon.
Did BugShield take over their domain registrar?
No. We advised on the records that needed changing, used Vault access only for the repair session when required, and left ownership with the client.
Why did hosting still look green?
The new server was fine. Most of the public still hit the old IP or mismatched SSL until DNS and certificates were corrected.
Was email fixed as part of the same fee?
DNS mistakes that broke mail were identified and corrected where we had changed related records. Deeper mailbox provider settings remained with their email vendor.
What monitoring stops a repeat?
External uptime checks catch certificate and resolution failures even when the host panel looks healthy. They added Shield monitoring after this incident.
More case studies
WooCommerce
WooCommerce checkout restored the same day
A mid-size UK fashion shop had card payments fail after a payment plugin update. Within hours, orders were flowing again.
Read case studySecurity
Hacked WordPress site cleaned and secured
Visitors saw a defaced homepage and Google began showing security warnings. BugShield removed the malware, rebuilt trust signals, and locked down admin access.
Read case studyError fix
WordPress critical error after update, fixed the same day
A UK charity’s donation site white-screened after weekend updates. BugShield diagnosed a plugin conflict, restored access, and verified forms before donors returned on Monday.
Read case studyFacing something similar?
Get a confirmed price, a BugShield developer, and direct chat from payment onwards.
Request a Fix