Cyberduck Mountain Duck CLI

Version 8 (modified by dkocher, on Mar 10, 2017 at 9:11:51 PM) (diff)

--inplace for rsync

Cyberduck Help / Howto / Mountain Duck / Known Issues

Known Issues will write .DS_Store files to the remote volume

You can workaround this with setting defaults write DSDontWriteNetworkStores -string true in a window and restart using  → Force Quit… → Finder → Relaunch. does not show files prefixed with . on remote volumes

You can workaround this with setting defaults write AppleShowAllFiles YES in a window and restart 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

Performance issues in rendering preview

We suggest to disable the option View → Show View Options → Show Icon Preview (⌘-J) in and choose Use as Defaults.

Saving a file in will attempt to create a folder /Temporary Items on the remote volume. On some servers this may fail due to a permission failure or because the name of the folder is not allowed as in S3.

You will get the error message Bucket name is not DNS compatible. Please contact your web hosting service provider for assistance..

Writing files to S3 compatible third party service provider may fail

The S3 interoperable service must support multipart uploads.

In, creating a new top level folder in S3 fails with Interoperability failure. Bucket name is not DNS compatible. Please contact your web hosting service provider for assistance.

A bucket name in S3 cannot have whitespace in the filename. Because a new folder created with is named Untitled Folder the operation fails. As a workaround, create a new bucket with mkdir in

In, creating a new top level folder in OpenStack Swift will not allow to rename it from untitled folder

Because OpenStack Swift does not allow to rename containers this operation will fail.

Cannot choose the region for S3 bucket when creating a new top level folder

Creating a top level folder in S3 or OpenStack Swift will default to the default location for new buckets (us-east-1 for S3) or containers.

Multiple OpenStack Swift containers in different regions with the same name

Browsing containers will be erratic. As a workaround, browse a region by using a connection profile limited to a single region as with Rackspace Cloudfiles region profiles.

Mounted volumes do not appear on the Desktop

Navigate to volumes using ⌘⇧-C in a 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 sidebar in Favorites.

Changes from server not immediately visible

The directory listing in or File Explorer may become out of date when another applications is adding, removing or modifying files on the server. You can force File Explorer to refresh the directory listing with F5. On the Mac, choose Reload in Finder from the bookmark menu item or Reload from the Finder Extension menu.

Search in

The Spotlight indexer does not work on remote volumes.

Failure saving documents from Microsoft Word & Excel

Make sure to update your Mountain Duck installation to version 1.5.

0 byte files on WebDAV server

If you are running an Apache configuration make sure to disable fastcgi and php-fpm. Refer to Troubleshooting WebDAV in the ownCloud manual and 0 byte files.

Additional ._* files saved on remote volume

The ._* files contain metadata about the file some application write in addition to the file content. On macOS, this metadata can be stored alongside the file on the filesystem, but on remote volumes with no metadata support an auxiliary file is created to contain this information. You can delete metadata on files using xattr -d <filename>.

File permissions reset when saving file (SFTP)

Mountain Duck will forward all permission changes done by Finder or the editing application to the SFTP server. There is a hidden preference to disable the writing of permissions. On macOS, enter in a window

defaults write io.mountainduck fs.setattr.chmod false

to disable. Make sure to quit Mountain Duck before making the change and then re-open the application.

File owner reset when saving file (SFTP)

Some editors save files using an Atomic Save feature that writes changes to a file to a temporary file later replacing the edited file by renaming the temporary file to the name of the edited file. This works well on local filesystems, where there is support to retain the owner of the file that is different from the editing user using a special function call. This does not work for volumes mounted with Mountain Duck and the file owner will be reset to the default owner for new files created on the server by the logged in user. As a workaround, try to find a setting for the editor to disable the Atomic Save feature.

File Locks with vsftpd

Set the property lock_upload_files=NO in vsftpd_conf.

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.


We maintain a list of known providers that fail to work with Mountain Duck due to interoperability issues.

Bug Reports

Please open a ticket from

Provide logging output


Attach the file C:\Users\[YOURUSER]\AppData\Roaming\Cyberduck\mountainduck.log.


Open, filter for “Mountain Duck” in the upper right search field with system.log selected in the left pane. Then choose File → Save Copy As… to save the log file and attach it to your email reply. 

Attachments (2)

Download all attachments as: .zip