halcyoncmdr

Pangolin officially says on their site :

Pangolin generally requires minimal resources to run effectively. A basic VPS with 1 vCPU, 2GB RAM, and 8GB SSD is sufficient for most deployments.

If you choose a VPS with only 1GB RAM, you may need to create swap space to avoid memory pressure during installation, updates, or periods of higher traffic.

I’ve got a 1 vCPU, 1GB RAM, 25GB Disk droplet for $6/mo and have no issues for my limited home use. Updates don’t really take a noticeably long time or anything, it takes maybe 45 seconds to fully bring up the docker container again after an update. But it runs just fine.

Similar here. Just a Digital Ocean droplet running Pangolin. Functions basically the same as the cloudflare tunnel it replaced.

Can expose the service directly if needed, or from behind a login page.

If only pangolin supported 0.0.0.0 routing. It’s been requested for months but instead of doing that… They’ve been courting paid enterprise usage.

Jellyfin on the native docker app works.

And if it’s a model without docker capability built in (most of the lower end ones they remove docker support), docker can usually be side loaded fairly easily.

Pretty much.

But… I mean… that’s not the right thing to do for proper security. You would be 100% reliant on user passwords and the devs fixing any security issues like remote code execution or privilege escalation in a timely manner, and you updating after that release comes. Now if Emby is running in a container like docker, or on a dedicated system, you have backups, etc. then even if someone got in there’s not much they could realistically do other than watch your media.

But realistically, you won’t have issues doing it that way in the real world unless you’re already being targeted for some reason.

Emby is based on jf from years ago.

That’s backwards… Jellyfin was forked from Emby in 2018. Both have been developed separately since then, and are still very similar.

Yeah, via an Emby Connect account through their server infrastructure for the initial connection.

Does This Mean My Streaming is Passing Through the Cloud?
No, all connections are direct from your devices to your Emby Server. The sole purpose of the Emby Connect feature is to help your devices locate your Emby Server so that you don’t have to set it up yourself.

I used it in the past, but moved off when I started self-hosting more than Emby. I now have a cheap VPS at Digital Ocean and a Pangolin droplet to handle any web apps that I need to share a remote connection for (like Emby and Jellyseerr), without having to bother with VPN setup. Works like a Cloudflare Tunnel, but without the cloudflare crap.

They’re not wrong. Making the default a proprietary format further entrenches that format even if you’re using a different product, it still helps Microslop.

Switching the default to an PDF instead removed that implicit support while still allowing users the flexibility to use the OOXML format if needed.

There is a third option, the program that Jellyfin was originally forked from back in 2018, Emby.

Sort of the middle child between the two. Nearly identically to Jellyfin for obvious reasons, several third party apps for Jellyfin work with it as well like Jellyseer, it has apps for nearly every device, and easy external connections via their servers like Plex does.

They do however have a premium subscription system like Plex to support things like those servers. It’s not as expensive as Plex, even before the recent rate hike, but it is there and some stuff is locked behind that premium license.

Yeah, let me just walk my normie friends and parents through setting up a VPN on their TV so they can stream their shows.

You can set pangolin to allow access to an entire resource or just certain paths without the front auth, instead relying on the built in auth.

Your random plex/emby/jellyfin server isn’t going to be a huge target and the built in auth is good enough for the limited access your media system should have.

All of my self-hosted systems are on a TrueNAS system and using the built-in app system (basically docker). It notifies me when they’re needing updates, and has a single click update process for everything. I just login weekly to see if the button is yellow, then check on it like 15 minutes later to see if anything failed to update. Yeah they’re all on the same hardware, which is probably bad, but nothing there is strictly necessary, it’s all just media stuff and for fun.

The one service that is separate is Pangolin on a DigitalOcean droplet. I just handle that manually when it says there’s an update. Still effectively just docker, but no easy button.

I could automate these more, but I would spend more time setting it up than I would save since it only takes me a couple minutes maybe once a week.

Backup? Psh… That’s what the lab is for.