Hardware: Beelink U59 YunoHost version: 126.96.36.199 (stable)
**I have access to my server : Through SSH & through the webadmin & direct access via keyboard / screen Are you in a special context or did you perform some particular tweaking on your YunoHost instance ? : yes, runing backports package because my GPU is not available with Debian 10, so I upgraded kernel of linux in 5.X Backports and forced it in the grub to launch the GPU pilots.
Description of my issue
My goal is to create a hoster cloud server through nextcloud. I have mounted a NAS in the fstab and have full read and write access to all the folders on the NAS from the computer.
So I subsequently installed Nextcloud, add the NAS to external media, but I cannot create, move, upload, a file. Only read access is allowed to me.
I tried a chmod 777, chown … and nothing helps.
Here is what I get when I try an action :
Mon but est de créer un serveur cloud hoster via nextcloud. J’ai monté un NAS dans le fstab et j’ai bien accès en écriture et en lecture à tous les dossiers présent sur le NAS depuis l’ordinateur.
J’ai donc par la suite installé Nextcloud, ajouter le NAS en media externe, mais il m’est impossible de créer, déplace, televerser, un fichier. Seul l’accès en lecture m’est autorisé.
J’ai essayé un chmod 777, chown … Et rien n’y fait.
Hmm… Most Yunohost users have no permission to use Bash or log in. I think you can circumvent that, by temporarily adding user nextcloud to the SSH-users-group in the Yunohost usergroup configuration. You won’t know its password (and I would not change it), but with some luck you can after that su -u nexctloud after that (or make public key SSH login working, but that is for later).
Ok, yes, of course.
How is the NAS mounted? Maybe setfacl can only be run on the filesystem directly, or not via all network mount protocols. For sure, I think sshfs does not support it, compare getfacl for my Yunohost /home/yunohost.app/nextcloud/data first mounted via sshfs and then when executed directly on the filesystem;
This situation may be the reverse of your situation, so perhaps it is the wrong direction to look in (I mounted Yunohost on my desktop, instead of NAS on Yunohost; the result of ACL on Yunohost is that only part of the mounted Yuno-FS is visibile on the desktop)
Hey! But still: your nextcloud user is probably not allowed to write to /mnt!
I’m having dinner first, maybe this already helps a bit