We use cookies
We use cookies to optimize our website. By continuing to browse the site, you agree to our use of cookies.
New design
Control panel
  • Русский
  • Українська
  • English
  • UAH
  • USD
  • RUB
  • EUR
  • 0-800-307-307 Hotline
  • +38 (044) 392-74-33 Kiev
  • +38 (057) 728-39-00 Kharkiv
  • +38 (056) 794-38-31 Dnipro
  • +38 (032) 229-58-93 Lviv
  • +38 (048) 738-57-70 Odessa
  • +38(093) 170-15-42  Life
  • +38 (067) 400-88-44 Kievstar
  • +1(888)393-24-51  USA, Toll free
  • +44(131)507-01-14  Great Britain
  • +7 (499) 348-28-61 Moscow "Connection terminated after XX seconds of inactivity" error in FileZilla

Sometimes when working with FTP errors of the form may occur:

Status: Connecting to XXX.XXX.XXX.XXX:21 ... Error: Connection interrupted after 20 seconds of inactivity Error: Unable to connect to server

Such errors indicate that the connection to the server failed. The reasons for this problem may be:

  • Server unavailability.
  • Problem with one of the nodes on the route to the server.
  • Closed port FTP (port 21 is used by default).
  • Closed one of the ports that are allocated FTP when connected.
  • Using FTP+ SSL (FTPS / implicit FTP).
  • Active transmission mode.

To diagnose the problem, you need:

  • Execute tracing to the server to connect to. If the problem is present during the trace phase, it may be worth contacting your ISP to check the address availability problem.
  • If the trace was successful, then you need to connect to the server using telnetusing port 21 (or the port that is used FTP-server). If the connection fails, you need to contact your network administrator or Internet service provider about blocking port 21.
  • If you have problems while tracing, checkwhether your IP address is blocked by DDoS protection.
  • Check the installed encryption method. If FTPS is installed (implicit FTP), change it to FTPES (explicit FTP) or regular FTP without encryption... It is recommended to use "Explicit FTP via TLS if available. "
  • Check the transmission mode. Please note that if you are behind NAT or Firewall with rules for filtering incoming requests by potential ports FTP worth using passive mode.

If the actions described above did not help in solving the problem and finding its causes, then you need:

  • Clarify your IP address. (For example, this can be done on the website 2ip.ua).
  • Repeat the above steps and save their results as text or screenshots.
  • Contact us at technical support and provide the obtained data for additional verification of the problem.