A layer of problems sits underneath WordPress entirely, in the hosting account and the server configuration it depends on — DNS records, SSL certificates, the PHP version and its resource limits, server-level caching, and for larger operations, a multisite network spanning several of those at once.
CFG-014 .htaccess / nginx rules cleanup
$109.3248 hours
MON-008 Activity log installation & retention config
$41.5348 hours
HCP-005 Addon & parked domain configuration
$41.5348 hours
Showing 17–32 of 56 fixes
A subsite's mapped domain not resolving correctly, traced from DNS through to SSL coverage.
Email accounts and forwarders created and tested — not a migration from another provider.
The environment type flag set correctly per site instance — production, staging, or development.
Error logging configured privately with rotation, so it never grows unbounded.
An FTP account restricted to exactly one directory — nothing more than the job needs.
Leftover hardcoded references to your old domain, found in code and content a migration tool missed.
A host migration coordinated through both control panels — flagged early if a feature won't carry over.
Why your site is being throttled, investigated as far as your host's own control panel allows.
Hotlink and leech protection configured, without blocking legitimate embedding you actually want.
An HTTPS warning despite a certificate being installed, traced to the actual mismatch.
Specific IPs or countries blocked at the server level, checked against legitimate traffic first.
Let's Encrypt auto-renewal failed silently — traced to the actual cause before it expires again.
Backup and restore configured for multisite's actual shared structure, tested with a real restoration.
An existing multisite network misbehaving, traced to network settings or a specific subsite.
An existing single site converted into a multisite network, with the trade-offs discussed upfront.
The network's shared database tables optimised, without touching any individual subsite's own data.
A layer of problems sits underneath WordPress entirely, in the hosting account and the server configuration it depends on — DNS records, SSL certificates, the PHP version and its resource limits, server-level caching, and for larger operations, a multisite network spanning several of those at once. None of it is visible from inside wp-admin, which is exactly why it gets missed: a DNS record pointing at the wrong IP, a PHP memory limit set by the hosting plan rather than the site’s actual needs, an SSL certificate that renewed on the server but never updated in WordPress’s own settings.
What these fixes have in common is that they happen in the hosting control panel, the DNS zone, or the server configuration itself, not inside a WordPress plugin — because that’s genuinely where the setting lives, and a plugin can only work around a server limit, not remove it. Multisite networks compound this: a change made at the network level affects every subsite at once, so a fix has to account for all of them, not just the one that reported the problem. The work is precise because a wrong change at this level affects the whole site, not one page.