A site going fully or partially dark almost always traces back to one of a small number of places: a plugin or theme update that assumed a PHP version or dependency that isn’t there, a database table that stopped responding mid-write, a corrupted .htaccess rule, or a server resource limit — memory, execution time, upload size — hit at the worst moment.
SOS-003 Error establishing database connection
$109.3248 hours
SOS-001 White screen of death — diagnosis & fix
$109.3248 hours
SOS-014 Blank page after plugin activation
$109.3248 hours
Showing 1–16 of 24 fixes
A plugin you just activated took the site down. We identify the conflict, get the site back, and tell you whether the plugin can be made…
The site moved hosts and is now erroring, half-loading, or serving the old version. We find what the migration left behind and repair it, without moving…
A broken .htaccess rule is stopping the site from serving. We repair it, keep the rules that matter, and remove what is conflicting.
A database table has crashed and queries against it fail. We repair it, check the rest of the database, and find what caused the crash.
Something has gone badly wrong and you want the site back as it was. We restore from the most recent good backup and tell you exactly…
WordPress cannot reach its database and shows a connection error. We check credentials, server status and table health, repair what is broken, and get the site…
An update broke the site and you want it reverted. We restore the previous working version of the plugin or theme, confirm the site is back,…
An update introduced a fatal PHP error and took the site down. We capture the exact error, roll back or patch the failing component, and verify…
Uploads fail or files cannot be written because permissions are wrong. We set them correctly and securely, and find what changed them.
Requests are being rate-limited and refused. We find what is being throttled and why, then fix the cause — whether that is a bot, a plugin,…
Your server returns a 500 error instead of the page. We read the server logs, find what is actually failing, fix it, and confirm every template…
The server accepts the request then gives up waiting for a response. We work out which layer is timing out, fix what we can reach, and…
The homepage redirects endlessly and never loads. We trace the redirect chain, find which rule is fighting which, and leave a single correct destination.
You cannot log into wp-admin and the password reset email never arrives. We restore access safely at database level, without touching your content.
Requests run past the server's time limit and get killed mid-execution. We find what is taking so long, fix or optimise it, and adjust the limit…
The homepage works but every other page returns 404. We repair the permalink structure and the rewrite rules behind it.
A site going fully or partially dark almost always traces back to one of a small number of places: a plugin or theme update that assumed a PHP version or dependency that isn’t there, a database table that stopped responding mid-write, a corrupted .htaccess rule, or a server resource limit — memory, execution time, upload size — hit at the worst moment. The symptoms vary wildly, from a blank white screen to a 500 error to an endless redirect loop, but the diagnosis is the same in every case: read what the server and PHP error logs are actually saying, reproduce the failure in isolation, and find the one change that triggered it. Migrations cause a version of this too — a site that worked perfectly on the old host can break on the new one because of a path, a domain reference, or a PHP setting that changed underneath it.
What these fixes have in common is that they start with a backup and a read before anything is touched, because the wrong move on a broken site — restoring blind, deleting a table, disabling everything at once — usually costs more than the original problem did. The goal is always the smallest change that gets the site back, not a rebuild.