Troubleshoot SSH timeouts and connection refusals Print

  • timeout, connection refused, ssh, network
  • 0

Quick answer

A timeout or connection refusal happens before an AI assistant can edit your site. Verify the network destination and port with an ordinary client first. A timeout, an explicit refusal, and a key-authentication error point to different stages of the connection.

Before you start

Use the service's actual SSH hostname and port, not a guessed value. A Cloudflare-proxied website hostname may not be the right SSH endpoint. Confirm your current public IP if the provider uses an access allowlist.

What to do

  1. Check that your internet connection works and that the server name resolves to the destination supplied for your service.
  2. Try the documented port with a normal terminal client. Record whether the result is timeout, refused, host-key warning, or authentication failure.
  3. Review local firewall, VPN, corporate network, and provider IP restrictions. Ask support whether the server is reachable from your network.
  4. Once network access succeeds, troubleshoot username/key authorization separately and only then retry the assistant workflow.

Check the result

A successful connection should progress to verified server identity and authentication. Confirm the account and folder with a harmless read before changing files.

If something does not work

Do not repeatedly guess ports, disable security software, or open server-wide firewall access. Send support the hostname, port, approximate time/time zone, your public IP if requested securely, and the exact sanitized error.

Related help

Official references

Reviewed October 31, 2026. Interfaces, vendor availability, and account features can change. Check your current account before making changes.


Was this answer helpful?

« Back