Hoping for a guide on setting up remote access for Jellyfin via TOS6/Jellyfin App

[Hrimnir]

Hey all. I was hoping someone might have a guide that's specific to terramaster's OS. I know its a linux based OS, but are the apps that you install through TOS running in dockers or?

I'm probably in a lot over my head because 1. I'm not a linux guy, and 2. I'm not a virtualization guy either haha.

Mainly, I use the built in Jellyfin "app" that was available in TOS6 and it works wonderfully from within my internal network. I am wanting to setup remote access so that when I'm away on trips, or if I'm at a family members house, i can utilize Jellyfin.

My initial research has told me that the preferred method would be to setup and use a reverse proxy. After reading through some of the guides, I believe this may be over my head from a technical perspective, but I'm willing to give it a try. However, usually these guides are talking about running things like docker containers, caddy, duckdns, etc. All of this is a little overwhelming, but it seems like the bulk of the effort/difficulty is getting the domain and the reverse proxy running, vs just configuring Jellyfin for remote access.

I've been told straight up port forwarding is an option but is an immense security risk as I'm essentially exposing everything to the internet so to speak (which, I feel like even a reverse proxy is doing this as well but with 1 extra jump between "you" and the internet?).

Either way, i was hoping someone far more knowledgeable than me could give me a few pointers, or at least point me in the right direction, cus right now I'm sort of a fish out of water. Thank you for any help anyone may be able to provide!

Edit: I forgot to mention, i know VPN is an option per se, but because my parents TV is an LG TV and uses WebOS as far as the research i've done they don't have VPN apps that will work on it. I was hoping to simply install the jellyfin app on the TV (like i have done at home) and simply direct it to the correct address and utilize it that way, much like running say Netflix, on the TV.

I personally *can* VPN into my network if its the only plausible option if im on a trip or otherwise outside the network, but, i'd prefer again to just use the app on my android device, or the desktop app, etc.

Their router is just the bog standard provided garbage all in one type thing that xfinity provides, so i doubt there is anything within the router i'd be able to utilize.

[londonwhite]

You can use a reverse proxy or VPN.

[jdcesari]

i used my internet provider dns
and opened the port.
chatgpt gave me the right procedure

[Fusor]

I'll share few tips as I'm also new to those stuff, though I've been behind of a PC for over 35 years, and I've started with a command line interface, so I've never feared it. Just using Jellyfin as an app from the store is fine, and it will work fine, I've never used it, I've been a Plex user for way too long, and as far as I remember Jellyfin is more anime oriented, Plex is all around the map (generally more anime NOT oriented, but works for it). So as I've said, running Jellyfin (JF) from the apps is easy, but what's the fun of having a NAS and not automating things on it, and then it's when it becomes a bit of a pain. As I've said, I don't use JF, I use Plex, but I can guess the way they work from the app store is identical (correct me if I'm wrong). So, for anime, first thing you'll want is Shoko, it hashes anime files, matches them in AniDB and can rename them according to your needs, moving the files also included, it has metadata agents for Plex and JF (think it's called Shokofin for JF, you can find it on their web site), thenofc you can add a torrent client to directly download stuff on your NAS, so you can pass the torrent, it downloads, Shoko gets the files, renames and moves in the Jellyfin library, easy work done for you. The you can search for Sonarr and Radarr, to help you with finding the stuff etc. Check what they do and you'll start wanting more, finding media has neveer been easier in my like, and I have my NAS for less than 2 months.
So, tip No. 1, learn Docker, it's easier running stuff in Docker, than installing them manually. You've said you're not Linux guy, I'm not one either, so to see what it does and how it works, there's Docker for Windows as well. And to describe you how things are, when you download software (in general life) you chose Windows, Linux (usually you have to chose from Debian, Ubunto etc.) or Mac, or....you can chose Docker, if you have a Docker engine, it is the same for all OS, inside the container, there's everything it needs to run, and it'll just run out of the box in 99% of the time. Think of it as a mini virtual machine, that comes preinstalled with eveerything it needs to run the specific program, you just put the container in it and it's ready to go. Also as a form of protection, Docker containers only expose few ports outside of the container, it's your choice if that port will stay in your local network, or you'll expose it to the internet. The other fun part is,when you install containers, they create their own networks, that are for the container itself, but, if you combine them in a compose, you create a virtual network between the containers, and if they have to talk to eachother, they can talk inside that network, totally isulated to the outside world. And here's where the reverse proxy makes things even better. So you remember you can access your NAS as TNAS.local, that is the DNS name in your local network, but, if you bind your network to a domain, and put a reverse proxy, you can do something similar to the internet, but with encription. So here how it'll work. You have your Docker containers in their own network, different from your local network, and unreachable, unless you adress the port itself (Ex. TNAS.local will oper the control interface, but TNAS.local:32400 will open Plex, and TNAS.local:8111 will open Shoko). If you configure the reverse proxy, you can bind your domain, you purchase or get for free, pointing your network IP accessible from the internet, and you open only ports 80 and 443, and that's all open to the internet. Let's say your domain is MytNet.com, and configure your router to lead all traffic from ports 80 and 443 to your reverse proxy server (NGINX, ex. TNAS.local:12345) and you configure your proxy connections, so you try access plex.MyNet.com, it finds MyNet.com is your internet IP, connects on port 80/443 -> router forwards to reverse proxy (TNAS.local:12345) -> reverse proxy finds that plex.*** is bound to TNAS.local:32400 and redirects the data back to you.
It became a bit chaotic, I know, sorry about that, if you have questions, ask me, not that I know all, I fight with it at this moment as well, so it's fresh in my head. Point is, start by finding out how Docker works, once you figure it out, you'll find that managing programs through containers maight be easier, than maniging them localy, or even in Windows. Docker programs are usually designed to work through web interfaces with eachother as well, you won't get to the point where one program deletes the files of the other program, like it maight happen in Windows. Once you get the hang on Docker, things will become easier for you, and you'll start getting more ideas.

P.S. Plex has it's own tunneling interface, in 90% of cases, you won't even need to open the Plex port to the internet, and it'll still work, just not on full speed and with full quality).

[Jeremy1]

You’re definitely not alone — reverse proxies and Docker setups can get confusing fast for beginners. I agree that TerraMaster could really use a simple TOS6-specific guide for Jellyfin remote access. Cloudflare Tunnel might also be worth looking into since it’s often easier and safer than direct port forwarding.

[Felix]

Our TOS7 Beta already includes Jellyfin in the App Center for remote access by default. You can upgrade to experience it if needed. For your data security, please read the Beta version upgrade instructions carefully before upgrading.