Selfhosted

60525 readers

985 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

Be civil.
No spam.
Posts are to be related to self-hosting.
Don't duplicate the full text of your blog or readme if you're providing a link.
Submission headline should match the article title.
No trolling.
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.
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.

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 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

228

Is they're an easy way to make my Jellyfin accessible outside of my home network for free? (anarchist.nexus)

submitted 3 days ago* (last edited 3 days ago) by Vegan_Joe@anarchist.nexus to c/selfhosted@lemmy.world

163 comments fedilink hide all child comments

I have docker installed, but only have a vague idea of how it works.

Back in the day, I would just port forward, but even then, I would need a static IP somehow.

I have heard a reverse proxy is an option, but that is an entirely new topic to me.

Surely there is an easy way to access Jellyfin outside of my home network that I'm just missing.

*Edit: I am blown away by all the help and support! I currently have tailscale running, and I'm in the process of purchasing a domain.

Thanks everyone!

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

[–] pHr34kY@lemmy.world 3 points 3 days ago* (last edited 3 days ago) (2 children)

You can still just open it to the internet. Just do it on IPv6 instead. You won't find it by scanning IP ranges like they do on IPv4. You'll want to set up DNS for it though. Also get a free TLS cert from LetsEncrypt. It's a bit of work initially.

[–] frongt@lemmy.zip 8 points 3 days ago (1 children)

Assuming their ISP and everything else supports ipv6. An even so it'll still be visible through scanning, through brute force, or if anyone is reading cert transparency reports anf scanning the domains that show up.

[–] quick_snail@feddit.nl 1 points 3 days ago (1 children)

This. Better to hide it on a non standard port of an existing domain

[–] helix@feddit.org 1 points 3 days ago

Or to not do security by obscurity at all.

[–] mic_check_one_two@lemmy.dbzer0.com 7 points 3 days ago

Was going to comment something along the lines of “Inb4 someone posts that obscurity will keep you secure” but here you are. No, you won’t be secure just because it’s on IPv6. And TLS certs are open to the public, (they literally have to be, since any device attempting to access your server needs to be able to validate the cert) so bots will scrape them and instantly have whatever you made it for. So it wouldn’t even keep you obscure.