IP Addresses Used For Connection

The remote server's firewall must allow inbound connections from the addresses Files.com uses to reach it. The source addresses depend on the Remote Server's connection routing settings.

For supported Remote Server types, Files.com uses your site's dedicated IP addresses by default when they are provisioned. A Remote Server can also use the outbound addresses assigned to a specific Custom Domain. This lets you keep each partner connection on the addresses that partner has allowlisted, even when several domains and sets of addresses belong to the same site.

FTP, SFTP, WebDAV, and S3-compatible Remote Servers support dedicated addresses. Check the provider's connection settings for other Remote Server types. The Custom Domain choice is available wherever dedicated-IP routing is offered; it selects the addresses for operations that use that routing.

Dedicated IP Routing

Site Administrators and Workspace Administrators choose the routing when adding or editing a Remote Server. In Connection Routing, selecting Use site's dedicated IPs for outbound connections (recommended) provides a Custom Domain selector. Leaving it at Use the site's default dedicated IP addresses retains the site's default routing. Selecting a domain makes connections that use dedicated-IP routing originate from that domain's outbound addresses.

The selector lists eligible domains on the same site that are assigned to the Remote Server's Workspace, plus domains shared from the Default Workspace. A domain needs the Site Alias destination and eligible outbound IP addresses. A Site Administrator configures its Workspace availability and provisions its addresses; Workspace Administrators can select available domains without access to the Custom Domains settings page.

Each choice shows its outbound addresses. Give every address shown to the remote server operator, because connections may originate from any of them. After saving, the Remote Server's details page shows the selected domain's outbound addresses in Connection Routing. Users who can use the Remote Server but are not Site or Workspace Administrators see the administrator's selection as read-only text and cannot change it.

Saving tests the connection using the selected addresses. A failed connection test displays an error but does not prevent the configuration from being saved; a saved configuration alone does not establish that the remote firewall accepts the connection.

Clearing the Custom Domain selection restores the site's default dedicated addresses. Switching to the Files.com general IP pool or Agent routing clears the selection. Coordinate a routing change with the remote operator so the allowlist covers the new source addresses.

Unavailable Custom Domains

If a selected domain is deleted, loses eligible outbound addresses, or becomes unavailable to the Remote Server's Workspace, connections fail rather than switching to the site's default addresses. This keeps the connection from using addresses outside the set chosen for that partner.

The edit form retains an unavailable selection as a disabled option with the warning This Custom Domain is not available for outbound Remote Server connections. Users with read-only access to the selection see Connections will fail while the administrator-selected Custom Domain is unavailable. A Site Administrator can restore the domain's availability, or a Site or Workspace Administrator can choose another eligible domain or clear the selection. Confirm the resulting addresses with the remote operator before resuming the workflow.

Connections From the General IP Pool

Without dedicated addresses, or when their use is disabled for the connection, allow the Files.com owned IP range. A rule covering that range accommodates connections from Files.com's shared pool. You can choose this routing when the remote system already allows the shared range.

Connections Routed Through an Agent

When a Remote Server uses Agent routing, the Agent connects to the remote service from its own network. Allow the Agent host's address, or its network's outbound NAT address, as seen by that remote service. The Agent also needs its own outbound connection to Files.com.