Server Admin

WHM, cPanel, and FTP stop working after a server reboot: what to check

A field guide to the boring but critical post-reboot checklist when WHM, cPanel, and FTP go dark together. Services, ports, firewall, license, and the order to fix them in.

  • The Turn Group
  • 6 min read
  • 2.2k views
Server terminal showing WHM and cPanel service restart

If your WHM, cPanel, and FTP all stop responding after a server reboot, the instinct is to panic and start restarting things at random. Do not. There is a specific order to check these things, and working through it methodically gets you back online in minutes rather than hours of thrashing.

Why they go down together after a reboot

WHM, cPanel, and FTP going dark simultaneously is almost always caused by one of three root issues: a service that did not start cleanly on boot, a firewall that came up before the services were listening (and is now blocking their ports), or a cPanel license check that failed on restart. Knowing which of these three you are dealing with is the entire diagnostic problem. Everything else follows from that.

Step 1: Confirm the server is actually up

SSH into the server directly. If you cannot SSH, the problem is at the OS level or network level, not the application level, and the steps below do not apply yet. Check with your hosting provider's out-of-band console or VNC access. If SSH works, continue.

ssh root@your.server.ip

Once you are in, check the uptime and recent boot time to confirm the reboot completed normally:

uptime
last reboot

Step 2: Check whether the cPanel services are running

On a cPanel/WHM server, the main service manager is chkservd. Check the status of the core services directly:

systemctl status cpanel
systemctl status cpsrvd
systemctl status pure-ftpd

If any of these show as inactive or failed, try starting them manually:

systemctl start cpanel
systemctl start cpsrvd
systemctl start pure-ftpd

Then try accessing WHM and FTP again. If they start cleanly and stay running, a service was simply not enabled to start on boot. Fix that with:

systemctl enable cpanel
systemctl enable cpsrvd
systemctl enable pure-ftpd

If the services fail to start, or start and immediately die, move to the next step before trying to restart them again.

Step 3: Read the logs before doing anything else

Randomly restarting services when they are failing to start is counterproductive. Read the logs first. The most useful log files for this situation:

  • /usr/local/cpanel/logs/error_log for cPanel application errors
  • /usr/local/cpanel/logs/safetynet_log for license and startup issues
  • /var/log/messages or journalctl -xe for system-level boot errors
  • /var/log/pure-ftpd/pure-ftpd.log for FTP-specific errors
tail -100 /usr/local/cpanel/logs/error_log
tail -100 /usr/local/cpanel/logs/safetynet_log
journalctl -xe | head -100

Look for the specific error message. Common ones and what they mean:

  • "Could not obtain a license" or "License check failed": the license server was not reachable at boot time. See Step 5.
  • "Address already in use": a previous instance of the service is still occupying the port. Kill the zombie process and restart.
  • "Permission denied" on a config file: file permissions changed, often from a botched update or security scan.

Step 4: Check the firewall

If services are running but you still cannot access WHM or cPanel from a browser, the firewall is the next suspect. On most cPanel servers this is CSF (ConfigServer Security and Firewall).

csf -l | grep 2086
csf -l | grep 2087
csf -l | grep 21

Check that ports 2086 (cPanel), 2087 (WHM), and 21 (FTP) are not being blocked. Also check whether CSF is in testing mode, which can cause it to auto-disable rules after a few minutes:

grep "TESTING" /etc/csf/csf.conf

If TESTING = "1", CSF is in test mode. Set it to 0 and restart:

csf -x   # disable temporarily to test
# confirm you can access WHM
csf -e   # re-enable
csf -r   # restart with production config

If you are using a different firewall (iptables directly, ufw, or a hardware firewall in front of the server), verify those rules separately.

Step 5: Check the cPanel license

cPanel checks its license against cPanel's servers. If the server came up before network routing was fully established, or if the IP address changed (for example after a cloud provider reboot), the license check may have failed. Force a re-check:

/usr/local/cpanel/cpkeyclt

If this returns a license error, check that the IP address the server is using matches the IP registered to your cPanel license in the WHM License Manager or your cPanel store account. IP changes after VM reboots on certain cloud providers are a common cause of this.

Step 6: Force a full service restart through cPanel's own tools

If the above steps have cleared the root cause, use cPanel's service manager to restart everything cleanly rather than individual service restarts:

/usr/local/cpanel/scripts/restartsrv_cpsrvd
/usr/local/cpanel/scripts/restartsrv_ftpd

These scripts handle the service startup in the correct order with the correct environment variables. They are preferable to direct systemctl commands when the cPanel layer needs to be involved.

Step 7: FTP specifically still not working

FTP has an additional layer of complexity: passive FTP requires a range of ports to be open, not just port 21. If active FTP connects but file transfers fail or directory listings hang, the passive port range is likely blocked. Check your FTP configuration:

grep PassivePortRange /etc/pure-ftpd.conf

Confirm that the passive port range (typically 49152-65534 or a subset configured in WHM) is open in your firewall. In CSF:

grep "TCP_IN" /etc/csf/csf.conf

Also worth noting: in 2026 there is very little reason to run plain FTP. SFTP (over SSH, port 22) and FTPS (FTP over TLS) are both far more secure and are not subject to the same passive port complexity. If you are still relying on plain FTP, this is a good moment to switch your workflow to SFTP.

When to call cPanel support

If you have worked through all of the above steps and services are still failing, it is time for cPanel's support team. Have the following ready when you contact them:

  • Output of tail -200 /usr/local/cpanel/logs/error_log
  • Output of journalctl -xe
  • Output of /usr/local/cpanel/cpkeyclt
  • Your cPanel license tier and the IP address of the server

If you manage multiple servers and this kind of issue is recurring, it may be worth reviewing your overall server administration approach. The article on WHMCS PHP configuration issues covers another common post-update headache on cPanel servers that is worth having in your toolkit.

The bottom line

WHM, cPanel, and FTP going dark after a reboot almost always comes down to services not starting on boot, firewall rules blocking their ports, or a license check failing on restart. Work through the steps in order, read the logs before you restart anything, and you will have a diagnosis within ten minutes. Random service restarts without reading the logs first will just cost you time.