Not able to mount a VC-container from a NAS: Permission denied.... VeraCrypt::File::Open:276

[Aqmos]

I have an encrypted container on my NAS, which I can mount without problems using Windows to access the data therein. However, this doesn't work when using Linux. Here I get the error message: "Permission denied.... VeraCrypt::File::Open:276". I did some reading already and it seems that "it was caused by the fact that the permissions of the shared files only allow the current Ubuntu user, not even root. But VeraCrypt launched the mount process as root to be able to create mount points and that's why it can't access the file." (https://github.com/veracrypt/VeraCrypt/issues/23; from 2015, but still unsolved...).

Expected behavior

Mount a veracrypt file on a NAS using Linux. On Windows, this works without problems

Observed behavior

When opening the file (which I can obviously see in e.g. Dolphin, Veracrpyt asks for: "Password for /run/unser/1000/gvfs/smb-share:server=nasXXX.local,share=YYY.vc" Some seconds after entering the password, the error message "VeraCrypt::File::Open:276" appears. After copying the NAS-container on my local computer, I can open it without problems using Linux.

Steps to reproduce

1. Create a veracrypt-file (*.vc) on the NAS (or locally and then copy it to the NAS)
2. Try to open the file with VeraCrypt using Linux
3. Enter the password
4. Receive the error message...

Screenshots

Your Environment

**VeraCrypt version: 1.25.9

Operating system and version: Ubuntu 22.04.3 LTS, 64-bit, GNOME-Version 42.9; Window-mgr: Wayland

System type: 64-bit

[Plarixtu]

I have the same issue, but my error message has the number 278 and reads "Permission denied.... VeraCrypt::File::Open:278"

[Unixware]

in my case , VeraCrypt 1.26.7 (fedora 39) shows "Permission denied.." with error 287 VeraCrypt::File::Open:287 (trying to mount from NAS, via NFS )

[r3st0r3]

I had the same problem (error 287) with a veracrypt container hosted on a FritzBox attached USB-Drive. In my case this was not a problem of veracrypt. I tried to open the container with zulucrypt-gui also which gave me a message like "not supported filesystem/raid" when trying to open the container. The problem in my case was an inode/stale filehandle problem that could be fixed by adding "noserverino" to the mount options of the smb-volume hosting the veracrypt container.

For reference: https://unix.stackexchange.com/questions/606406/linux-smb-cifs-stale-cp-cannot-open-file-jpg-for-reading-stale-file-handle