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 17–24 of 24 fixes
PHP runs out of memory partway through a request and the page dies. We find what is consuming it, raise the limit where that is appropriate,…
The server refuses to serve pages and returns 403. We find what is blocking the request — permissions, a security rule, or server config — and…
An update left the site stuck showing a maintenance notice. We clear it safely, check whether the update actually completed, and repair anything it left half-finished.
Installing SSL has put the site into a redirect loop. We find which layer is redirecting and leave a single clean path to HTTPS.
Uploads are rejected for being too large. We raise the limits at every level that enforces them and confirm the upload actually completes.
Your site loads a completely blank page with no error message. We enable logging, find the fatal error WordPress is hiding, fix it, and verify every…
Core files are damaged or missing. We reinstall WordPress core cleanly, leaving your content, plugins, themes and uploads exactly as they are.
Scheduled tasks are not running, so backups, emails and publishing silently fail. We find why cron is not firing and set it up so it runs…
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.