If it’s Ubuntu and you’re looking at an NTFS filesystem, have you looked at the permissions you’ve established for the mount? i.e. Is the user that nextcloud runs as (apache?) allowed to view the folder, but are the files set to a different permission level. First off I would suggest that you show us what the file permissions look like in the root of your shared folder…
# ls -laZ
The Z above will include the selinux context just in case that’s enabled, which can have an effect on things as well.
Starting up this thread again as I am not finding answers anywhere else. I have followed the usual tips to “chown” and “chmod”. This is what the file permissions look like when entering the command you suggested.
I read somewhere that it could be a problem that the external storage is located in /media/user/storage and that it is better if it is placed directly in /media/storage. If so, how do I make it more permanently “stick” in /media/ in stead of going back to /media/user/ after a server reboot?
When trying to open the external storage I get a dialogue window telling me:
"External mount error
There was an error with message: Empty response from the server. Do you want to review mount point config in admin settings page?"
I can configure my local external storage in Nextcloud and even get a green check mark. Trying to look in the folder I either got an empty folder or the response “External mount error - there was an error with message: Empty response from the server.”
Solution (maybe wrong but it works):
It seems that the permission I granted www-data only was given for the local drive itself, not for the parent directory. That seems to have caused the problem that www-data lacked permission also to access the local drive. I was able to unmount the drive and mount it in /media/drive, instead of /media/user/drive, then I gave www-data privileges both in /media and /media/drive using these commands: