Jellyfin through a traefik proxy, with a WAF as middleware and brute force login protected by fail2ban

If you’re using a government run DNS, why not use the CIRA ones instead? https://www.cira.ca/en/canadian-shield/

To add to this….ive added a layer of protection against accidental deletion and dumb fingering by making each year of my photos archive into a separate zfs dataset. Then each year I set each dataset to read-only and create a new one.

Manual, but effective enough. I also have automatic snapshots against dumb fingering, but this helps against ones I don’t notice before the snapshots expire.

I did (am doing) something very similar. I definitely have issues with my indexing, but I’m just ordering it manually by year/date for now.

I’m doing a little extra for parity though. I’m using 50-100gb discs for the data, and using 25gb discs as a full parity disc via dvdisaster for each disc I burn. Hopefully that reduces the risk of the parity data also being unreadable, and gives MORE parity data without eating into my actual data discs. It’s hard enough to break up the archives into 100gb chunks as is.

Need to look into bacula as suggested by another poster.

Different devices. iOS, android, AppleTV. Most of it is likely Apple’s fault for the limited options in the ecosystem tho.

It’s not a transcoding power issue. It’s a UI consistency and usability issue. With every device having a slightly different UI, with some apps having issues if playing back natively and some needing transcoding, the experience is inconsistent and frankly doesn’t pass the “wife acceptance factor” test, or the “let your friends use it without needing to handhold them through regular troubleshooting for their particular device” test.

I still don’t use Plex and exclusively use Jellyfin, but it’s still a hard sell to non technical users. Plex has much more polish.

It is……if you use a computer. Their AppleTV app still looks like some random coder’s pet project with random playback issues.

Yes. Your machines would have one main IP address, and one virtual IP address that would be assigned to either machine depending on the priority or health check status. That IP can be on the same physical interface, or a separate one. It’s very flexible, pretty standard config for high availability setups.

Keepalived to set up a floating IP between two proxy hosts. The VIP is where the traffic points to, the two hosts act as active/passive HA.

I think the universal consensus is that outside of a very specific use case: multiple VDI desktops that share the same image, ZFS dedupe is completely useless at best and will destroy your dataset at worst by causing to be unmountable on any system that has less RAM than needed. In every other use case, the savings are not worth the trouble.

Even in the VDI use case, unless you have MANY copies of said disk images(like 5+ copies of each), it’s still not worth the increase in system resources needed to use ZFS dedupe.

It’s one of those “oooh shiny” nice features that everyone wants to use, but will regret it nearly every time.

“Both sides”

“Vote third party!”

Wtf seriously this isn’t the same thing remotely but the arguments used are.