Below are items and topics that may affect interactions between Files.com and Dropbox.

Case Sensitivity

Be aware of case sensitivity differences when copying, moving, or syncing files and folders between Dropbox and other storage locations. Dropbox is a case insensitive system whereas other systems may be case sensitive. This can cause files to be overwritten, and folders to have their contents merged, if their case insensitive names are a match.

File Name Limitations and Restrictions

Dropbox has file name limitations and restrictions. Restricted characters in file and folder names can cause issues when interacting with Dropbox. These issues can affect Remote Mounts, Remote Syncs, Automations and more.

Dropbox also prohibits certain types of file, including temporary files, symbolic links, resource forks, and system files. Refer to the Dropbox documentation for troubleshooting why certain files fail to transfer.

Reauthenticating

Certain remotes that use OAuth for authentication may require regular rotation of your credentials. When this is needed, you will see an alert in the top left of the web interface. You can click the link in that alert to re-authenticate and re-establish the connection to the remote.

The exact reauthentication period varies and can be from hours to weeks in duration. The default Dropbox web session duration is 4 hours, but this can be configured for a different duration by your Dropbox administrator. Please contact your Dropbox administrator, or refer to the Dropbox documentation, for more information.

What To Do When Your Remote Server Connection Is Disabled

Because Dropbox uses the oAuth authorization protocol, there may be future errors with the authentication even after your remote server is configured and running smoothly for some time. When one of those errors happens, Files.com will disable your Dropbox remote server connection and record the error in your External Events log.

When you've resolved the problem that caused the authentication error, you can re-enable your remote server by saving its configuration. Even if you don't make any changes to the configuration, saving the record will cause Files.com to re-enable the connection so that any associated mounts and syncs will begin working again.