Troubleshooting Remote Server Mount

A Remote Server Mount brings another system's files into the Files.com file tree, but the remote system still determines whether each operation can succeed. Credentials, network access, file restrictions, and activity on the remote can all affect the result. Understanding where an operation fails helps administrators restore access without changing unrelated settings.

Start with the scope of the problem. A mount that cannot connect suggests a different cause from one that transfers most files but fails on a particular name or size. A transfer that stalls needs timing and connection details; a file that disappears while several processes use the folder calls for a review of concurrent activity.

Use the detailed error message and the failed operation together. Check the remote system as well as Files.com, especially if people or applications also modify the files directly there. For a previously working mount, compare recent changes to credentials, permissions, network rules, and the remote service before altering the mount configuration.

For a High Availability Mount, use the backend status, shared storage, and canary-file checks when investigating failover or health-check problems.

Mount Setup Issues

When setting up a Remote Mount, a warning message saying A conflicting <type> behavior exists at /path/to/folder/ indicates that you are attempting to set up the mount on a prohibited folder.

Check that the folder is empty. The mount will expose the remote folder at that path; it does not merge the remote folder with existing Files.com content.

A mount is mutually exclusive with a folder's geographic Storage Region setting. A folder can be configured with either a Remote Mount or a Storage Region, but not both. When a mount is configured for a folder, it overrides the Storage Region setting of that folder.

Authentication or Firewall Issues

Most authentication failures come down to incorrect credentials, but they can also stem from IP address restrictions enforced by the remote server.

If the Remote Server uses a saved credential, update it in the Remote Server Credential Manager and re-test the connection.

If the remote server enforces an IP address allowlist, check the following settings.

Check Connection Routing on the Remote Server's details page. If it selects a Custom Domain, give the remote operator every outbound IP address shown there. These can differ from the site's default dedicated addresses. For default dedicated routing, use the site's default addresses; for general-pool or Agent routing, use the addresses appropriate to that route.

If an administrator-selected domain is unavailable, connections fail without switching to default addresses. The edit form shows the saved domain as a disabled choice with an availability warning. Have a Site Administrator restore its outbound eligibility or Workspace availability, or select another eligible domain and coordinate the new allowlist with the remote operator. See Unavailable Custom Domains.

Connection Timeout

If the connection to the remote mount times out then the remote server is most likely unreachable, offline, incorrectly configured, or blocked by a firewall.

Remote Server Issues

If the remote server has a temporary issue, such as being temporarily offline or unavailable, accessing the remote mount will fail. Subsequent attempts may succeed once the remote service is accessible again.

If the remote server has a permanent issue or limitation, such as not accepting file sizes greater than 2GB or having incorrect access permissions set, affected files will never upload or download successfully.

To resolve these issues, confirm that the correct access permissions are set on the remote server and communicate any known limitations to your users. For example, if the remote server cannot accept file sizes greater than 2GB, tell your users to keep file sizes below that limit.

For a permission failure, inspect the failed operation and remote path in the Outbound Connections log. Check both the Files.com user’s effective folder access and the connection account’s remote permissions. A successful list or download does not establish permission to write, replace, rename, or delete. A copy or move overwrite also needs remote delete permission.

Test the failed operation with the original connection and an agreed sample. Use a disposable file in a folder outside live processing, and confirm the result on the remote system. For a replacement, rename, or deletion test, use only that sample; keep other users and scheduled work away from it. If the test folder has different permissions, its success does not prove the original path works. Have the remote administrator correct the required right on that path and verify it with an agreed sample rather than replacing the shared connection with broadly privileged credentials.

Invalid File or Folder Names

Remote servers often prohibit certain characters in file and folder names. When you see issues with invalid file or folder names, modify those names to remove the restricted characters.

Remote servers may also restrict the length of the file or folder name. Common length limits include 160 and 255 characters.

Some remote servers calculate the total length as just the file or folder name including any extension. Others calculate it as the sum of the whole folder path, file name, extension, and temporary suffix.

To resolve this issue, shorten the names of files and folders so they fall below the length limits of the remote server.

On the Files.com side, the path limit is 550 characters for the sum of the full path, including folder names.

Invalid File Sizes

Some remote servers enforce maximum file size limits. Check the remote server's documentation for details on any size limits or restrictions.

Remote servers that use APIs or HTTP-based connections often do not support zero-byte files.

Slow Transfer Times

Slow transfers and long transfer durations can be caused by low network bandwidth, high network latency, a large number of files being transferred, large file sizes, network throttling, remote system performance, local system performance, encryption methods, and session time limits.

The physical limitations of a network or system cannot be circumvented. If sending a 10GB file across the internet to the remote server takes you 2 hours, then sending the same 10GB file across the internet to the remote server will take us 2 hours as well, assuming both connections to the remote server are identical.

Enabling regional data routing causes all data transmissions to your site's remote servers to funnel through your site's region. When accessing Remote Mount folders, this setting improves transfer speeds for connections within the same region, and it decreases speeds for connections with other regions.

Concurrent File Changes

Race conditions arise when files on a Remote Mount are changed through multiple systems or processes simultaneously, for example when a Sync deletes a source file while another process is modifying the same file directly on the remote system. They aren't always obvious, and sometimes show up in logs as errors like "not found" or "destination already exists".

Coordinating Changes

Wherever possible, avoid setting up a Remote Mount to a "working directory" where files are likely to be in use by remote processes.

The remote system may implement file locking, which prevents more than one user from editing the same file at the same time.