Hi Picco,
I am using Cryptomator features with QNAP NAS. At this point the concept does not change, the brand should have little influence. Once you have enabled the services on the NAS to be able to access via Windows or MacOS, you should see a local folder in your pc.
Open your Cryptomator application and select/choose the path of your NAS folder. At this point, is so easy because you need to create a strong password and thats it.
If you do NOT see the NAS folder it is because initially cryptomator may have problems detecting an existing “network” folder. No problem.
Log out and access the NAS directly from the Cryptomator application.
Hello 7k518xmp,
thank you very much for your very quick reply.
So far I understand … but let me ask some further questions please:
If I want to access the encrypted container at the NAS later:
Do I have to mount the share (of the NAS) first or is it possible to directly mount the container instead?
In case I want to access the container with the iOS/ipadOS app, the only way seems to be using WebDAV … so I think I have to activate the WebDAV Server on my NAS, too. - right?
I didn’t use WebDAV in my life, but I will try to support you as much as possible with my knowledge. Consider that I’m an Apple user too (iPhone and MacOS).
If it will be necessary, I could try to test with my NAS.
Do I have to mount the share (of the NAS) first or is it possible to directly mount the container instead?
First of all you should decide where you need to access your data, for example if you would like to access from outside your network, you need a VPN server. (Or limit the access to your data only inside your network)
Decided what I described above, you can choose to expose a shared folder (NFS = Windows ; AFP/SMB = MacOS) or expose Cryptomator folder/container with WebDAV (I don’t know how this should be implement, but maybe I can try to do).
In case I want to access the container with the iOS/ipadOS app, the only way seems to be using WebDAV … so I think I have to activate the WebDAV Server on my NAS, too. - right?
If you have the possibility to enable WebDAV Server and expose your Cryptomator folder/container, yes you could try to do.
Another possibility is that the Synology application could create a (shared) folder between the local device (iPhone or iPad) and the NAS itself. In this case, by entering the local path (after accessing the NAS from the application), you may be able to access the Cryptomator folder/container.
Please consider seriously the VPN server, because it could be dangerous to expose NAS and (WebDAV) server on the internet…
I hope I was helpful, for further support you can continue with the threat of this topic. It will be a pleasure to help you.
All access to the NAS only takes place in the local network, no access from the outside (Internet) is configured or planned.
Regarding the first question“Do I have to mount the share (of the NAS) first or is it possible to directly mount the container instead?” :
I have tried the following, which seems to work:
I mount the share using the Finder.
Go to > Connect to Server > smb://name_of_my_synology/name_of_the_share
then I open Cryptomator and open the desired vault.
The vault has the path: /Volumes/name_of_the_share/name_of_the_cryptomator_container
… this seems to work, but I am not sure if this is the right way. - What do you think?
My question now was whether, instead of mounting the share via the Finder, I can simply mount the cryptomator_container created in it directly with:
Finder > Go to > Connect to Server > smb://name_of_my_synology/name_of_the_share/name_of_the_cryptomator_container
…and then open it in the next step with the Cryptomator application
Regarding my second question::
You wrote "
Do you think the WebDAV server has any advantages/disadvantages compared to your second suggestion? (once again: everything should only take place in the local network, without access from outside/from the internet)
…hmmmhhh … but how can I access the (shared) folder with the application on my mobile device?
I think the only way is WebDAV?
Hi Haenschen,
I’m sorry for not being very helpful. My knowledge is very limited.
Maybe you can try replacing the part of the path “asthcloud2021” with the IP address of your NAS …
Another thing that comes to mind - sorry, I have no idea about Linux - I think I once read something that under Linux, instead of the slash “/”, a backslash “\” is used … maybe that helps …
Keep your fingers crossed that you find a solution here !!!
I’m very pleased to hear that your problem has now been solved … Sometimes the solution is so simple … but when you’re still facing the problem you just don’t see it!
My joy was a bit premature, unfortunately. The problem recurred after I restarted my computer. I’m running Linux Mint and found a recommendation to use davfs2–now struggling with this with no light at the end of the tunnel…
If you’re having persistent problems with SMB via the operating system there is an alternative way to connect to your storage server that might work better for you in your specific environment.
There is an open source cloud mounting program available for Linux called rclone.
With that software you can mount your storage server either over SFTP or SMB it supports both. Once you mount the remote it will appear as a folder in your home folder. Then in cryptomator you pointed to the directory you created in your home folder for the nas server.
You sure when doing the mount that you enable read write caching with this flag:
–vfs-cache-mode full.
Get the software directly from their website rather than an outdated version in your repo. They have a script on the download page that does the download and install.
There is a nice gui app that makes it easier. Its called rcloneview.
You can put the Mount command in a shell script and run it when the computer boots using the startup applications program.
If you run into any trouble mounting your server to a folder let me know and I will assist.
This is how I run cryptomator to access vaults located at a variety of cloud servers.
Hi Leo,
My wife and I have been using a Cryptomator vault on our Synology NAS for years, via a network share. I read in a different thread here that Cryptomator can access only a local vault. Tobi’s approach (see above) using smb or ftp worked for me, but resulted in network connections that Cryptomator was unable to access. It worked also with rclone view (your advice), but still another network connection! And none of them survived a reboot.
So, if you could kindly provide a sample script for rclone, I’d appreciate your help. I worked with Unix some 20 years ago. Now, I want to shift from Win10, in order to keep my potent, but not Win11-capable hardware.
If no one else is interested in this, please let’s communicate privately; German welcome.
