Selfhosted

40411 readers

275 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:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
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.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

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

Questions? DM the mods!

founded 2 years ago

MODERATORS

Understanding proxies (self.selfhosted)

submitted 1 year ago by root to c/selfhosted

10 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

[–] root 1 points 1 year ago (2 children)

Ah I see. I think I read somewhere that using your own cert requires you to add it to each device that will access said service, which for me is a bit of a deal breaker. I don't think the rest of the family would be too thrilled; I have to make my projects somewhat transparent to them XD

[–] untilyouarrived 1 points 1 year ago (1 children)

I use a real domain name, but only have them available internally (and use WireGuard to access them when out and about). You can use letsencrypt with them then because you can validate through DNS.

[–] root 1 points 1 year ago (1 children)

I see. I have a valid domain as well that I could use, which would make things easier. I guess after I set things up, I can lock down Nginx/ my home lab again, and the certs would still work. My biggest worry was exposing my internal systems to the world.

[–] untilyouarrived 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 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.