Unstable and slow if vault is on a FRITZ!Box NAS.

[berndschreiber503]

Please agree to the following

• I have searched existing issues for duplicates
• I agree to follow this project's Code of Conduct

Summary

Unstable and slow if vault is on a FRITZ!Box NAS.

What software is involved?

• Operating System: Monterey 12.4
• Cryptomator: 1.6.10
• FUSE 4.2.5 (But also used WebDAV, same bug)
  logs and screenshot.zip

Volume Type

No response

Steps to Reproduce

Establish a NAS on a FritzBox (external or FritzBox internal).
Make a new Vault.
Use Vault

Expected Behavior

Cryptomator working like on the cloud or HDD.

Actual Behavior

it Does sometimes work as expected, but after a restart of cryptomator it doesnt do it again. Mostly does not work.
It stumbles if Cryptomator is used. A short bust of 64 mb and nothing for 15 seconds. then again. If the copy process is terminated, the partly copied files cannot be erased with finder. (Error code -36).

Reproducibility

Intermittent

Relevant Log Output

see screenshots and logs in attached .zip file.

If needed, please contact me to do further testing. I can also provide remote desktop control access if needed.

Anything else?

Dear Cryptomator Team,

I have a hard drive connected to my FRITZ!Box and used as a Network Attached Storage. I would like to encrypt the files on the NAS with Cryptomator but it seems to be incompatible. While files are transferring fast and without problems to the NAS unencrypted, it stumbles if Cryptomator is used. A short bust of 64 or 8 MiB and nothing for 15 seconds. then again. If the copy process is terminated, the partly copied files cannot be erased with finder. (Error code -36).

Finder copy process cannot be stopped. Locking the with Cryptomator fails. Forecelock also fails.

-tested with different HDDs, USB 3.0 Sticks and the internal FRITZ!Box Memory (4GB)

-tested with WebDAV and FUSE (newest version of macFUSE installed and reinstalled)

-Running on Monterey 12.4 and newest FRITZ!OS

Thanks!

[scwall]

Hello, I have exactly same question, you have a idea for this bug ? Thanks

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.