Skip to content

WHM transfer hangs at "verifying remote system": what to check

A WHM transfer that stalls at "verifying remote system" is almost always one of four problems: trust, time, network, or license. Here is the order to check.

A WHM transfer that hangs at “verifying remote system” — sometimes for the entire timeout window of 10 minutes — is a frustrating place to be, because the UI offers no detail. The actual cause is almost always one of four things, and each leaves a fingerprint on the transfer log or on the remote system that diagnoses it in seconds once you know where to look.

What’s happening

The verification step uses an API token (or root password) to authenticate against the remote WHM, then runs a series of sanity checks: license is active, version is compatible, disk space exists, the source account list is fetchable. Any one of those can stall. Network-level issues (firewall, MTU, slow path) make the API call hang. Trust issues (wrong token, mismatched 2FA) make it retry. Time drift between the two hosts breaks the API token signature. A bad license on either side blocks everything.

How to verify

On the destination (the host running the transfer):

# transfer session log
ls /var/cpanel/logs/transfer_* | tail
tail -f /var/cpanel/logs/transfer_<latest>/<session>.log
# can the destination reach the source's API?
curl -kI https://<source-host>:2087/json-api/version
# time drift
ssh root@<source-host> date
date
# trust state
whmapi1 verify_api_token user=root \
  remote_host=<source-host> token=<token>

On the source:

# is the destination's IP in any deny list?
csf -g <destination-ip>
tail -f /usr/local/cpanel/logs/access_log | grep <destination-ip>
# license
/usr/local/cpanel/cpkeyclt

The fix

  1. Trust — the API token must exist on the source with sufficient ACLs (all:1). Generate via WHM > Manage API Tokens. Test with curl -k -H "Authorization: whm root:<token>" https://<source>:2087/json-api/version.
  2. Time drift — both hosts must be within 30 seconds of each other (NTP). Run chronyc tracking on each, or systemctl status chronyd. A 5-minute drift makes API tokens fail with vague errors.
  3. Firewall / CSF — the destination IP must be allowed on the source on port 2087 (WHM API). Add to /etc/csf/csf.allow, run csf -r. The transfer logs will show Connection timed out if blocked.
  4. License on either side — cpkeyclt on both. A source with an expired license refuses API calls; a destination with an expired license refuses to take accounts.
  5. Version compatibility — destination must be the same major version or one higher than the source. /usr/local/cpanel/cpanel -V on both. Upgrade the destination first if needed.

If the log shows the verification passed but the next step hangs, the issue moved to the actual transfer (file copy, database export). Stack Harbor handles transfer-session triage under migration solutions — start a conversation when transfers will not start.