Comment Re:I don't get it (Score 1) 147
Castillo de San Marcos - Built at Sea Level in 1672.
Castillo de San Marcos - Still at Sea Level in 2025.
Castillo de San Marcos - Built at Sea Level in 1672.
Castillo de San Marcos - Still at Sea Level in 2025.
I don't think it directly supports remote streaming
It does, but you'll need to route the incoming traffic through manually. For me, that involves having the router forward traffic on port 443 to the server and configuring a reverse proxy on the server to hand off traffic addressed to jellyfin.$HOME_DOMAIN to the Jellyfin daemon. In my case, Jellyfin is one service among many on a Docker host, with Caddy directing incoming traffic to wherever it needs to go.
It's not automated like Plex, but I've streamed movies and TV shows from across the country without any problems.
I recently switched my service plan (with Cox in Las Vegas) from 500 Mbps with a 1.2-TB (IIRC) monthly limit to 250 Mbps with no limit. After a couple of months of overages that basically doubled my bill, it'll be nice to have predictable billing no matter how much we end up using. 250 Mbps has been fast enough so far.
Plex is available on many more devices. Jellyfin has PC, iOS, Android, AppleTV, AndroidTV, Roku, and LG TVs. But Plex also has PlayStation and Xbox, Samsung TVs, Vizio TVs, and many other smaller streaming boxes.
I used to run Plex. I even paid for a lifetime subscription years ago. I now run Jellyfin; it's been less of a hassle to keep it running and it puts less load on my server. I shut off my Plex container last month after switching my parents' Rokus over to Jellyfin. At home, I switched to Chromecasts (the newer ones that run Android TV) after having run OpenELEC on Raspberry Pi 3s for a while.
Plex also has better remote access support. Just enable it and setup a port forward/firewall rule. Jellyfin? Have fun configuring a VPN on each client to access it.
My Jellyfin instance shares a box with a bunch of other services. Caddy routes traffic on port 443 wherever it needs to go: to Jellyfin, to one of the *arrs, to Nextcloud, GitLab, etc. One rule at the router passes inbound port 443 off to Caddy. No VPN is necessary.
By comparison, there were more than a few instances where Plex's "it just works" networking configuration didn't just work.
Message from Our Sponsor on ttyTV at 13:58 ...