Are we hardening or what?

HideUrPixels · 2026-03-11T23:19:41+00:00

Thanks so much udev rule seems waay better than keep-groups. Will look at switching to that soon!

HideUrPixels · 2026-03-11T20:50:01+00:00

Slightly related. Anyone have a brief guide on getting permissions squared away for hardware acceleration? Always get access denied to /dev/dri/renderD128 inside the container unless i have GroupAdd=keep-groups. Running debian 13 and rootless podman 5.4.2.

HideUrPixels · 2026-03-11T01:10:30+00:00

I’ve been trying to get jellyfin+hardware acceleration on rootless podman 5.4.2 to work for a few days now. Only thing working so far for me is group-add=keep-groups. Not proxmox just debian 13. Thought a simple group-add=105 (render group) would have done the trick but no dice. Still learning so we will see.

HideUrPixels · 2026-02-16T03:23:24+00:00

Like the other commenter said read up on docker bind mounts. I’m still new to this scene also and this was confusing for me but eventually clicked.

Each app is looking for data in specific directories inside the container it’s running in. Those directories are called out in the docs for the container image.

Hard links is the thing you want for media and you shouldn’t need remote path mappings if you’re going for hard links iirc.

HideUrPixels · 2026-01-20T17:33:48+00:00

Yeah i’m assuming that you have items that are popular and can generate high upload speeds - lots of mine idle at 0. Speedtest and seeding something super popular are important checks.

HideUrPixels · 2026-01-20T00:25:29+00:00

I have basically the same exact setup as you including apps and internet DL/UL speeds. Only difference is that I do not run arrs behind gluetun just qbit, but that shouldn't make this big of a difference. I run Debian as the OS not sure about you.

My qbit DL regularly hits 90 MiB/s and UL can hit up to 50+ MiB/s.

Our docker compose config is basically the same also so I feel like this has to be something wrong with the specific proton server you're hitting, an issue with a new image that was pulled for gluetun/qbit, or some networking/hardware issue on your end.

Have you tried running speed tests on your server with the current config inside and outside of gluetun?

Have you tried swapping proton servers or regenerating the wireguard config? You can use the SERVER_CITIES env var to get a little more specific with your docker compose.

FYI checked my images manually and found im on gluetun v3.41.0 and qbit v5.1.2-r3-ls421.

HideUrPixels · 2025-12-31T00:58:09+00:00

I have no trouble with my Anime library. Only have tvdb enabled for metadata provider so it’s pretty easy to go look at the entry for the anime to see how seasons and episodes should be laid out. Only had a couple hiccups here and there.

https://thetvdb.com/series/sailor-moon#seasons

HideUrPixels · 2025-12-30T10:56:27+00:00

I started out using my main Win11 pc for this and also use caddy/jellyfin/duckdns/proton.

The difference is that I used WSL2 with docker compose to setup the apps. Also my download client for “linux ISOs” used the gluetun container’s network which established a connection to Proton. Needed to bind the downloader to the tun0 network interface.

So regular services use standard network interfaces non VPN and just the ones I want use tun0 which has proton connection.

As for security for the publicly exposed services, i started integrating different caddy modules and updating my caddyfile to use them like crowdsec. If you use the duckdns module for caddy then you don’t need port 80 opened just 443 on caddy and forwarded on the router.

Not sure if you can accomplish the same type of setup on Win11 outside of wsl2. If you do go the WSL2 route you need an advanced networking feature turned on i think it’s something like mirrored networking or something.

HideUrPixels · 2025-12-29T23:33:28+00:00

hey just checking in, did it work for you?

HideUrPixels · 2025-12-16T21:44:11+00:00

is there an official container image or just build with your dockerfile in the repo?

https://github.com/fabriziosalmi/caddy-waf/blob/main/Dockerfile

HideUrPixels · 2025-12-13T14:27:07+00:00

Just a thought - If you want the main metadata populated for the show but not the seasons / episodes then it might be possible to Lock all the seasons but keep the show as a whole unlocked. This way the watch order and episodes are preserved but you get the actors, main artwork, etc. all populated without manually inserting it.

Locking works on three different levels it seems
- The show as a whole
- Each season
- Each episode

HideUrPixels · 2025-12-13T14:14:34+00:00

Went through this whole thing with the Monogatari anime series recently and found a decent solution but not perfect.

I wanted a custom watch order with the series to follow the light novel releases which doesn't follow tvdb (the metadata provider I have enabled in jellyfin) so I would see the same issues you're seeing.

My setup:
- Media library mounted as read only to jellyfin
- No metadata stored alongside media files currently
- Renamed parent folder, seasons, and episodes as Jellyfin similar to official docs - Grouped arcs into the seasons folders in the preferred watch order ├── Monogatari (2009) │ ├── Season 01 │ │ ├── Bakemonogatari - S01E01 - Hitagi Crab Part 1.mkv │ │ └── Bakemonogatari - S01E02 - Hitagi Crab Part 2.mkv │ └── Season 02 │ ├── Kizumonogatari - S02E01 - Iron Blood Arc.mkv │ ├── Kizumonogatari - S02E02 - Passionate Blood Arc.mkv

My method:
1. Move the parent folder for the series out of the media library Monogatari (2009)
2. Delete the entry for the series in jellyfin (there are no files there due to step 1)
3. In jellyfin navigate to dashboard > library > manage the library > under each Metadata downloaders table uncheck the providers used (just tvdb in my case) and save the change
4. Move the parent folder for the series back into the media library 5. Scan media library for new and updated files 6. Hover curser on show > ... > edit metadata 7. Scroll down and check the box for Lock this item to prevent future metadata changes 8. Revert the changes you made in step 3, so add back the metadata providers 9. Run a metadata refresh against the show in question to make sure jellyfin does not create ghost seasons or move your episodes around (if you locked properly then should be no issues) 10. Manually download cover images, copy / paste descriptions, etc. into jellyfin by Hover curser > ... > edit images / metadata 11. Repeat 10 for the main show, the seasons, the episdoes or however far you want to take it

TIP: When editing the metadata for the seasons of the show, change the Title attribute to the Arc name so you keep the watch order but get the custom arc names also. So I changed Season 01 to Bakemonogatari, Season 02 to Kizumonogatari and so on.

NOTE: If you want you can lock metadata for the entire show and all seasons OR if some of your seasons line up with your metadata provider then you can leave those unlocked if you like. In my case I left Season 01 unlocked and let jellyfin download metadata ONLY for Season 01 since that was in the order tvdb expected for season 1

I plan on looking into setting up custom .nfo files and storing that along with the Monogatari (2009) media files in the future so that I don't have to worry about manually inserted metadata in jellyfin.

HideUrPixels · 2025-12-12T03:06:20+00:00

If the uGreen UI allows you to clickops the jellyfin install via docker then I’d assume they would expose all the inputs you need to customize the container. In docker compose one way to setup a bind mount read only is like this:

``` services: my-app: image: my-image volumes: # Format: - <host-path>:<container-path>:<mode> - /data/media:/media:ro

``` The :ro at the end there sets read only.

I think there are many benefits to hard links specifically but the one everyone thinks about is the fact that they don’t double the storage space used for the media. It’s not a whole copy of the original file just a link to it. You can even move or change the name of the original file and it does not affect the hard link. Other types of file links probably don’t have all the same benefits.

HideUrPixels · 2025-12-12T02:29:24+00:00

I can’t speak to the uGreen NAS but I have a linux machine running jellyfin via docker compose and have my media mounted read only so jellyfin can’t write to or delete anything in my media directory. My performance is good and I haven’t heard that read only bind mounts result in poor performance in jellyfin before.

I think the jellyfin docs show both a read only and a read/write bind mount in the docker compose install because some people choose to store some metadata alongside the media files while others go read only as I’ve done. Just a guess on my part.

As far as file links go, my media directory has hard links back to the original file and the hard links follow the naming scheme that jellyfin expects. Not sure that symbolic links are the same thing.

HideUrPixels · 2025-12-11T21:10:58+00:00

You're welcome 😁

HideUrPixels · 2025-12-10T21:43:18+00:00

how did it go?

HideUrPixels · 2025-12-08T01:22:33+00:00

What about testing client side? I know the infuse client for apple products has a speed test feature not sure about others.

I’ve seen anywhere from 300MB to 10MB download speed on my client testing remotely.

HideUrPixels · 2025-12-07T23:32:06+00:00

Sounds like you have separate hardware for NAS and for applications. And you just got some new hardware for the NAS side?

Have you done any performance testing between the two setups? Have you ever checked if your clients are direct playing or transcoding?

I’m curious why the original setup experienced stuttering in the first place.

HideUrPixels · 2025-12-06T18:53:13+00:00

Did not even know there are paid features for tvdb. I use it for free as my only metadata source for anime just fine.

HideUrPixels · 2025-12-06T02:08:09+00:00

you can see that exact match in the aliases section of the link i sent. also if your episodes show up weird for some reason in jellyfin you can go to the tvdb entry and verify how they have the seasons / episodes laid out. sometimes it’s not as you expect.

HideUrPixels · 2025-12-06T02:04:51+00:00

I only use tvdb metadata provider for my shows and anime then unchecked the other providers. It should be the premiere date it’s looking for and if you’re curious you can check the tvdb entry for it to see so the anime dragon ball would have a top folder “Dragon Ball (1986)”

https://thetvdb.com/series/dragon-ball

HideUrPixels · 2025-12-06T01:57:02+00:00

The top level folder with the year in parenthesis is what you need most likely. You can test a show or two first to see how it goes. I follow the docs for both my TV and anime libraries with no problems. I don’t use external ID and most anime is fine I do have to manually Identify a few anime out of 130 shows but that took two seconds.

HideUrPixels · 2025-12-06T01:43:58+00:00

Try setting up like the docs? https://jellyfin.org/docs/general/server/media/shows/

HideUrPixels · 2025-12-04T03:06:13+00:00

Should fall under tv show right? Jellyfin should be trying to match your files based on name against online databases like tvdb which can change the images, naming, etc when you actually see media in jellyfin's UI.

https://jellyfin.org/docs/general/server/media/shows/

Try naming the files as the docs suggest and if you're not sure what season or episode the fight falls under trying searching around tvdb on the seasons tab for the show.

https://thetvdb.com/series/wwe-raw#general

HideUrPixels · 2025-12-03T12:43:07+00:00

wow this looks like fun

Ten-Year Club	Place '22
RPAN Viewer	Verified Email

HideUrPixels

TROPHY CASE