FTP Upload Stalls After 3 Minutes? Here's the Fix!

General Discussion
, , , ,
1

Topic Banner
Topic Banner1200×630 95.8 KB

FTP Upload Keeps Stopping

I’ve been trying to upload my PHP-Nuke Platinum package to my Xisto account, but it’s been a nightmare. The upload works for about 3 minutes and then just stops. I tried three different FTP clients—SmartFTP, CuteFTP, and even the command line—but same issue.

My Setup

  • File size: ~15 MB (PHP-Nuke Platinum archive)
  • Connection: Slow cable; download ~30 KB/s, upload ~5-10 KB/s
  • Bandwidth: Unlimited, so that’s not the bottleneck

SmartFTP seemed to hang when switching to a port in the 6000 range. Our host might be blocking those ports? I read somewhere that some hosts restrict high ports for FTP data connections.

The Solution That Worked for Me

I switched to FileZilla and it worked! It still times out occasionally, but it reconnects automatically. Turns out the issue was SmartFTP’s port selection. FileZilla’s passive mode handles it better.

Tips if You’re in the Same Boat

  • Use FileZilla (or any client that supports passive mode and port range customization)
  • In FileZilla, go to Edit > Settings > Transfer > FTP and set “Limit number of simultaneous connections” to 2
  • Enable “Keep-alive” in the connection settings to prevent timeouts

Anyone else run into weird FTP hangs on Xisto?

2

Topic Summary: FTP uploads to Xisto kept stopping after 3 minutes; switching from SmartFTP/CuteFTP to FileZilla with passive mode and keep-alive solved it.

:open_book: Topic Overview (Wikipedia):

The File Transfer Protocol (FTP) is a standard communication protocol used for the transfer of computer files from a server to a client over a computer network. FTP is built on a client–server model architecture using separate control and data connections between the client and the server. FTP users may authenticate themselves with a plain-text sign-in protocol, normally in the form of a username and password, but can connect anonymously if the server is configured to allow it. For secure transmission that protects the username and password, and encrypts the content, FTP is often secured with SSL/TLS (FTPS) or replaced with SSH File Transfer Protocol (SFTP). — Read more on Wikipedia

:movie_camera: Video Tutorial:

:books: Official Documentation & Reference Links:

---
title: FTP Upload Stalling Fix
---
flowchart TD
    A[Start] --> B{Stalls after 3 min?}
    B -- Yes --> C[Check firewall]
    C --> D{Passive mode?}
    D -- No --> E[Enable passive mode]
    D -- Yes --> F[Check timeout]
    F --> G{Timeout < 3 min?}
    G -- Yes --> H[Increase timeout]
    G -- No --> I[Check NAT/router]
    I --> J{FTP over TLS?}
    J -- No --> K[Enable TLS]
    J -- Yes --> L[Check client settings]
    L --> M[Test upload]
    B -- No --> N[Other issue]
3

FTP Timeouts: Deeper Diagnosis

Glad FileZilla worked for you. The port 6000 issue is common with some hosts that restrict passive FTP data ports. Xisto’s cPanel typically uses a range of passive ports (often 49152-65534), but SmartFTP might have been trying to use ports outside that range.

Additional Checks

  1. Configure FileZilla’s Passive Mode

    • Go to Edit > Settings > Connection > FTP
    • Under “Passive mode”, select “Failover” or “Use the server’s external IP address”
    • If your Xisto account is behind a firewall, you might need to enter the external IP manually (check in cPanel > FTP accounts)

  2. Firewall / AV Interference

    • Windows Firewall or antivirus (like Norton) can interfere with FTP data channels. Add FileZilla as an exception.

  3. Check cPanel Settings

    • In Xisto’s cPanel, under “FTP Connections”, you can view current sessions and force close stuck ones.
    • Make sure you’re using the correct FTP server: ftp.yourdomain.xisto.com or your IP.

Alternative: Use SFTP via SSH

If FTP continues to misbehave, Xisto also offers SFTP (SSH File Transfer Protocol) on port 22. It’s more secure and handles firewalls better. In FileZilla, just change the protocol to SFTP.

Give those a try and report back if the timeouts persist!