Cyberduck Mountain Duck CLI

Cyberduck Help / Howto / Mountain Duck / Known Issues

Known Issues

Finder.app will write .DS_Store files to the remote volume

You can workaround this with setting defaults write com.apple.desktopservices DSDontWriteNetworkStores -string true in a Terminal.app window and restart Finder.app using  → Force Quit… → Finder → Relaunch.~

As of version 2.1, .DS_Store files are only saved in a temporary location and not stored on the mounted remote volume.

Finder.app does not show files prefixed with . on remote volumes

You can workaround this with 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.

Performance issues in Finder.app rendering preview

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

Saving a file in TextEdit.app 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.. As of version 2.1, .DS_Store files are only saved in a temporary location and not stored on the mounted remote volume.

Writing files to S3 compatible third party service provider may fail

The S3 interoperable service must support multipart uploads.

In Finder.app, 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 Finder.app is named Untitled Folder the operation fails. As a workaround, create a new bucket with mkdir in Terminal.app. As of version 2.2 the new bucket is created only after renaming in Finder. Make sure to choose a filename with no shitespace.

In Finder.app, 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. As of version 2.2 the new bucket is created only after renaming in Finder. Make sure to choose a filename with no shitespace.

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 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.

Changes from server not immediately visible

The directory listing in Finder.app 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 Finder.app

The Spotlight indexer does not work on remote volumes.

0 byte files on WebDAV server

If you are running an Apache configuration make sure to disable fastcgi and php-fpm. Refer to our best practice for Nextcloud and ownCloud installations.

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>.~

As of version 2.1, extended attributes are only saved in a temporary location and not stored on the mounted remote volume.

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 Terminal.app 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.

Warning when copying or moving files from network drive

Depending on your trusted sites settings you might see a warning dialog with the message These files might be harmful to your computer when trying to copy or move files and folders from a mounted network drive to your local computer. To make Windows trust your remote storage you need to add the hostname of your mount to your Internet Options. Please refer to https://superuser.com/a/149057 for more details. As of version 2.1 this is no more an issue.

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": false

Sharing a mounted drive in local network

With the implemented functionalities it isn't possible to share a mounted drive within the local network. You can workaround it by creating a symlink to the drive.

  • In CMD: mklink
  • In PowerShell: New-Item -Type SymbolicLink

You are now able to share the symlinked drive to the network by sharing the directory.

Cache uses a lot of disk space on the system drive (Windows)

Mountain Duck 3 or later required. The cache directory which is usually located in %LocalAppData%\Cyberduck\Cache can grow to a significant size. To change the writing location of the offline Cache you have to follow these steps:

  • Quit Mountain Duck.
  • Create the directory which should be the new writing target for the Cache.
    • In CMD: mkdir "<target Drive Letter>:\Mountain Duck\Cache"
    • In PowerShell: new-item -type directory -path "<target Drive Letter>:\Mountain Duck" -name Cache
  • Remove the original Cache directory in %LocalAppData%\Cyberduck.
  • Create a link between the old location and the new location.
    • In elevated CMD: mklink "%LocalAppData%\Cyberduck\Cache" "<target Drive Letter>:\Mountain Duck\Cache"
    • In elevated PowerShell: new-item -type symboliclink -target "<target Drive Letter>:\Mountain Duck\Cache" -path "$env:LocalAppData\Cyberduck\Cache"

Enable application icon in Dock (macOS)

Mountain Duck 2.7.0 or later required. 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

Interoperability

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

Kaspersky Internet Security

Make sure to uninstall Kaspersky Internet Security with its kernel extensions causing kernel panics prior mounting a volume.

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.

Defaults on Windows

Windows does not provide a shared way of setting defaults per app. Mountain Duck however implements a way of setting defaults in a similar way as mac OS does.

To get the defaults value for a known name do following steps:

  • Win+R
  • "Mountain Duck" -Dproperty.name

Example: "Mountain Duck" -Dapplication.name.

You may also type "Mountain Duck" -Dapplication.name directly into the start menu.

To set a defaults value for a known name do following steps:

  • Win+R
  • "Mountain Duck" -Dproperty.name=value

Example: "Mountain Duck" -Dbookmark.sort=nickname.

You may also type "Mountain Duck" -Dbookmark.sort=nickname directly into the start menu.

Bug Reports

Please open a ticket from https://mountainduck.io/help/.

Provide logging output

Windows

Choose Preferences → Connection → Log → Show and attach the selected file AppData\Roaming\Cyberduck\mountainduck.log.

Mac

Choose Preferences → Connection → Log → Show in Finder and attach the selected file system.log.

Last modified 9 days ago Last modified on Dec 7, 2018 3:03:45 PM
swiss made software