Known Issues
Performance Considerations
To reduce the number of requests to the remote server for mounted volumes, we recommend the following settings when running in Online connect mode.
Choose View → Hide Preview (⌘⇧P)
Disable View → Show View Options → Show icon preview
Choose File Explorer → Folder Options.
Check Always show icons, never thumbnails
Check Display File Icon on thumbnails
Uncheck Show preview handlers in preview pane
Characters to avoid
The following characters should be avoided within file and folder names.
:(colon)/(forward slash)\(backslash)
<(less than)>(greater than):(colon)"(double quote)/(forward slash)\(backslash)|(vertical bar or pipe)?(question mark)*(asterik)
Known Issues
Can only open single PDF in Adobe Acrobat Reader
This is a known bug in Adobe Acrobat Reader when opening documents from a network volume. As a workaround uncheck edit → Preferences… → Security (Enhanced) → Enable Protected Mode at startup.
Adobe Documentation: Protected mode (Windows)
rsync fails with error
If your server does not accept the creation of . temporary files you might need to add the --inplace when running rsync.
High CPU usage when working with Sublime Text
When working with Sublime Text we recommend turning off indexing by adding the following setting to your user preferences in Sublime Text.
"index_files": falseYou might want to turn off Git support in Sublime which has caused high CPU usage for some users when scanning
.gitfolders.
"show_git_status": false
Sharing a mounted drive in local network
It is not possible to share a mounted drive within the local network.
Changes from server not immediately visible
The directory listing in Finder.app or File Explorer may become out of date when another application is addin , removing, or modifying files on the server. You can force File Explorer to refresh the directory listing with F5. On macOS, choose Reload from the Finder Extension menu. Enable Sync → Index files in Preferences to look for remote file changes every 10 minutes.
Cache uses a lot of disk space
The cache directory is located in %LocalAppData%\Cyberduck\Cache on Windows or in ~/Library/Group Containers/G69SCX94XU.duck/Library/Application Support/duck on macOS by default. You can choose another disk for storage of files to be stored in the local cache. You can clear files cached on local disk with the Delete on local disk context menu option.
Missing sync status icons
Finder
When you have other applications installed that register a Finder Extension (macOS) for the volume mounted, the status icon may not appear. This has been reported for the following applications:
Araxis Merge
BetterZip
Sophos. Documented in SAV for Mac OS - Sophos Finder Extension Known Issues
Please check in System Preferences → Extension → Finder for other applications that may override the badge icons.
Note
If none of those applications are in use, a Finder re-launch can make the badge icons appear again.
Windows
Windows has a limitation on the number of applications that can register for bagde icons in File Explorer. You will need to either uninstall other applications or edit your registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\ShellIconOverlayIdentifiers.
You can find this well documented by Microsoft at Sync icon overlays are missing.
Operating system specific issues
Finder.app does not show files prefixed with . on remote volumes
You can work around this by setting defaults write com.apple.finder AppleShowAllFiles YES in a Terminal.app window and restart Finder.app using → Force Quit … → Finder → Relaunch. If you are running macOS Sierra (10.12) you can choose ⌘⇧. to toggle files starting with a dot to show in Finder.app.
Original document can’t be changed (Preview.app)
Files opened in Preview.app and edited cannot be saved at the original location but the message “The original document can’t be changed, so a duplicate with your changes has been created” is displayed in the title bar. As a workaround, you can set a custom mount point in Preferences → Connection → Mount Location for volumes such as a ~/Volumes/ folder in your home directory.
Enable application icon in Dock
As a utility application with no application windows, no icon is displayed in the Dock but only in the system status bar. If you want to enable the application icon to appear in the Dock set the following property
defaults write io.mountainduck application.dock.icon.enable true
Mounted volumes do not appear on the desktop
Navigate to volumes using ⌘⇧C in a Finder.app window or choose Finder → Preferences … → General → Show these items on the desktop: Connected Servers to make the volume appear on the desktop. Mounted volumes are also listed in the Finder.app sidebar in Favorites.
Search in Finder.app (Spotlight)
The Spotlight indexer does not work on remote volumes
Multiple Mountain Duck Finder Extensions processes
The system may launch additional copies of Mountain Duck Finder Extension whenever an Open or Save dialog is displayed. This means there may be multiple copies of the extension running at once, and some may be very short-lived.
Connection Interrupted
It may be that Finder closes the connection because Mountain Duck hasn’t answered fast enough on the request of Finder. Although Finder indicates that the server connection is interrupted it isn’t as Mountain Duck is still connected to the server.
This is an issue within the operating system that can occur to any network drive.
Additional ._* files saved on remote volumes
The ._* files contain metadata about the files some applications write in additional to the file content. On macOS, this metadata can be stored alongside the file on the filesystem, but on remote volumes, with no metadata suppport, an auxiliary file is created to contain this information. You can delete metadata on files using xattr -d <filename>.
As of version 2.1, extended attributes are only saved in a temporary location and not stored on the mounted remote volume. If you want to revert to saving extended attributes to the server, enter in a Terminal.app window
defaults write io.mounteinduck fs.filesnames.metadata.enable false
If you want to delete metadata files, you can open a Terminal.app window and enter dot_clean -m <folder>.
File system driver isn’t set up properly
Error: A volume has been accessed for which a file system driver is required that has not yet been loaded
If you get this error message you most likely haven’t restarted your system after the installation or update of Mountain Duck. Restart your system to resolve this error. If a system restart doesn’t resolve the error try to repair Mountain Duck followed by an application reinstall if this doesn’t work either. Additionally, make sure no antivirus software is interfering with the operation of Mountain Duck.
Missing files in Windows Explorer
Windows has a limitation on the maximum path length. It might happen that Mountain Duck exceeds this maximum for long file names when trying to create placeholders in the local cache. If Mountain Duck is unable to create a placeholder file for a remote file it will not appear in the Windows Explorer listing.
To work around this Windows limitaion you can enable long path support in Windows 10 as of version 1607.
Open the Local Group Policy editor (search for Edit Group Policy)
Navigate to Local Computer Policy → Computer Configuration → Administrative Templates → System → Filesystem
Double-click the Enable NTFS long paths option and select Enabled
Please refer to Maximum Path Length Limitation.
Multiple File Versions
This is expected behavior within the Online mode as Windows Explorer will first create an empty file followed by writing to the file. Due to this process, you’ll see two versions within the versioning on your server. Within the Smart Synchronization mode the empty file won’t be synced and the upload is deferred until the file has been fully copied.
Windows Search Indexer
The Windows Search indexer does not work on networks drives.
Windows sessions
Mountain Duck requires an interactive user logon session. This separation is done to ensure that each in a multi-user scenario has access to all available Windows drive letters (Otherwise this would be limited to 26 drive letters, shared across all users). Bookmarks are mounted in your regular and elevated user session only - there is no way for other logged-in users or non-interactive services to access your drive. There are no persistent mounts created for anyone to use and cannot work across user sessions - mounts for user A are not visible nor accessible by user B even on the same machine.
Windwos service has no access to a mounted drive
Please make sure you have not checked Run whether user is logged on or not on the scheduled task configuration.
A Windows service has no access to a mounted drive
See Windows sessions above. Services do not have access to logged-in user drives.
Mountain Duck Tooltip persists on screen
You can close that overlay by holding your mouse cursor for about 3 seconds on the Mountain Duck icon within the Tray area.
Interoperability
Hosting Service Providers
A list of known providers that fail to work with Mountain Duck due to interoperability issues.
OwnCube: Their deployment does not work and we discourage this product.
Bitnami ownCloud: PHP-FPM is enabled by default in virtual machines and Ubuntu-based cloud images but must be disabled for uploads to complete. Refer to How to disable PHP-FPM and 0 byte files on WebDAV server.
Third party software
Kaspersky Internet Security
Make sure to uninstall Kaspersky Internet Security with its kernel extensions causing kernel panics prior to mounting a volume.
Eset Cyber Security Pro
Make sure not connections on the loopback interface are blocked.
Bitdefender
Be aware that Bitdefender may interfere with connections.
Sophos Endpoint Protection
May interfere with installation.
Backups
Time Machine
Backups to Time Machine do not work with volumes mounted from Mountain Duck. Time Machine requires disks mounted using Apple File Protocol (AFP). See Backup disks you can use with Time Machine.
Windows Backup
Volumes mounted with Mountain Duck cannot be used by Windows Backup. It can only save backups on destinations that are located within your local system or within your local network.
Bug Reports and Feature Requests
To get help with bugs, feature requests, or other issues please refer to the support page.