all the time. ie Sudo mount -a = pemrissions denied.
nice to know but, it fails to mount even when i sudo mount -a, well after the network is up.
this made no change.
I do now know actually as this line “just worked” before. as long as the nextcloud service can read and write files to the network share, i’d be happy.
where would that argument go?
also FYI this line works if i set the share to public. i don’t think it’s an unraid things as i have this problem with xubuntu 20.04 LTS at home with a windows server.
ALSO i’m hosting from unraid but, NFS is broken on unraid:
Limetech’s solution is to just not use NFS as it’s old.
so i can’t use NFS, i can’t get SMB to work. i FINALLY got NC setup with LDAP integration.
I see TONS of threads with people having issues with SMB shares with ubuntu and it was WAS supposed to be fix but, either someone finds some small argument that gets it working or the threads just linger with no resolution.
Its not, I use it for my own nextcloud in exactly the way you’re doing. You’ll want to turn hardlinks off in the tunables section but it works fine otherwise.
In your mount -a output I see unc=\IP.ADD.R.ESS
This is not a UNC path though. A unc path would include the hotsname, not IP, of the host machine. Not sure if thats really a clue though.
Admittedly this is not a fix for your specific issue, but if you want to work around it I can point you in another direction. You’ll have to stop your array and change hardlinks to no.
i did try NFS and it technically worked with even though i had an IP instead of a host-name however the command line in ubuntu server was going bonkers with handling exceptions.
i’ll try again.
curious what arguments you put after the IP address under your NFS in unRaid?
the reason i ask is because each guide i look at puts all kinds of different arguments after the IP address for the NFS settings (in unRaid) so i guess i’m not sure what it is or if it would be just an IP address?