I’m trying to set up a group so multiple users can share a folder. I created the group and a folder for it but I’m not what paths I should use for both. The result is that the user can see the group folder in the web UI but an error occurs after clicking on it:

“Failed to get directory listing: Unable to get directory contents"

Thanks

To set up the folder, which I called “shared”, I set the home directory for it to /srv/sftpgo/data/shared. For reference, my user home directory is /srv/sftpgo/data/user1. Then to allow user1 to access it, I mount it as a virtual folder. Is this what you did?

permalink
report
reply
1 point

Not quite. I’m trying to setup a group to let all users access the same folder. I created a folder called Family (I think it set its path to /Family. I’m away from the pc so I’ll grab it later). Then I created a group called Family and mounted the folder in it. But I wasn’t sure what paths to use for the group.

permalink
report
parent
reply

Okay I think I might know what you mean? I just tried doing that and got it to work. We can compare what we did. Here’s mine.

I created a shared folder called “Shared”

then I create a group called “All” and mount the “Shared” folder to /shared

I went to a user and add them to group “All”

Examining that user’s files

I can navigate into that shared folder and access everything (I have stuff in there already).

permalink
report
parent
reply
0 points

Ah thanks!! I hadn’t set the group home dir properly. I guess I don’t understand what that’s supposed to represent. I assumed it would include the group name somehow, but I set it to. /srv/sftpgo/data/%username% and it works.

permalink
report
parent
reply
0 points

I created another group and hit the same problem. I had to restart the docker container before it worked. Odd.

permalink
report
parent
reply
1 point

I totally misread this as SMTP2Go and then was very confused by the body of your post 😅

permalink
report
reply
1 point

Haha! When I first learned about SFTPGo it took me a while to not include a “2”!

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.2K

    Monthly active users

  • 3.5K

    Posts

  • 76K

    Comments