I only personally have experience with jellyfin, but the docs of Emby look to support the same remote access as Plex (without the TURN server).
So essentially you can use a login instead of a server IP, but it does require port forwarding or upnp on your router - which you may already have enabled.
halcyoncmdr@piefed.social 2 weeks ago
Yeah, via an Emby Connect account through their server infrastructure for the initial connection.
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.
hereiamagain@sh.itjust.works 2 weeks ago
So basically if I slap emby on an open port, and point my domain to my IP, it’ll work just the same. Connect is just for people without static IP addresses?
halcyoncmdr@piefed.social 2 weeks ago
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.
That’s backwards… Jellyfin was forked from Emby in 2018. Both have been developed separately since then, and are still very similar.