Ports Used by Files.com
Files.com uses a standard set of ports for client and system connections. API and web traffic uses port 443. Protocol-based access uses different ports depending on the protocol.
If your network restricts inbound or outbound access by port, use the table below when configuring connectivity. Each protocol uses specific ports for control and data channels.
| Protocol / Service | Port(s) | Direction | Description |
|---|---|---|---|
| HTTPS / API / Web Interface | 443 | Inbound | Used by the Files.com web app, Desktop App, CLI, SDKs, and REST API |
| FTP(S) (Control) | 21 | Inbound | Standard FTP command channel |
| FTP(S) (Data) | 40000–50000 | Inbound | FTP data passive channel range |
| FTPS (Implicit) | 990 | Inbound | Implicit FTPS control channel |
| FTPS (Alternate) | 3021 | Inbound | Alternate explicit FTPS command port |
| FTPS (Implicit Alternate) | 3990 | Inbound | Alternate implicit FTPS command port |
| SFTP | 22 | Inbound | Secure File Transfer Protocol (SFTP) command and data channel |
| SFTP (Alternate) | 3022 | Inbound | Alternate SFTP port |
| AS2 (HTTP / HTTPS) | 443 | Inbound | Used for AS2 connections |
| WebDAV | 443 | Inbound | WebDAV access via HTTPS |
| Agent Direct Transfers | 4001–4010 | Inbound to the Agent host | Optional listener for Direct Transfers between the CLI App or Desktop App and a customer-hosted Agent, over TCP and UDP. This range is the default and is configurable on the Agent |
| Outbound Connections (all protocols) | Dynamic | Outbound | Used by Files.com for Remote Servers, SMTP, LDAP, and Webhooks |
If your firewall inspects or limits outbound connections, configure it to allow traffic for the ports listed above.
Files.com does not respond to ICMP traffic. ping and traceroute will not complete against Files.com hostnames or IP addresses even when the service is fully operational. To verify reachability, test an actual TCP connection to one of the ports above: an HTTPS connection to port 443 or an SFTP connection to port 22.