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.

[–] NotSteve_@lemmy.ca 3 points 2 years ago

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

[–] mp3@lemmy.ca 13 points 2 years ago (1 children)

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.

[–] Dagnet@lemmy.world 4 points 2 years ago (2 children)

Someone already suggested that but it seems to be missing a step, still need something to direct to the port I have for jellyfin?

[–] Blackmist@feddit.uk 4 points 2 years ago (1 children)

That's just on your router, no?

[–] Dagnet@lemmy.world 5 points 2 years ago (1 children)

no idea, I dont know how to do any of that

[–] Wistful@discuss.tchncs.de 3 points 2 years ago* (last edited 2 years ago) (3 children)

This tutorial explains everything in detail.

Edit: I stupidly assumed you are using windows. But anywayys...if you are thats a good tut

[–] PipedLinkBot@feddit.rocks 2 points 2 years ago

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.

[–] Dagnet@lemmy.world 2 points 2 years ago

I am on windows, your stupidity paid off. Hooray stupid but lucky people! (sadly Im only stupid, not lucky)

[–] Dagnet@lemmy.world 1 points 2 years ago

Followed that guide and only managed to make my duckdns domain lead to my router...

[–] mp3@lemmy.ca 2 points 2 years ago (1 children)

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.

[–] Dagnet@lemmy.world 1 points 2 years ago (1 children)

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

[–] mp3@lemmy.ca 3 points 2 years ago (1 children)

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

[–] YIj54yALOJxEsY20eU@lemm.ee 3 points 2 years ago

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.

[–] nickiam2@aussie.zone 11 points 2 years ago (1 children)

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

[–] Evotech@lemmy.world 0 points 2 years ago (1 children)

There's no way that's the simplest solution

[–] YIj54yALOJxEsY20eU@lemm.ee 5 points 2 years ago (1 children)

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.

[–] Fades@lemmy.world 1 points 2 years ago (2 children)

You don’t need to do anything for plex

[–] YIj54yALOJxEsY20eU@lemm.ee 2 points 2 years ago

It just streams it straight to their brains?

[–] MigratingtoLemmy@lemmy.world 1 points 2 years ago

JFL at using Plex with their shenanigans recently

[–] MonkderZweite@feddit.ch 7 points 2 years ago

VPN. Wireguard is pretty easy.

[–] gears@sh.itjust.works 5 points 2 years ago* (last edited 2 years ago) (1 children)

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"

[–] AVeryCleverName@lemmy.one 1 points 2 years ago (1 children)

How frequently does your cronjob run?

[–] gears@sh.itjust.works 2 points 2 years ago

I think every 12 hours? I'm not sure. But it doesn't need to be super frequent, unless your IP changes often

[–] mhz@lemm.ee 2 points 2 years ago

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.

[–] nolight@lemm.ee 1 points 2 years ago

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.

[–] Appoxo@lemmy.dbzer0.com 1 points 2 years ago

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.

[–] MigratingtoLemmy@lemmy.world 1 points 2 years ago

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.