I just use a free dynamic DNS provider (ie: DuckDNS), and most home routers are able to publish IP address changes to that DNS, otherwise you just need a small software to publish those change, which you can do ok the server hosting Jellyfin.
You’ll also need to do some port forwarding at the home router level so that external users can reach the server.
You’ll preferably want to do what’s called a DHCP reservation so that your server’s internal IP address remains the same, then do a port forward from your public port 8096 to internalIP:8096. That way, you just have to point someone outside of your network to hostname.duckdns.org:8096 (which will get resolved to your current public IP address) for your Jellyfin server.
Free services always have some kind of dubious hidden product they are selling elsewhere about you to someone else, because network hardware is not free, network system maintenance is not free, internet access is not free. Facebook is free, yet we all know what it’s true cost is.
DuckDNS is run by two guys who are funded by donations. I do agree with what you’re saying about free services but I’m more willing to trust DuckDNS in this case
The easiest way is to setup tailscale on the server, then share the server with the web interface. Your friends/family simply install the tailscale client, login, and it just connects like magic. No port forwarding or firewall configuration required. There’s plenty of how-tos out there.
I wouldn’t bother with a paid dynamic DNS. Most domain registrars let you change your DNS record with an API call (I know GoDaddy does because I use them.)
Then you just set up a cron job to fetch your IP and then change your DNS record to match. I use a subdomain because my main domain hosts a blog and some other stuff on a VPS, while my jellyfin server is at home.
A good search would be “[registrar name] dynamic DNS script”
Ddns is your answer, check your router and see what it can support or just go with whatever you feel good for you and install their updater on your server.
I’ve set up a cloudflare tunnel, all you need is a domain. It forwards my local Jellyfin instance to the public web, and is easy to get started with. I’m not sure how secure it is though, so I would appreciate any advice from more enlightened pirates.
Run a VPS as a VPN server with ports forwarded. Run a VPN client on your router to forward Internet facing traffic from Jellyfin to said VPN tunnel. Essentially, open ports on the VPS instead of your own router. This is conceptually similar to Cloudflare tunnels.
What is the easy way to share jellyfin over the internet? Portforwarding doesn’t work for me cause I don’t have a static ip address
EDIT: I thank all the answers but none of them seem actually easy
The issue of dynamic IP addresses is solved using a service like DuckDNS. Space Invader has some tutorials on it: https://youtu.be/CS72kN2c6hU
There is also ddns-updater which I like to use in docker
Run Opnsense or pfSense and do that from your firewall.
Here is an alternative Piped link(s):
https://piped.video/CS72kN2c6hU
Piped is a privacy-respecting open-source alternative frontend to YouTube.
I’m open-source; check me out at GitHub.
I just use a free dynamic DNS provider (ie: DuckDNS), and most home routers are able to publish IP address changes to that DNS, otherwise you just need a small software to publish those change, which you can do ok the server hosting Jellyfin.
Someone already suggested that but it seems to be missing a step, still need something to direct to the port I have for jellyfin?
That’s just on your router, no?
no idea, I dont know how to do any of that
This tutorial explains everything in detail.
Edit: I stupidly assumed you are using windows. But anywayys…if you are thats a good tut
Here is an alternative Piped link(s):
This tutorial explains everything in detail.
Piped is a privacy-respecting open-source alternative frontend to YouTube.
I’m open-source; check me out at GitHub.
I am on windows, your stupidity paid off. Hooray stupid but lucky people! (sadly Im only stupid, not lucky)
Followed that guide and only managed to make my duckdns domain lead to my router…
You’ll also need to do some port forwarding at the home router level so that external users can reach the server.
You’ll preferably want to do what’s called a DHCP reservation so that your server’s internal IP address remains the same, then do a port forward from
your public port 8096tointernalIP:8096. That way, you just have to point someone outside of your network tohostname.duckdns.org:8096(which will get resolved to your current public IP address) for your Jellyfin server.tried doing hostname.duckdns.org:8096 and it didnt work so Im not sure its supposed to be like that, website mentions something called caddy
you’ll need to have your own hostname and make it point to your home IP address, just in case it wasn’t clear enough
It’s good you are trying to help but I’m not sure someone copying and pasting whatever they read should have a port exposed to the Internet.
Purchase a domain and host it with a reverse proxy to your internal net.
You don’t even need to purchase a domain, free dynDNS services (DuckDNS or similar) are good enough for Jellyfin and the like.
Free services always have some kind of dubious hidden product they are selling elsewhere about you to someone else, because network hardware is not free, network system maintenance is not free, internet access is not free. Facebook is free, yet we all know what it’s true cost is.
DuckDNS is run by two guys who are funded by donations. I do agree with what you’re saying about free services but I’m more willing to trust DuckDNS in this case
deleted by creator
The easiest way is to setup tailscale on the server, then share the server with the web interface. Your friends/family simply install the tailscale client, login, and it just connects like magic. No port forwarding or firewall configuration required. There’s plenty of how-tos out there.
tailscale.com
There’s no way that’s the simplest solution
Not the simplest to set up, to make accessible, to secure, or for everyone else to use? This solution is a pretty reasonable one considering all four.
You don’t need to do anything for plex
It just streams it straight to their brains?
JFL at using Plex with their shenanigans recently
VPN. Wireguard is pretty easy.
I wouldn’t bother with a paid dynamic DNS. Most domain registrars let you change your DNS record with an API call (I know GoDaddy does because I use them.)
Then you just set up a cron job to fetch your IP and then change your DNS record to match. I use a subdomain because my main domain hosts a blog and some other stuff on a VPS, while my jellyfin server is at home.
A good search would be “[registrar name] dynamic DNS script”
How frequently does your cronjob run?
I think every 12 hours? I’m not sure. But it doesn’t need to be super frequent, unless your IP changes often
Ddns is your answer, check your router and see what it can support or just go with whatever you feel good for you and install their updater on your server.
Doesnt matter if you have dynamic or static.
But it will matter once CG-NAT comes into play.
Sincerely a dynamic IP jellyfin user with a reverse proxy.
I’ve set up a cloudflare tunnel, all you need is a domain. It forwards my local Jellyfin instance to the public web, and is easy to get started with. I’m not sure how secure it is though, so I would appreciate any advice from more enlightened pirates.
Run a VPS as a VPN server with ports forwarded. Run a VPN client on your router to forward Internet facing traffic from Jellyfin to said VPN tunnel. Essentially, open ports on the VPS instead of your own router. This is conceptually similar to Cloudflare tunnels.