Troubleshooting Remote Server Mount

A mount depends on the remote connection and storage as well as Files.com access and processing settings. Start with the failed operation and its path: inability to connect, a denied replacement, a missing folder, and slow file delivery call for different checks.

Use the Outbound Connections log and the workflow's own results to identify the time, connection, path, and operation. Compare them with the remote service's records. Test with the same connection identity and route so the result addresses the failure being investigated.

Mount Setup Issues

A conflicting <type> behavior exists at /path/to/folder/ indicates a conflict with the mount setup restrictions. The local folder must be empty, cannot be within another mount, and cannot be a protected Partner Channel folder. The mount exposes the remote folder rather than merging it with existing content.

Storage Location (Region) applies only to native storage. A setting inherited from above the mount does not move the remote files. Select their region on the remote storage system instead.

Authentication or Firewall Issues

For an authorization failure, identify the credential the Remote Server actually uses. Update shared credentials in the Credential Manager, or complete re-authentication when an OAuth authorization can no longer be renewed. For example, an expired Azure SAS token stops the remote connection even while the Files.com user can sign in normally.

For network access, check Connection Routing and give the remote operator every source address displayed for that route. A selected Custom Domain can have different addresses from the site's defaults. General-pool and Agent connections use their own source addresses.

An unavailable administrator-selected Custom Domain causes failure rather than fallback to default addresses. Restore its eligibility or select another permitted route and coordinate the allowlist change. The routing reference explains the availability warning.

Connection Timeout

Match the failed stage to the protocol: name resolution, connection establishment, authentication, listing, or transfer. Ask the operator whether the remote service received the attempt. No matching record points toward the host, port, route, or network path; an accepted connection that stalls also needs investigation of server load and responses.

FTP can authenticate while its passive data ports remain unreachable. Use the protocol's specific diagnostics for FTP/FTPS, SFTP, or WebDAV.

Operation Permissions

Check both the user's effective Files.com folder access and the connection account's rights on the remote path. Match those remote rights to the failed operation: an account allowed to list and download can still be unable to replace a file. A copy or move overwrite requires remote delete access as well as write access.

Test the failed operation with a disposable file in an agreed location outside live processing. A new-file upload does not test replacement. A successful sample in a differently permissioned folder does not prove the original path works. Have the remote operator correct the required right on that path rather than replacing the shared connection with broadly privileged credentials.

Invalid File or Folder Names

Compare the rejected name with the remote provider's character restrictions, case behavior, and length limit. Some systems count the whole path and any temporary suffix rather than just the final filename. Files.com's own full-path limit is 550 characters.

Correct the name at the source when every delivery needs the revised path. Exclude an item only when the workflow does not need to transfer it; exclusion does not deliver a compatible copy under another name.

Invalid File Sizes

Check the destination's file-size and storage-capacity limits against the failed item. Repeated retries do not let an item exceed a fixed provider limit. For Box or OneDrive uploads whose size is not supplied in advance, check the large-file buffering requirement.

Slow Transfer Times

Distinguish slow listings from slow contents transfer, and client upload completion from buffered onward delivery. A folder with many small files requires many operations even when its total data size is modest. Concurrent jobs can also compete for the remote account's capacity or trigger provider rate limits.

For a slow copy or rename, identify the connector's actual operation. An FTP or SFTP copy reads and uploads the entire file, while a provider-side object copy does not relay those contents. A folder rename can process every child. Measure duration and usage on the affected connection, using the same operation and file sizes.

Check the actual network route, endpoint region, connection limit, and provider responses before increasing parallelism. The transfer measurement method compares native and mounted storage to help isolate the client-facing and onward paths. Regional routing changes the network path and can help or add distance depending on the endpoints. An eligible cloud transfer may instead use Direct Routing from the client's network.

Missing Folders and Concurrent File Changes

Compare missing or renamed paths with activity performed directly on the remote system as well as through Files.com. Several processes using the same working folder can remove a source, replace an output, or move it while another operation still needs it. Coordinate completed-file handoffs rather than repeatedly retrying against changing contents.

Missing-folder handling preserves associated configuration during remote absence; it does not preserve the file contents. For failover or health-check problems, investigate High Availability backend status separately from ordinary file-access failures.

Incomplete Moves or Replacements

If an operation fails after changing some paths, inspect its results and both remote locations. A copy-and-delete move can leave both names when deletion fails. A tree move can leave different files at each location. A requested overwrite can remove the old destination before its replacement fails.

Keep dependent applications from consuming an incomplete destination, and reconcile the affected files before repeating the operation. Repeating a broad overwrite can remove files that another process has since created. Use the remote system's recovery tools when earlier contents are needed; the mounting Site's native archive does not hold those remote files. File Operations explains the completion and recovery boundaries.