this post was submitted on 14 Jun 2023
5 points (100.0% liked)

Self Hosted - Self-hosting your services.

11594 readers
3 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

Important

Beginning of January 1st 2024 this rule WILL be enforced. Posts that are not tagged will be warned and if not fixed within 24h then removed!

Cross-posting

If you see a rule-breaker please DM the mods!

founded 3 years ago
MODERATORS
Zoe8338@lemmy.ml
dogmuffins@lemmy.ml
testman@lemmy.ml
5
How to host server outside network (sh.itjust.works)
submitted 2 years ago by HumanPerson@sh.itjust.works to c/selfhost@lemmy.ml
6 comments fedilink hide all child comments
 

Does anyone have any advice on hosting a server to the outside world? I intend to host a Jellyfin media server and want to be able to access it remotely. I was leaning towards hosting a VPN on my network with a good password but I don't know much about that. I am looking for a free option that ideally doesn't require proprietary software and can be completely hosted locally. For reasons that I won't go into, I am a little concerned about my isp seeing the traffic to the media server. I know I am being paranoid but I don't really care. I imagine if I host it through port forwarding on the router but set up HTTPS that would encrypt the traffic and stop my ISP from seeing it, but I don't know if hosting a VPN would be easier / more secure. Thoughts?

you are viewing a single comment's thread
view the rest of the comments
[–] fitgse@sh.itjust.works 0 points 2 years ago (1 children)

If you are ok with Jellyfin being public, then I would just put it in front of an nginx proxy. That way, your nginx proxy will handle SSL termination. With SSL, your ISP won't be able to inspect the traffic directly.

If you are running docker, then I'd recommend jwilder/nginx-proxy and its lets encrypt companion jrcs/letsencrypt-nginx-proxy-companion. It makes putting things behind an SSL proxy very easy! This of course assumes you have a public IP address through your ISP and aren't stuck behind CG-NAT!

A second option is to keep it private then use a VPN (this is what I do). Wireguard can be a good option although setting up each device is a bit manual, since you have to generate key pairs for each of them. This also requires you have a public IP through your ISP or have a public box that bridges your public VPN to your home network. That said, it works really well.

Tailscale is a free, but commercial option built on top of wireguard that makes set up a lot easier. If you are stuck behind CG-NAT this is probably your easiest option.

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

To Hijack this: If I wanted to host a public instance of jellyfin at jellyfin.mydomain.xyz, I would then need a dDNS hosted on my server, and then...? If I want to allow non-technical people to access my instances, how do I manage that? Could you point me to a guide that explains the overarching requirements that one would need for that, with a mention of examples for each service I need to host that I need to achoeve this? Because I am a bit lost atm :p

[–] fitgse@sh.itjust.works 1 points 2 years ago (1 children)

If you are running Jellyfin on a computer at home you’ll need to configure your dns with your dns provider to point to your home public ip then configure your router to forward port 443 to your Jellyfin server.

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

And this works even with a dynamic/non-static IP? I thought there was more hassle involved :D

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

No, if you don't have a static IP, you will need to use a dynamic DNS solution.

You might also investigate ipv6 if your ISP provides it. Often, if they don't give you a static ipv4 address, they might assign you a static block of ipv6 addresses you can use. That makes a big assumption that you can always use ipv6 though!