Your server <server name> did not respond in a timely manner.

During the deployment pre-flight check process, you may run into the following error:

Your server <server name> did not respond in a timely manner. Please ensure that it is up and there are no firewalls blocking access.

This happens because DeployHQ wasn't able to complete its connection checks within 45 seconds.

Try again

This error can be caused by temporary network issues between our deployment servers and yours. If the problem is intermittent, simply retrying the deployment may resolve it.

Firewall

The most common cause of this is a firewall problem. You'll need to check that our IP ranges are allowed through your server's firewall, in particular, if you're deploying from multiple zones.

Verify hostname and port

If your server was previously working, your hosting provider may have changed the hostname or IP address assigned to your account. Log in to your hosting control panel and confirm the current SSH/FTP hostname and port match what you have configured in DeployHQ.

Some hosting providers use non-standard ports (for example, port 17177 instead of the default 22 for SSH). Make sure the port in your DeployHQ server settings matches what your host requires.

DNS Configuration

If you're confident the IP addresses are allowed through, and you can access the server, it's worth checking that DNS is working correctly (when connecting to a server via a hostname). If IPv6 is misconfigured for example, the process will timeout when connecting to your hostname.

When that's the case, it's advisable to try an IPv4 address directly.