Skip to main content

Connection Settings

An SFTP connection needs a reachable hostname, compatible encryption, and a Files.com user that is allowed to connect. The settings below apply to clients connecting to your Files.com site.

Account and Authentication

The account must be enabled, and its Protocol Access must allow SFTP. Access can come from the user's settings or a Group; when the site manages protocol access through Groups, only the Group settings apply.

An account set to None (Use SSH or API keys) authenticates with an SSH/SFTP key or an API key supplied as the password. It cannot use an account password. Other authentication methods support different credentials: Password and SFTP/SSH key (SFTP only) requires both, while SSO passwords work directly over SFTP only with Active Directory or LDAP.

Register the user's public SSH key before connecting with its matching private key. The server's host key serves a different purpose: it lets the client confirm the identity of the server. Use the appropriate host key fingerprint when configuring a new connection or migrating an existing service.

When a password change is required on a Password account, it blocks SFTP login with the user's username, including SSH-key login, until the user changes the password through the web interface. API-key authentication is independent of this password requirement.

For accounts with Files.com two-factor authentication, the protocol authentication requirements determine the supported method and how to supply the code. An SSH key alone does not satisfy that requirement. Unattended transfers use a dedicated machine account with key authentication and Shared/bot user enabled so each connection can proceed without an interactive challenge.

After a password and code establish an SFTP sign-in, the same combination can cover parallel connections and later reconnects from the same source IP address to the same Files.com server address, within the first sign-in's session limits. The code-reuse rules explain when a fresh code is needed.

Hostname

Set the hostname to [your_subdomain].files.com or to the custom domain for your site, if applicable.

We do not recommend using IP addresses, because they may change. Using an IP address is not officially supported, and we cannot assist with troubleshooting if you choose to do so.

Port

Use the default port 22.

If port 22 is blocked or interfered with by your corporate firewall, try port 3022 as an alternative.

If neither port is reachable, the network or firewall administrator needs to allow the connection.

Firewalls and IP Whitelisting

The client's network must allow outbound SFTP traffic on port 22 or 3022. When a firewall uses an IP whitelist, it must allow every address that can serve the chosen hostname; allowing only one address can cause intermittent failures.

For a Custom Domain with dedicated addresses, allow every address assigned to that domain and connect using its hostname. With a Files.com-managed certificate for the Primary Custom Domain, [your_subdomain].files.com also uses the Primary Custom Domain's dedicated addresses. With a certificate you provide for the Primary Custom Domain, the Files.com subdomain continues to use the general pool. Subdomain Addresses and Certificates explains this distinction.

For a hostname that uses the general pool, allow the Files.com owned IP range. A rule covering the range allows the connection to use any server in the hostname pool.

These are destination addresses allowed by the client's firewall. A Files.com IP Whitelist controls the source addresses from which users can connect; it is a separate access control.

Ciphers

Your SFTP app and Files.com will only connect if both sides agree to use a secure cipher. Insecure ciphers may be rejected by either side.

Configure your SFTP app to use a supported, secure cipher. Refer to your app's documentation to learn how to configure ciphers for your connection.

Timeout

Your SFTP app will connect to Files.com using its default timeout setting.

Very short timeout settings can cause connection issues, so set the connection timeout value to 120 seconds or more.

Retry Logic

Some SFTP apps include a built-in retry feature. Your app will connect to Files.com using its default retry settings.

If this setting is configurable, we recommend setting your app to attempt 3 connection retries, with 10-second intervals between retries. This allows a failed connection to one server in the hostname pool to automatically retry via another pool member.

Keepalives

Files.com gracefully disconnects SFTP sessions after 120 seconds with no new commands or data transfer. This prevents unused sessions from occupying connection resources.

Most SFTP apps complete transfers in progress and reconnect once the user issues another command. These idle timeouts are normal, and most SFTP apps handle them without issues.

Some apps do not handle these timeouts gracefully. To prevent idle timeouts, many apps offer a "keepalive" setting. Files.com supports keepalives to keep the session open without sending new commands.

If your app aborts a transfer or errors out due to the idle timeout message, enable keepalives every 30 seconds to maintain the SFTP connection and avoid timeout messages. With keepalives enabled, the app sends either a null packet or a dummy command to simulate user interaction between the app and our SFTP service.