470
Jellyfin over the internet (startrek.website)
submitted 3 days ago by [email protected] to c/[email protected]

What’s your go too (secure) method for casting over the internet with a Jellyfin server.

I’m wondering what to use and I’m pretty beginner at this

(page 4) 50 comments
sorted by: hot top new old
[-] [email protected] 6 points 3 days ago

I just use tailscale. I am thinking about external share options but for me and my closests just plain simple tailscale

[-] [email protected] 7 points 3 days ago

Over the top for security would be to setup a personal VPN and only watch it over the VPN. If you are enabling other users and you don't want them on your network; using a proxy like nginx is the way.

Being new to this I would look into how to set these things up in docker using docker-compose.

[-] [email protected] 4 points 3 days ago

Is putting it behind an Oauth2 proxy and running the server in a rootless container enough?

[-] [email protected] 5 points 3 days ago

Jellyfin through a traefik proxy, with a WAF as middleware and brute force login protected by fail2ban

[-] [email protected] 6 points 3 days ago

I have had Jellyfin directly open to the Internet with a reverse proxy for years. No problems.

[-] [email protected] 3 points 3 days ago* (last edited 3 days ago)

If your reverse proxy only acknowledges jellyfin exists if the hostname is correct, you won't get discovered by an IP scanner.

Mine's on jellyfin.[domain].com and you get a completely different page if you hit it by IP address.

If it does get found, there's also a fail2ban to rate-limit someone brute-forcing a login.

I've always exposed my home IP to the internet. Haven't had an issue in the last 15 years. I'm running about 10 public-facing services including NTP and SMTP.

load more comments (1 replies)
[-] [email protected] 4 points 3 days ago

Synology worked for me. They have built in reverse proxy. As well as good documentation to install it on their machine. Just gotta configure your wifi router to port forward your device and bam you're ready to rock and roll

load more comments (4 replies)
[-] [email protected] 6 points 3 days ago* (last edited 3 days ago)

An $11/yr domain pointed at my IP. Port 443 is open to nginx, which proxies to the desired service depending on subdomain. (and explicitly drops any connection that uses my raw ip or an unrecognized name to connect, without responding at all)

ACME.sh automatically refreshes my free ssl certificate every ~2months via DNS-01 verification and letsencrypt.

And finally, I've got a dynamic IP, so DDClient keeps my domain pointed at the correct IP when/if it changes.


There's also pihole on the local network, replacing the WAN IP from external DNS, with the servers local IP, for LAN devices to use. But that's very much optional, especially if your router performs NAT Hairpinning.

This setup covers all ~24 of the services/web applications I host, though most other services have some additional configuration to make them only accessible from LAN/VPN despite using the same ports and nginx service. I can go into that if there's interest.

Only Emby/Jellyfin, Ombi, and Filebrowser are made accessible from WAN; so I can easily share those with friends/family without having to guide them through/restrict them to a vpn connection.

[-] [email protected] 2 points 3 days ago

This is an interesting setup

[-] [email protected] 3 points 3 days ago

VPN or Tailscale

[-] [email protected] 6 points 3 days ago

Personally I use twingate, free for 5 users and relatively straightforward to set up.

load more comments (4 replies)
[-] [email protected] 4 points 3 days ago

OpenVPN into my router

[-] [email protected] 5 points 3 days ago

I don't use jellyfin but my general approach is either:

  1. Expose it over a VPN only. I usually use Tailscale for this so that I can expose individual machines but you do you
  2. Cloudflare tunnel that exposes a single port on a single internal machine to a subdomain I own

There are obviously ways to do this all on your own but... if you are asking this question you probably want to use one of those to roll it. Because you can leave yourself ridiculously vulnerable if you do it yourself.

load more comments (2 replies)
[-] [email protected] 5 points 3 days ago* (last edited 3 days ago)

for me i just needed a basic system so my family could share so I have it on my pc, then I registered a subdomain and pointed it to my existing ec2 server with apache using a proxy which points to my local ip and port then I opened the jellyfin port on my router

and I have certbot for my domain on ec2 :)

load more comments (5 replies)
[-] [email protected] 3 points 3 days ago

Tailscale + Caddy (automatic certificates FTW).

[-] [email protected] 4 points 3 days ago

SWAG reverse proxy with a custom domain+subdomain, protected by authentik and fail2ban. Easy access from anywhere once it's set up. No vpn required, just type in the short subdomain.domain.com and sign in (or the app keeps me signed in)

load more comments (8 replies)
[-] [email protected] 4 points 3 days ago

Nobody here with a tailscale funnel?? It's such a simple way to get https access from anywhere without being on the tailnet.

load more comments (3 replies)
[-] [email protected] 4 points 3 days ago

For my travel devices, I use Tailscale to talk to the server. For raw internet, I use their funnel feature to expose the service over HTTPS. Then just have fail2ban watching the port to make sure no shenanigans or have the entire service offlined until I can check it.

[-] [email protected] 2 points 3 days ago

OpenVPN into my own LAN. Stream from there to my device.

load more comments
view more: ‹ prev next ›
this post was submitted on 26 Jun 2025
470 points (98.0% liked)

Selfhosted

46672 readers
1087 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS