IP Addresses Used For Connection

If you have a Custom Domain installed on your site, Files.com has provisioned two dedicated IP addresses for your site and will use them by default for outbound connections to the remote server. Provide these two IP addresses to your counterparties and ask them to whitelist them in any applicable firewall.

If you do not have a Custom Domain installed on your site, you do not have Dedicated IP Addresses provisioned for your site, and Files.com will use addresses from the Files.com owned IP range for connecting outbound to the remote server. If your counterparties maintain an IP address whitelist, they will need to whitelist that range. A single firewall rule covering the range allows all Files.com traffic.

Customers often ask for Dedicated IP Addresses as a way to avoid having to ask their counterparty to whitelist the Files.com owned IP range. Files.com offers this for Remote Server connection purposes by adding a Custom Domain to your site. The Custom Domain provides the justification for the dedicated IP address: FTP, unlike HTTP, requires every custom domain to be hosted on a dedicated IP address in order to have a custom SSL Certificate that matches the domain.

If your counterparties restrict outbound access via a firewall, they will only need to whitelist your two dedicated IP addresses rather than the Files.com owned IP range.

Once provisioned, dedicated IPs are used for both inbound connections to your site via your custom domain and outbound connections from Files.com to applicable Remote Servers used for Sync and Remote Server Mount.

By default, Files.com uses your dedicated IP addresses for outbound connections to FTP, SFTP, WebDAV, and S3 Compatible remote servers. You can disable the use of your dedicated IPs in these circumstances if you need to. For example, you might do this if your counterparty has already whitelisted the main Files.com IP range.