More cPanel control panel problems!

Hey Daniel Garcia,

I completely get it. There's nothing quite like a server meltdown to ruin your day, especially when it's your primary web hosting control panel that's locked up – the double "control panel" in your title really emphasizes the frustration! I've been there, pulling my hair out trying to figure out why a simple package update turned into an all-out digital disaster, bringing down crucial server management.

Given you're getting connection refused and can SSH, here's the immediate diagnostic path I'd recommend for these severe cPanel/WHM issues:

• Verify cPanel/WHM Service Status: First, ensure the core cPanel service (cpanel or cpsrvd) is actually running. From SSH, try systemctl status cpanel or /etc/init.d/cpanel status. If it's not running, attempt to start it with systemctl start cpanel or /etc/init.d/cpanel start. If it hangs or fails, check dmesg for kernel-level errors or resource exhaustion.
• Check for cPanel Process Running: Even if systemctl says it's not running, sometimes a zombie process can exist. Run ps aux | grep cpsrvd to see if any cpsrvd processes are active. If so, kill them (kill -9 [PID]) and then try restarting the service again.
• Firewall Configuration: This is a very common culprit after updates. Your firewall (e.g., CSF/LFD, iptables) might be blocking ports 2083 (cPanel SSL), 2087 (WHM SSL), 2082 (cPanel non-SSL), and 2086 (WHM non-SSL).
  • Temporarily disable CSF to test: csf -x (re-enable with csf -e if it's not the issue).
  • Check iptables rules for blocks: iptables -L -n.
  • Ensure ports are open.
• Disk Space: Believe it or not, a full /tmp or /var partition can completely cripple cPanel. Check your disk usage with df -h. If any partition is at 100%, you've found a major problem. Clear old logs or temporary files if possible.
• Run cPanel Update Script Forcefully: Sometimes an update fails mid-way, leaving things in an inconsistent state. Try running /usr/local/cpanel/scripts/upcp --force from SSH. This attempts to re-run and complete any pending updates or repairs to the cPanel installation.
• Review cPanel Logs Again (with context): If the above doesn't yield results, re-examine /usr/local/cpanel/logs/error_log and /var/log/cpanel/error_log for specific errors around the time you tried to restart/update. Look for keywords like "failed," "fatal," "segmentation fault," or "permission denied." These are often more indicative than generic warnings.

You're spot on about disk space, just realized my /var/log is nearly maxed out and that's probably why it's refusing connections...