Server Management Resources

Troubleshooting Terminal Required 14 min read

Common Server Troubleshooting Steps

A practical workflow for checking uptime, logs, resource usage, services, and network ports when something breaks on your server.

DNS 11 min read

Understand A, CNAME, MX, TXT, and NS records—and how to update them in cPanel, Cloudflare, GoDaddy, and Namecheap.

DNS Terminal Required 8 min read

Use dig, nslookup, and host from the command line to verify A, MX, TXT, and CNAME records before and after DNS changes.

PHP Terminal Required 12 min read

Check your PHP version, upgrade on Ubuntu/Debian or CentOS/RHEL, switch versions safely, and restart your web stack.

PHP 10 min read

Change PHP versions in cPanel, Plesk, GoDaddy, SiteGround, Bluehost, WP Engine, and Kinsta without SSH access.

Security Terminal Required 9 min read

Force HTTPS with Apache .htaccess, NGINX server blocks, cPanel redirects, or Cloudflare SSL settings—and verify with curl.

FTP 9 min read

Set up FileZilla with FTP or SFTP credentials from your host, transfer files safely, and fix common connection errors.

FTP 7 min read

Create scoped FTP users in cPanel or Plesk with directory limits, quotas, and security best practices.

SSH Terminal Required 11 min read

Connect with password or SSH keys from macOS, Linux, or Windows—and resolve refused connections and permission errors.

WordPress Terminal Required 13 min read

Enable WP_DEBUG, use Query Monitor, read PHP logs, inspect the browser console, and tackle the white screen of death.

WordPress Terminal Required 6 min read

Safely deactivate a broken plugin by renaming its folder through FileZilla or the mv command over SSH.

WordPress Terminal Required 16 min read

Fix database connection errors, 500/403/404 responses, memory limits, maintenance mode, redirect loops, and upload size issues.