In case you haven’t realized, the user and pass in the docker compose are for setting the user/pass that you will enter on windows to access the share. It doesn’t have to be the same as the Linux server user account - though mine is the same because it’s easier to remember.

This very community seems to be the largest by far - around 45k followers if I’m seeing it correctly. It feels a lot more active than the average Lemmy community as well.

These memes are giving me life pls don’t stop

Hmm, well it doesn’t seem to be any problem with the docker compose then as best as I can tell. I picked a random ext4 flash drive and replicated your setup with the UID and GID set and it seems to work fine:

# /etc/fstab
/dev/sda1       /home/<me>/mount/ext_hdd_01  ext4    defaults 0 2

~/mount % ls -an
total 12
drwxr-xr-x  3 1000 1000 4096 Mar 27 16:22 .
drwx------ 86 1000 1000 4096 Mar 27 16:31 ..
drwxrwxrwx  3    0    0 4096 Mar 27 16:26 ext_hdd_01

~/mount/ext_hdd_01 % ls -an
total 6521728
drwxrwxrwx 3    0    0       4096 Mar 27 16:26 .
drwxr-xr-x 3 1000 1000       4096 Mar 27 16:22 ..
-rw-r--r-- 1 1000 1000 6678214224 May  5  2024 PXL_20240504_233345242.mp4
drwxrwxrwx 2    0    0      16384 May  5  2024 lost+found
-rwxr--r-- 1 1000 1000          5 Mar 27 16:27 test.txt

# ~/samba/docker-compose.yml
services:
  samba:
    image: dockurr/samba
    container_name: samba
    environment:
      NAME: "Data"
      USER: "user"
      PASS: "pass"
      UID: "1000"
      GID: "1000"
    ports:
      - 445:445
    volumes:
      - /home/<me>/mount:/storage
    restart: always

I was able to play the PXL.mp4 video from my desktop and write back the test.txt file

Have you checked the logs with docker logs -f samba to see if there’s anything there?

Also you could try to access the HD from within the container, using docker exec -it samba bash and then cd into /storage and see what happens.

I would suggest adding “UID” and “GID” environment variables to the container, and set them to the numeric values for user and group numbers that show in place of your name when you use “ls -an” inside of the “mount” folder (they will probably be the same number).

For example, if inside your mount folder you see:

ls -an
total 12
drwx------ 2 1001 1001 4096 Mar 27 13:54 .
drwxr-xr-x 3 1000 1000 4096 Mar 27 13:51 ..
-rwx------ 1 1001 1001    0 Mar 27 13:54 hello.txt
-rwx------ 1 1001 1001    4 Mar 27 13:54 test.txt

Then set UID: 1001 and GID: 1001

I get the same error as you when I copy your docker-compose and try to access a folder owned by my user. When I add the UID and GID of my user id to the docker-compose (1001 for me), the error goes away.

What did you set UID and GID to and what is the output of “ls -an” when run inside of the shared directory? You can remove the file names for privacy. I just tested the docker container and it seems to work between my Linux laptop and my windows 11 desktop using this docker compose:

services:
  samba:
    image: dockurr/samba
    container_name: samba
    environment:
      NAME: "Data"
      USER: "samba"
      PASS: "secret"
      UID: "1000"
      GID: "1000"
    ports:
      - 445:445
    volumes:
      - ./samba:/storage
    restart: always

The files in my shared folder are owned by UID/GID 1000/1000 which is why I put those as my UID/GID, and when I logged in from Windows I entered samba and secret as the password and I was able to access and modify the files in the shared folder.

Have you done the steps under “How do I modify the default credentials?” and “How do I modify the permissions?” from the readme?

I think this is the tool you are looking for: https://github.com/luigi311/JellyPlex-Watched

I haven’t used it myself but I plan on it eventually when I do make the switch.

On one hand, it looks like this only applies to streaming from a remote server where neither the server owner or the user has Plex pass, so lifetime holders or committed server operators with a subscription can continue to provide access to all our non paying friends. It isn’t explicit whether non-paying users people who port forward / do reverse proxying themselves are affected but it sounds like they are, which is utter BS since direct connections hardly cost Plex anything.

It is however nice that they’re trading this for getting rid of the mobile unlock BS - it was always awkward explaining to friends that they could watch anywhere except on their phone unless they paid $5.

On the other hand, one notable side effect is that all non-lan streaming will now be associated with a paying server owner or a paying user, which makes it impossible to use Plex to share pirated media without a user on either end giving up PII / payment information. I have a gut feeling that this is an extension of the previous piracy crackdown on OVH(?) hosted servers meant to ensure they have the identity of all users who may be engaged in selling access.

Overall, yeah another reason to move to JF. I paid for lifetime more than a decade ago so I’m going to keep using Plex until my non-paying friends start to have issues, but I really hope this pushes more investment into JF apps. I really need a good android TV app that supports server transcoding (IIUC findroid’s beta TV builds are direct stream only).