Header

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.

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.

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.

Tree

Proudly powered by Katapult. Running on 100% renewable energy.