this post was submitted on 29 Nov 2023
32 points (92.1% liked)

Selfhosted

39985 readers
880 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

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

Questions? DM the mods!

founded 1 year ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz
32
Seeking Advice to Ensure Robust Security for My Home Server Setup (lemm.ee)
submitted 11 months ago* (last edited 11 months ago) by memmi@lemm.ee to c/selfhosted@lemmy.world
10 comments fedilink hide all child comments
 

Hey everyone,

I'm looking for some insights to confirm if my home server's security is up to par against common cyber threats. Here's a brief rundown of my setup:

  1. External Ports: I've limited external access to only three ports:

    • Port 80 and 443 for Nginx-Proxy-Manager
    • Port 51829 for Wireguard VPN

  2. Hardware:

    • I'm running a Raspberry Pi 4 and a Mini PC.
    • Both are connected to the router via Ethernet.

  3. Network:

    • NPM is set up for reverse proxy.
    • SSL is enabled for local DNS - to avoid memorizing IP addresses.

  4. Docker:

    • All applications are containerized and use network_mode: bridge.

  5. Internet-Facing Services:

    • Only two services are exposed to the internet:
      • A media server
      • The Wireguard VPN
    • I'm using free DuckDNS domains, configured with NPM.

  6. Firewall:

    • Currently, I'm relying on the default settings of Debian 12 and the Docker engine.
    • I haven't set up any specific firewall rules.

Given this setup, do you think my security measures are sufficient? I'm particularly curious about the risks associated with my Docker containers and the exposed ports. Any recommendations or best practices you could share would be greatly appreciated!

Thanks in advance for your help!

you are viewing a single comment's thread
view the rest of the comments
[–] Gooey0210@sh.itjust.works 1 points 11 months ago

Just in case, if you have jellyfin facing the web, jellyfin is not very secure, it has some vunurabilities unpatched for like forever I personally would recommend hiding it behind the VPN, and making it available to everyone at home Or as minimum or a good practice create locations in nginx to block for example logins outside of the VPN or house So to login you need to be at home.or connected to the VPN (useful if you have other people using your services, so they they they can login at home, but continue using everything outside)