Selfhosted

39226 readers

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

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

Questions? DM the mods!

founded 1 year ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

A few Questions about reverse proxies and running your own Jellyfin server (lemmy.world)

submitted 10 months ago by KpntAutismus@lemmy.world to c/selfhosted@lemmy.world

23 comments fedilink hide all child comments

First things first, the setup is currently up and running. but i would like to modify it to use a reverse proxy through my personal domain.

Currently, i'm using an old pc with Truenas and a jail with jellyfin in it. i'm connecting to it with the free Fritz!Box VPN service.

but that's stupid and slow. so i've bought a domain at godaddy.com. but i don't understand the principle of whatever is managing the domain knowing the public IP-adress of my server. i've heard of Caddy, but it's also running locally, so i don't understand how i connect the pc to the domain.

if anyone could simplify this down for me, it'd be very helpful.

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

[–] rentar42@kbin.social 4 points 10 months ago

There's plenty of reasons why you would not want to have a Jellyfin server be publicly available (even behind authentication). It's simply not a well-secured system at this point (and may not get there for a long time, because it's not a focus).

I strongly suggest keeping it accessed via VPN.

But note that VPN access is not necessarily any slower than "publicly" serving the HTTPs directly, at least not by much.

If you don't already use Wireguard as the protocol, then maybe consider running a wireguard VPN instead, that tends to be quicker than classic OpenVPN.

And last but not least: a major restricting factor in performance of media servers from afar is the upload speed of your ISP connection, which is very often much lower than your download (100Mbit/10Mbit are common here, for example, so only 10% of the speed up than down).