Adding a Remote Server

Any Site Administrator can add a new remote server to your site. Workspace Administrators can add remote servers within their Workspace. Users assigned an Integration-Centric Profile can add their own servers, limited to the types of server their profile expects.

Each remote server type has its own connection requirements, so the details you need on hand depend on the type of server you are adding. You can also select an existing credential from the Remote Server Credential Manager instead of entering new secrets each time.

Connections Back to the Same Site

A Remote Server must connect your site to an external system or to a different Files.com site. Files.com does not allow a site to be added as its own Remote Server. This applies both to the Files.com Remote Server type using an API key from the same site and to FTP, SFTP, or WebDAV connections using the site's own hostname and a user from that site.

Routing an operation out through a Remote Server and back into the same site adds an unnecessary connection to work Files.com can perform directly. Use the File Manager, API, or an Automation to operate on the source and destination paths within your site. To transfer files between separate Files.com sites, use a Files.com to Files.com Remote Server with an API key from the other site.

Maximum Connections

Some types of Remote Server allow you to configure a Max connections setting that restricts the number of concurrent parallel connections Files.com makes to that server.

Decrease this value if the remote server cannot support multiple concurrent connections.

For example, some FTP servers allow only 2 concurrent connections per user account, so any value above 2 in this setting causes poor throughput and warning messages on the remote server.

Buffered Uploads

Some types of Remote Server allow you to configure a Buffered Uploads setting that determines the route data transfers take between the user and the Remote Server.