Hosting Guides & Tutorials

Isolate the site, restore from a backup taken before the compromise, rotate every credential, and fix the entry point before you bring it back online.

Stop, work out exactly what is gone, then check for a backup before touching anything else — order matters here.

Two ways to send one domain to another, and why a proper 301 redirect matters far more than it looks like it should.

How to find what is actually straining the database, and the maintenance most busy sites are quietly overdue for.

Why every extra file a page loads adds delay, and how to cut the number down without changing how the page looks.

Deactivating a plugin leaves its files and often its database tables behind. Here is how to remove one completely.

A corrupted table has a specific fix, and it is different depending on whether the table is MyISAM or InnoDB.

WP-Cron piggybacks on visitor traffic rather than running on a real schedule. Here is how to replace it with one that does.

Requesting a refund is a short ticket or email — here is what to include and what our published refund policy actually covers.

Resetting the password is the easy part — updating every application that still has the old one saved is the part people forget.

Three ways to reset a WordPress password, from the ordinary email link to editing the database directly when nothing else works.

The database half of a restore has its own tools and its own common errors — here is how to do it properly.

Getting back one deleted or broken file without touching anything else on the site.

A restore overwrites the live site with the backup, so do it in the right order — here is what that order is.

Restoring files and database together, whichever way you took the backup, and the checks to run once the site is back.

Rolling back is simple if the old hosting is still running, which is exactly why you should never cancel it early.

Rolling back is a deliberate restore to a specific date, and everything created after that date is lost the moment you commit to it.

Node needs a long-running process that shared hosting cannot give it — here is what that means and where a Node app actually belongs.

Cron runs a PHP script on a schedule with no browser involved — here is the five-field syntax and how to check a run actually worked.

The practical ways to actually check your files for malicious code, and how to read the results without missing what matters.

A plain find-and-replace can silently corrupt serialized data — here is how to do it without breaking the site.

The concrete steps that actually matter for securing a fresh Linux server, in the order that keeps you from locking yourself out.

Updates, strong unique logins, two-factor authentication, a minimal plugin list, and backups that actually restore — in that order of importance.

A store is a bigger target than a brochure site because there is more to steal and more ways in — here is where to focus first.