[[TOC()]] = [wiki:help/en Cyberduck Help] / [wiki:help/en/howto Howto] / [wiki:help/en/howto/mount 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 [https://mountainduck.io/changelog/ 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.`. === Writing files to S3 compatible third party service provider may fail === The S3 interoperable service must support [http://docs.aws.amazon.com/AmazonS3/latest/dev/mpuoverview.html 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''. === 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. === 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 [https://trac.cyberduck.io/wiki/help/en/howto/profiles connection profile] limited to a single region as with [https://trac.cyberduck.io/wiki/help/en/howto/cloudfiles#Profilesforasingleregion 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 [wiki:help/en/howto/mount#FinderExtensionWindowsFileExplorerExtension 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 [https://doc.owncloud.org/server/8.1/admin_manual/issues/index.html Troubleshooting WebDAV] in the ownCloud manual and [http://sabre.io/dav/0bytes/ 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 `.~~~ As of version [https://mountainduck.io/changelog/ 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 [https://developer.apple.com/legacy/library/documentation/Darwin/Reference/ManPages/man2/exchangedata.2.html 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 [https://mountainduck.io/changelog/ 2.1] this is no more an issue. == Interoperability == We maintain 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. Refer to [https://billing.owncube.com/viewticket.php?tid=688548 Ticket #688548]. * ''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 [https://wiki.bitnami.com/Components/PHP-FPM#How_to_disable_PHP-FPM How to disable PHP-FPM] and [https://trac.cyberduck.io/wiki/help/en/howto/mount#a0bytefilesonWebDAVserver 0 byte files on WebDAV server]. === 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 [https://support.apple.com/en-us/HT202784 Backup disks you can use with Time Machine]. === Windows Elevation === There are known issues with applications running elevated - as Administrator - and Mountain Duck not being run elevated. This leads to mounts not being visible either in Windows Explorer or elevated applications. See following chart as example: {{{ Scenario 1: * Mountain Duck: Not elevated * Windows Explorer: Not elevated, can see Mountain Duck drives * Application: Not elevated, can see Mountain Duck Drives Scenario 2: * Mountain Duck: Elevated * Windows Explorer: Not elevated, cannot see Mountain Duck drives * Application: Not elevated, cannot see Mountain Duck drives Scenario 3: * Mountain Duck: Not Elevated * Windows Explorer: Not Elevated, can see Mountain Duck drives * Application: Elevated, cannot see Mountain Duck drives Scenario 4: * Mountain Duck: Elevated * Windows Explorer: Not Elevated, cannot see Mountain Duck drives * Application: Elevated, can see Mountain Duck drives }}} Following may lead to this behavior: * UAC (User Account Control) is deactivated (Apps are getting highest privilege they request). We recommend turning User Account Control on for increased security * App requires to be run elevated Backup Software may not show Mountain Duck drives as they need to be run elevated due to accessing important system files. To resolve issues with Backup Software using Mountain Duck please Quit Mountain Duck, type "Mountain Duck" into the Start Menu and hit {{Ctrl+Shift+Enter}} to run it elevated - alternatively right click on Mountain Duck and choose "Run as Administrator". == 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`.