If you see the error
No route to host during the pre-deployment checks, it could mean the following:
- The server you're trying to connect to could be down. You could try pinging the server to check it responds.
- The firewall on the server is blocking access to port 22 (or the configured SSH port on the server if not using the default port). In this case, you will need to allow access to the appropriate port through the firewall or allow our IP ranges.