ssh time out when connecting from deployhq

Deployments from DeployHQ were working without a problem until a week ago, now when I try to deploy I get the following response on deployHQ:

‘Your server Production did not respond in a timely manner. Please ensure that it is up and there are no firewalls blocking access.’

I have restarted ssh.

I am able to ssh into the machine from the command line using my own ssh key.

I checked that the deployHQ IP ranges are whitelisted in the firewall: SSH TCP 22 [deployHQs IP addresses]

the auth file for the user that DeployHQ uses to connect contains the correct public key.

deployHQ has the correct hostname, username and key set.

Nothing has changed on the server as far as I know.

What else can I look at, what should the ‘ss’ command display if ssh is working correctly?


Submit an answer
You can type!ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Accepted Answer

Hello, @ecell100

You’ve mentioned that you’re using hostname in order to connect. May I ask if you’ve made any recent DNS changes? Can you try to connect using the IP address instead of the hostname to see if this will make a difference?

Regards, Alex

Hey, @ecell100

Thanks for confirming this, I’m glad this is now sorted!

Sometimes there might be an issue with DNS propagation and resolving hostnames, so using an IP address instead of the hostname when you face issues like this one is recommended.

Hopefully if anyone else is having the same issue will be able to sort them by using the IP address directly as well.

Regards, Alex


I changed the deployment target to use an ip address, and (after removing an extra folder in the deployment path that deployhq didn’t like), it worked!

So, why would this be the case?