The items below address the most common FTP connection settings customers need when connecting to Files.com.

Hostname

Set the hostname to [your_subdomain].files.com or, if your account uses a custom domain, use that address instead. Avoid connecting directly to an IP address. Although some customers do so for specific reasons, Files.com does not officially support IP-based connections.

Encryption

Enable encryption in your FTP client whenever possible. Most clients list this as a protocol option, such as FTPS or FTPeS, where the “S” stands for secure. Using these settings ensures that your data remains encrypted while it’s in transit between your client and Files.com.

If your client cannot use encryption, you can still connect by allowing unencrypted FTP in your Files.com account settings. Only use this option when encryption is not supported, since unencrypted connections send data in plain text and may expose sensitive information.

Files.com supports both Implicit and Explicit FTPS encryption modes.

Port

Your port selection can help you work around corporate firewalls. The default FTP port 21 is frequently blocked or restricted. If you experience connection problems, try port 3021 as an alternative.

Some clients use Implicit security mode, which operates on port 990. For that mode, Files.com also supports port 3990. Testing these alternate ports often resolves firewall-related issues and restores connectivity.

Active vs Passive Mode

The FTP protocol supports two data connection modes: Active and Passive. Files.com recommends using Passive mode for all FTP and FTPS connections.

Timeout

Increase the connection timeout in your client to 60 seconds, if the option is available. A longer timeout helps maintain stable connections when network latency is high.

Retry Logic

Configure your client to retry failed connections 3 times at 10-second intervals. This gives the client time to contact a different server if one host is temporarily unreachable.

Files.com hostnames resolve to multiple servers in separate datacenter locations. Make sure your client attempts connections to multiple IP addresses when possible to take advantage of this redundancy.

Keepalives

Files.com automatically ends FTP sessions that remain idle for more than 60 seconds to conserve server resources. Most clients handle this gracefully, but some may not.

If your client disconnects or errors out after being idle, enable a keepalive feature. Sending a null packet or lightweight command every 30 seconds prevents the connection from timing out. Clients will still complete transfers in progress and reconnect automatically for new commands. Keepalives ensure your session stays active and stable during longer workflows.