Selfhosted

573 readers

1 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.

Resources:

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

> Questions? DM the mods!

founded 1 year ago

MODERATORS

HybridSarcasm@lemmy.world

Understanding proxies (lemmy.world)

submitted 1 year ago by root@lemmy.world to c/selfhosted@lemmy.world

13 comments fedilink hide all child comments

Hey all,

So I've been playing with Nginx so that I can reference my self hosted services internally by hostname rather than by IP and port.

I set some custom entries in my pihole, setup the proxies on Nxing, and boom. All is working as expected. I can access Jellyfin via jellyfin.homelab, amp via amp.homelab, etc.

I wanted to have all of these internally facing, because I don't really have a need for them outside of my network, and really just wanted the convenience of referencing them.

Question 1) If I wanted to add SSL certs to my made up homelab domain, how hard would that be?

Question 2) When accessing something like Jellyfin via jellyfin.homelab, all traffic is then going through my nginx VM, correct? Or is Nginx just acting as a sort of lookup which passes on the correct IP and port information?

you are viewing a single comment's thread
view the rest of the comments

[–] untilyouarrived@lemmy.world 2 points 1 year ago* (last edited 1 year ago) (1 children)

Yeah. I don't expose anything other than the WireGuard port.

You can validate the wildcard certificate at your registrar, so you don't need to open anything up to the world.

[–] root@lemmy.world 1 points 1 year ago

Would you need to leave Nginx "online" after setting up the certs? I have mine so that it can't reach out at all.