/ Server help

When a server breaks, start here

Free guides for anyone who runs a Linux server or VPS: what to check first, what not to do, the commands that answer the question, and when to stop. To hand the incident over instead, Server Rescue fixes it for $69, and if we cannot fix it you pay nothing.

  • Server down: what to check first

    A Linux server or VPS stopped answering. The checks that find the cause fastest, what not to do, and a fixed-price rescue: no fix, no fee.

  • 502 Bad Gateway on nginx

    nginx answers 502 when the app behind it does not. How to read the error log, bring PHP-FPM or the app back safely, and when to hand it over.

  • 504 Gateway Timeout

    nginx waited for the app and gave up. How to find the slow part, why a longer timeout is rarely the fix, and when to hand it over.

  • Error establishing a database connection

    WordPress cannot reach its database. Check whether MySQL runs, why it stopped, the four lines in wp-config.php, and when to hand it over.

  • WordPress white screen or critical error

    A blank page, or 'There has been a critical error on this website'. Find the PHP error, switch off the plugin or theme behind it, raise memory if needed.

  • Too many redirects

    The page redirected you too many times. See the loop with curl or the free redirect checker, then fix the usual causes: CDN SSL, proxies, site URLs.

  • 403 Forbidden on nginx or Apache

    The server refuses the page. Read the error log, then check file permissions, a missing index file, deny rules and SELinux, with the command for each.

  • Disk full: no space left on device

    A full disk stops databases, uploads and logins. Find what filled it with df and du, free space without breaking anything, and stop it filling again.

  • SSL certificate expired: the fix

    Browsers say your certificate expired. How to confirm it, why automatic renewal stopped, how to renew with Certbot, and how to see the next one coming.

  • Renewing a Let's Encrypt certificate

    certbot renew failing, or not running at all? Test it with a dry run, fix the challenge, reload the web server with a hook, and check the timer.

  • DNS not resolving or still on the old server

    A domain does not resolve, or still points at the old server after a change. Check with dig, tell caching from a real fault, and fix the record.

  • Email from the server going to spam

    Mail from your site or server lands in spam or bounces. Check SPF, DKIM, DMARC and reverse DNS with dig, read the headers, and fix each record.

  • Website hacked: the first steps

    Your site redirects to spam or your host flagged malware. What to do in the first hour, how to find the way in, and why a restore alone lets them back.

  • Moving a site to a new server

    Move a site or app to a new server in a safe order: lower the DNS TTL, copy, test before the switch, a final sync, switch, and keep the old server.

  • Linux server hardening checklist

    The basics that keep a small Linux VPS out of trouble: updates, SSH, firewall, services, TLS, backups and monitoring, with the commands to check each one.