So, i have a NextCloud instance running, with the data directory binded to a folder on my storage. Now, when ik want to list or edit the contents of this folder directly from Nautilus or the terminal, I get a permission denied message. Obviously i do not have sufficent rights. How do i give myself permissions to at least view the contents of the folder? Maybe this is basis linux stuff, I have just not touched this before, and I don’t want to modify this folder or break my NextCloud ;)

4 points

Generally, in my experience, modifying the backing storage for a nextcloud instance is more of a PITA than its worth. I would just mount the webDAV in your file manager. This way the nextcloud db stays in sync with the backing storage.

If you are going to be making direct modifications to the backing storage, check this form post on modifying the nextcloud config to have it look for changes on the filesystem.

As for the permission side of things, run ls -lh in the folder that you want to make changes and see what the user:group is for ownership of the existing files and make sure your new files match. Chmod and chown will be your friends here and chmod has a --reference option that let’s you mirror permissions from an existing file, a real time saver.

Hopefully this helps!

permalink
report
reply
1 point

I hadn’t thought of the database issue, thanks! I am afraid though that changing the ownership of the folder might break things though? Love the --reference option by the way

permalink
report
parent
reply
1 point

I would cd into the user folder that you want to add / remove files from and see what the ownership is to begin with and simply replicate ownership to match what’s already there.

permalink
report
parent
reply
2 points

I went with the suggested mount as webdav, and this works out fine for me, thanks

permalink
report
parent
reply
3 points

Easiest way would be to use the Nextcloud desktop app which will mount your Nextcloud and present them inside nautilus for you to do as you wish.

permalink
report
reply
1 point

That may well be a better idea, thanks. But one of the things i would like to do, besides view the contents of the folder, is rsync the directory to another storage, which brings up the permissions issue again

permalink
report
parent
reply
2 points
*

Nextcloud has the file system available via WebDAV. Mount the WebDAV to a local mount and go from there perhaps?

permalink
report
parent
reply
2 points

This is indeed what i settled for now, thanks

permalink
report
parent
reply
1 point

I’m guessing you’re talking about the client, right? The data folder on the server shouldn’t be touched or modified, except by Nextcloud.

Check who owns the folder. I’ll assume the folder is at ~/Nextcloud, but if it’s not, just substitute in the path to the Nextcloud folder.

You can check who owns the folder using ls:

ls -la ~/Nextcloud

This should give you something like:

drwx------ 10 user group    4096 2024-03-04 00:00 Nextcloud

Where the word “user” is in the above example should be the name of the owner of the directory. Where the word “group” is should be the group.

If either is root, check to make sure the Nextcloud client is not running as root (using sudo or otherwise).

Otherwise, give yourself ownership of the directory:

sudo chown username:username -R ~/Nextcloud

Replace username with your username.

permalink
report
reply
1 point

Thanks for the explanation. Would that break nextcloud if i changed the owner of the folder?

permalink
report
parent
reply
1 point
*

The data is all stored server-side. The worst that could happen is the sync connection stops working and you need to redownload the files. Nothing gets deleted by these commands. They will still be on your disk and accessible by you.

If this breaks Nextcloud, it indicates something’s wrong with your installation.

permalink
report
parent
reply
1 point

Thanks, I went with the suggested webdav route, this is fine for now.

permalink
report
parent
reply

Selfhosted

!selfhosted@lemmy.world

Create post

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.

Rules:

  1. Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

Community stats

  • 5.1K

    Monthly active users

  • 3.6K

    Posts

  • 81K

    Comments