this post was submitted on 04 Jan 2026
128 points (97.8% liked)

Selfhosted

61949 readers
545 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:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.

  8. AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

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

Questions? DM the mods!

founded 3 years ago
MODERATORS
 

I created a short tutorial on using sub domains to access services hosted within my home network, thought I would share it here in case anyone finds it useful

This is the first time I've made a technical tutorial so apologise if there are mistakes/its confusing, feedback will be appreciated

you are viewing a single comment's thread
view the rest of the comments
[–] Appoxo@lemmy.dbzer0.com 1 points 8 months ago (1 children)

Better rather than worse, yes.

Just need to be aware if what you expose and how and where.

[–] Magnum@infosec.pub 1 points 8 months ago (1 children)

So its also not designed to be exposed via nginx?

[–] Appoxo@lemmy.dbzer0.com 2 points 8 months ago

Please stop nitpicking.
It's as insecure as every other software exposed to the internet.
It's just that some softwares (like Jellyfin) is more prone to be a risk than others (like nginx).

Juat be aware of what you do.