- Improve FUSE-T startup rollback and unmount cleanup, and report when service termination cannot be confirmed.
diff --git a/doc/html/en/Troubleshooting.html b/doc/html/en/Troubleshooting.html
index f033a92f..4f86fbc2 100644
--- a/doc/html/en/Troubleshooting.html
+++ b/doc/html/en/Troubleshooting.html
@@ -424,6 +424,26 @@ Locate the IRPStackSize key in the Windows regi
https://support.microsoft.com/kb/285089/ and
https://support.microsoft.com/kb/177078/
+
+Problem:
+
+On Linux, a volume stored on a network share opened in the file manager, or on another file system that your user account mounted with FUSE (for example sshfs or rclone), cannot be mounted: VeraCrypt reports "Permission denied". Or VeraCrypt warns that it opened the volume file with your user account's access rights.
+
+Probable Cause:
+
+Such file systems are mounted by your user account without the allow_other option. Linux then denies access to every other user, including the administrator (root), even though your account can open the files. VeraCrypt mounts volumes with administrator privileges, so VeraCrypt 1.26.29 and earlier versions cannot open such volume files.
+
+Possible Solutions:
+
+-
+Later versions of VeraCrypt open the volume file with your user account's access rights when administrator access is denied, provided that VeraCrypt obtained administrator privileges through sudo or doas, as it does when you enter your password in VeraCrypt. The volume is then served through VeraCrypt's FUSE layer, which is slower than direct mounting by the kernel, and VeraCrypt displays a warning. Keep the share mounted and your session active until you unmount the volume: ejecting the share or logging out while the volume is mounted can cause data loss. If "Permission denied" is still reported, either your account itself cannot open the file, or VeraCrypt was started as root without sudo (for example from a root shell) and cannot determine your user account. In the latter case, start VeraCrypt as your user. Keyfiles stored on such a file system work only when VeraCrypt itself runs as your user, not when it is started with sudo.
+
-
+For regular use of an SMB share, mount it with the kernel CIFS client instead (package cifs-utils), owned by your user account. For example:
+
sudo mount -t cifs //server/share /mnt/share -o username=NAME,uid=$(id -u),gid=$(id -g). Volumes stored on such a mount are mounted directly by the kernel and do not depend on your session.
+ -
+For sshfs, rclone and other FUSE file systems that support it, enable
user_allow_other in /etc/fuse.conf and mount the file system with the option -o allow_root. Administrator privileges can then access it, and VeraCrypt opens the volume file normally. The volume still depends on that file system: keep it mounted until you unmount the volume.
+
+