this post was submitted on 09 Oct 2025
21 points (95.7% liked)

Jellyfin: The Free Software Media System

7611 readers
2 users here now

Current stable release: 10.10.7

Community Standards

Website

Forum

GitHub

Documentation

Feature Requests

Matrix (General Information & Help)

Matrix (Announcements)

Matrix (General Development)

Matrix (Off-Topic) - Come get to know the team and blow off steam!

Matrix Space - List of all the available rooms on Matrix.

Discord - Bridged to our Matrix rooms

founded 5 years ago
MODERATORS
 

I have been running a large server 24/7 for about a month and a half now. It is only for myself and the fam, no one else has access to it at all.

I'm trying to learn about selfhosting and whatnot, but it's....a lot. Is there anything I need to do specifically besides configuring it correctly in order to protect it and myself. I hear people talking about putting stuff in dockers, putting things behind a reverse proxy, a VPN, etc.

I do currently have it running behind ProtonVPN but that's it. Do I need to be doing more?

Thanks in advance for any help!

top 16 comments
sorted by: hot top controversial new old
[–] plantsmakemehappy@lemmy.world 16 points 3 days ago (3 children)

Don't expose it over the Internet, local network access only, is the easiest but also limits you to accessing it only at home.

You could use something like tail scale or setup your own wireguard server to keep it still local-ish but still allow trusted people access.

Reverse proxy with auth of some kind if you plan to expose it to the Internet.

[–] golden_zealot@lemmy.ml 1 points 2 days ago* (last edited 2 days ago)

Reverse proxy/SOCKS5 works well in my experience.

I have a little computer on my network which runs my VPN - then on that computer I have ssh listening on a non-standard port that my VPN's dyndns links up to a human readable hostname with a different port.

If I want to watch stuff off-network I just have to ssh -D to that hostname and port and then configure a browser to use the connection as a SOCKS5 proxy, then jellyfin and anything else I'm hosting works as if locally through that browser.

The ssh is key based as well, not password based - haven't had any incidents in doing it this way.

[–] bowreality@lemmy.ca 3 points 3 days ago (1 children)

Can you restrict Jellyfin itself to local network?

[–] oddlyqueer@lemmy.ml 13 points 3 days ago* (last edited 3 days ago) (1 children)

It is by default, you need to open ports on your router in order for it to receive traffic from outside your home network. And then configure those ports to forward to your jellyfin server.

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

Thanks for clarifying. No, it is only meant to be used as a centralized entertainment system here in my home. None of us care about taking said media with us when we leave the house.

[–] NameTaken@lemmy.world 8 points 3 days ago (1 children)

Is the server exposed to the internet at all? ie, Did you open a port on your firewall to allow inbound connections? If not, then nothing should be exposed to the internet and you should have no problem. Proton is also a vpn not a firewall and really doesn't offer much protection against attacks. It basically just muddies the water on the origin of your Internet traffic.

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

I did not do any configuration with the ports whatsoever. It's just one of my PCs connected to a NAS, which in turn streams television shows, movies, documentaries, and music throughout my home. No one else has physical access to the serup, and as far as I know, no one else has remote access to it either.

[–] orbituary@lemmy.dbzer0.com 8 points 3 days ago (1 children)

I don't expose mine directly. When I stayed in Mexico for a month, I connected to it via Tailscale.

[–] MTZ@lemmy.world 2 points 3 days ago (1 children)

Thanks for the answer! We don't care about taking the media with us when we leave every day. It is just meant to be a centralized home entertainment distribution system. If it ever does get to the point where we want remote access to it, I will look into Tailscale. Thanks again!

[–] orbituary@lemmy.dbzer0.com 2 points 2 days ago

Yeah, I think the only thing I would worry about at that point is a firewall with restrictive rules. Don't expose internal ports without proper MFA in place.

[–] Jakeroxs@sh.itjust.works 2 points 2 days ago

I expose mine, have crowdsec and Authelia in front and it's been fine so far, don't expose things like ssh to the internet and change the port for it and you'll probably be fine.

[–] hoshikarakitaridia@lemmy.world 1 points 3 days ago (1 children)

Hobbyist (not a security expert here) but using a VPN that's trusted should be fine. Your security hinges on proton's reputation but from what I know they're pretty good. If I'm wrong please correct me in the comments and I will edit this comment.

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

I've used the services of at least 9 or 10 VPNs over the years and I have not once been as satisfied with any of them as I am with Proton.

For only external vpns mullvad is pretty good. Also, tailscale is free and their node-based system is really good.

As an all-in-one solution proton is pretty much as good as it gets from what I've seen. One of my friends swears by it as well.

It really does seem that the only step up in security is deploying a wireguard or ovpn server yourself, which is a little more complex. Not arch Linux levels of complexity, but intermediate tinkerer levels of complexity.

I stopped doing it because maintaining that shit and debugging it everytime it breaks just sucks. Tailscale is easier. Still not happy with the amount of trust I put into tailscale though.