[Question] Best way to access Jellyfin remotely on linux + docker + vpn?

Hello!

I have Jellyfin running locally on my linux pc, in a docker container but I also use Mullvad vpn. I'm still newish to linux but I can access jellyfin through my lan. I am at a total loss with how to remotely access it remotely and securely. I think I need to split tunnel jellyfin but I also run arr apps in other containers. Maybe gluetun? I cant find a guide that tells me for sure but it sounds like what I may need

I have been through several guides for different methods but I'm at a loss on what to do.

Can anyone point me in the right direction?

You're viewing a single thread.

9 comments

Probably what you're looking for is the following setup:
docker <-> services <-> reverse proxy <-> VPN <-> Internet
Your next step is to chose a reverse proxy to handle your requests and serve your services on port 80 and port 443. There are several choice and you have to somehow stick with it, because each reverse proxy has it's up and downsides and learning curve:
Treafik (that's the one I use and is specifically made for containers)
Caddy (Never used it but heard only good things about it)
Nginx (this one is a beast to tame, however I heard it's easier to setup with nginx proxy manager)
Those are the 3 big players I'm aware of.
You reverse proxy ready and functional you need something to access them outside your LAN. There are also several ways to achieve the same goal. The one I use and are happy with is to configure Wireguard on your server and only open the port needed to connect to it.
This is also a big part and probably this is the route of a tinkerer and have lot of personal time to spare... There are easier AIO routes that will probably save you time and energy. (Others will point you to the right direction)
Bonus tip
You will rapidly understand the necessity of DNS. Reaching out to your services by IP:PORT will annoy you over time, even if you save them as bookmarks. Also if you don't assign a static IP to your containers they will change every time you restart them or reboot your server. Not very practical !!
Here you have 2 choices:
personal mini certificate authority (totally free and personal local domains but harder to setup)
cheap domain name with automatic certificate generation.
I personally chose the tinkerer route and learning process. But I have time to spare and while I prefer this route... It's very time consuming and involves a lot of web crawling and books reading.
If you are interested I can recommend you a good ebook on how to setup your own mini-CA :).
Hope it helps, you are halfway through !
- Nice explanation =). I am not OP but I am curious about one point: you seem to have the reverse proxy on your homeserver, not on the VPS.
  Is wireguard enough then to tunnel HTTPS traffic to your reverse proxy? Or do you need a more sophiscated tunnel (e.g. ngrok, boringproxy).
  P.S. I actually assumed that your VPN entry point is a VPS with a public, static IP. Therefore I understood that your were talking about two servers: the home server with the reverse proxy and a VPS as wireguard entry point. Please correct if this is wrong.
  
  Hi there ! Sorry my English is not that good, but I'm doing the best I can !
  Actually, I do not have a VPS. I use an old spare laptop as server which handles everything.
  I have Wireguard barebone installed with a a second external wireguard interface and some iptables to send all traffic to ProtonVPN.
  All my containers,on the same laptop, are directly reachable via this configuration and HTTPS is handle by Treafik with my self-signed local certificates (root CA with intermediate CA).
  Eg: From my mobile over WiFi or 4G I can access all my containers where ever I'm. My endpoint in my Wireguard's confirguration (on my phone) being my home's public IP.
  I hope I answered your question? If not I'm willing to give you a diagram of my setup, this will probably clear up the confusion/question? And will probably be way more explicit than my broken English 😄.
  
  You perfectly answered my question, thanks! You're fortunate to have a public IP at home. Many self-hosters need a VPS just for the public IP 👌 I had thought this was your case.

9 comments