Hi, thanks. I’ve been testing out NextCloud and it might be a bit too bloated and buggy for me (document editor iffy on mobile and encountering files and folders being falsely locked and thus cannot be interacted with) so I might give sftp a go.
Is there a dockerhub project you would reccomend? I’ve been looking at sftpgo (https://hub.docker.com/r/drakkan/sftpgo) as a option?
To prevent brute force login attempts into my jellyfin service.
Oh I can see how my title could be misunderstood - what I meant is that both jellyfin and fail2ban are running in (separate) docker containers. Not both services crammed.into one.
Thank you. I did see this list before. My jellyfin instance is not exposed to the net atm., but I’m thinking of exposing it in intervals and would like to have fail2ban working when/if I do.
I did the same. Not because I knew, but because I was unsure if permissions would fail if I didn’t.
Do I just enter the container shell and check GID and UID of a random file?
I’m CURSED I tells ya! I’ll look at the logs tomorrow. Good to know that you can get it working. Maybe I’m close then.
Do I need to enter the container bash and change something then? I tried adding UID and GID to the docker compose file, but it still fails. I updated the google docs notes if you want to see my steps.
Thanks for the suggestion. I tried and it still doesn’t work. I updated the google docs notes with my steps if you want to see what I did.
How do I tell? In the docker-compose.yml file I put the user and password for my server user. I thought that was going to make it work?
I did fiddle with it. I tried putting my server user and password in there, but didn’t get it working.
Well, I’m not trying to share from within the docker container. I just want to run the samba service from a container. The share is an external hard drive connected to the server. I want to be able to move files to and from the ext hdd from a windows machine.
I had a similar issue on an HP Elitedesk 800 mini G3. It turned out to be a faulty ram stick. Memtest revealed the issue and after unpligging the defective stick the issue was resolved.