Home / Ongoing Work / Hosting & Infrastructure

Hosting & Infrastructure

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.

$49
from
24h
fastest
MOST BOUGHT IN THIS CATEGORY
A plain directive list in .htaccess, for .htaccess / nginx rules cleanup CFG-014 .htaccess / nginx rules cleanup $109.3248 hours A code editor view, for Activity log installation & retention config MON-008 Activity log installation & retention config $41.5348 hours A server rack with one unit flagged, for Addon & parked domain configuration HCP-005 Addon & parked domain configuration $41.5348 hours

Showing 1–16 of 56 fixes

A plain directive list in .htaccess, for .htaccess / nginx rules cleanup
CFG-014

.htaccess / nginx rules cleanup

.htaccess or nginx rules cleaned of redundant and conflicting cruft.

Standard Code & template
Needs: SFTP access, Hosting panel
$109.32
Delivered in 48 hours
View fix
A server rack with one unit flagged, for Addon & parked domain configuration
HCP-005

Addon & parked domain configuration

An addon or parked domain configured correctly — a separate name, not a prefix on your existing one.

Quick Dashboard / config
Needs: Hosting panel, Sub-account invite
$41.53
Delivered in 48 hours
View fix
A checklist of audit items, one failing, for Automated health check report configurati…
MON-009

Automated health check report configuration

A combined health check report on schedule — with the same warning about an absent report.

Standard Dashboard / config
Needs: WP admin login, Third-party credentials
$109.32
Delivered in 48 hours
View fix
A navigation bar with one item highlighted, for Broken link monitoring setup
MON-005

Broken link monitoring setup

Broken link monitoring that keeps checking after we leave — with the same silent-failure warning.

Quick Dashboard / config
Needs: WP admin login, Third-party credentials
$41.53
Delivered in 48 hours
View fix
Two overlapping blocks, for CDN configuration vs origin conflict fix
CFG-011

CDN configuration & origin conflict fix

A CDN serving stale or broken dynamic content, traced against the origin server directly.

Standard Dashboard / config
Needs: CDN access, Hosting panel, WP admin login
$109.32
Delivered in 48 hours
View fix
A line chart, for Cloudflare settings audit & correction
CFG-017

Cloudflare settings audit & correction

Something actively broken with Cloudflare in the picture, traced to the one setting causing it.

Standard Dashboard / config
Needs: CDN access, WP admin login
$109.32
Delivered in 48 hours
View fix
Core Web Vitals gauges showing LCP, INP and CLS scores, for Core Web Vitals monitoring setup
MON-006

Core Web Vitals monitoring setup

Core Web Vitals tracked over time, not just a single snapshot — watching it stays with you.

Quick Dashboard / config
Needs: WP admin login, Third-party credentials, Search Console access
$41.53
Delivered in 48 hours
View fix
A code editor view, for Cron job creation & scheduling
HCP-003

Cron job creation & scheduling

A cron job created and scheduled through your control panel — the straightforward version, not custom code.

Quick Dashboard / config
Needs: Hosting panel, Sub-account invite
$41.53
Delivered in 48 hours
View fix
A server rack with one unit flagged, for Custom error page configuration
HCP-013

Custom error page configuration

Custom error pages replacing your host's generic default for 404s and worse.

Quick Dashboard / config
Needs: Hosting panel, Sub-account invite
$41.53
Delivered in 48 hours
View fix
A debug log with one highlighted fatal error, for Debug mode disable & error log cleanup
CFG-005

Debug mode disable & error log cleanup

Debug mode left exposing errors publicly, disabled without losing your private error log.

Quick Dashboard / config
Needs: SFTP access, WP admin login
$41.53
Delivered in 48 hours
View fix
A line chart, for Disk usage audit & cleanup
HCP-017

Disk usage audit & cleanup

What's actually eating your disk space, found and cleaned up with your confirmation first.

Standard Report deliverable
Needs: Hosting panel, Sub-account invite
$109.32
Delivered in 48 hours
View fix
A line chart, for DNS record audit & correction
CFG-018

DNS record audit & correction

A DNS discrepancy found by auditing the full zone when you don't know which record is wrong.

Standard Dashboard / config
Needs: DNS access
$109.32
Delivered in 48 hours
View fix
A server rack with one unit flagged, for DNS zone record management at host
HCP-009

DNS zone record management at host

DNS records corrected right inside your control panel, with the prior zone documented first.

Standard Dashboard / config
Needs: Hosting panel, DNS access, Sub-account invite
$109.32
Delivered in 48 hours
View fix
Two boxes connected by an arrow, for Domain change - full site URL migration
CFG-009

Domain change – full site URL migration

A complete domain change — database, code, and DNS together, with redirects from the old one.

Advanced Database operation
Needs: WP admin login, Database access, DNS access, Hosting panel
$219.49
Delivered in 72 hours
View fix

About these fixes

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.