My NextCloud provider recommended Cryptomator for storing encrypted files in the cloud.
The encryption function of NextCloud itself is said to still have too many bugs.
I use Cryptomator on Windows 1.14.2 (msi-5384) in combination with my provider’s NextCloud on the one hand and the MagentaCloud on the other.
When I try to create a subdirectory next to an existing one, I get a strange ‘item not found’ error message with MagentaCloud. The same attempt with my provider’s NextCloud works as expected: the new subdirectory can be created.
I found other posts here related to MagentaCloud that seem to describe similar issues.
Could it be that MagentaCloud is rather unsuitable for Cryptomator?
In response to your question, I also tried to connect my MagentaCloud using the original Nextcloud Desktop Client 3.15.3. That worked as well. I knew that MagentaCloud is also based on NextCloud, but I would not have thought of that on my own.
Today, the problem described above did not occur with either variant. Maybe it was just a temporary MagentaCloud problem.
That was quickly done… I don’t think I’ll be spending much more time with MagentaCLOUD.
I now wanted to delete my test data from the vault in my MagentaCLOUD so that I could start with productive data. Even deleting the small amount of test data didn’t work properly for either variant.
Not even with the MagentaCLOUD Desktop Client Version 3.6.7 on my second computer.
I still have a question: If I delete a subdirectory in a vault, will the corresponding encrypted subdirectory in the cloud also be deleted or will it remain as an empty directory? I ask because there are still so many subdirectories in the MagentaCloud, although only one subdirectory with another subdirectory remains in the vault, which cannot be deleted.
,