FTPMonitor / Guides / TCP connection timeout (firewall issue)

TCP connection timeout (firewall issue)

Why FTP/SFTP connections time out and how to diagnose firewall, routing, or allowlist blocking.

Diagnose this automatically

Test whether the network port is reachable before investigating authentication problems.

terminal
npx ftpmonitor check --protocol sftp --host example.com --port 22
Shareable output
terminal
npx ftpmonitor check --protocol sftp --host example.com --port 22 --format slack --copy

Prefer the browser? Run the same check on the homepage.

A TCP timeout means your request didn’t get a response at all.

This is usually a firewall/security-group block, routing issue, or the service is only reachable from a private network/VPN.

Common causes

  • Inbound firewall/security group blocks the port
  • Server is private/internal-only (not reachable from the public internet)
  • IP allowlist missing your source IP
  • Network routing/VPN required
  • Upstream device silently drops packets

Fix checklist

  1. Confirm protocol + port with the vendor/admin.
  2. Ask the server owner to verify firewall/security-group rules on the server side.
  3. Check IP allowlist requirements and add your source IP.
  4. If the host is internal, run checks from inside the network/VPN.

Quick commands

nc -vz <host> <port>
telnet <host> <port>
Related
Diagnostics powered by FTPMonitor CLI