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

Selfhosted

40394 readers
390 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 2 years 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 1 year ago* (last edited 1 year ago) by memmi@lemm.ee to c/selfhosted@lemmy.world
9 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
[–] MigratingtoLemmy@lemmy.world 3 points 1 year ago

Exposed parts can be messy if you're not used to them.

Easiest option would be to have a VPS set up as a VPN server with the ports you need forwarded to it, and your applications connecting to it. If you don't want the extra maintenance, Cloudflare tunnels for you. Racknerd boxes are $1/month.

Docker containers run as root by default. Either change the flag or switch to podman if you don't need root access for your containers.

Time to get a router compatible with OpenWRT/OPNsense.

There probably are better ways, but I'm totoo at the moment to recollect.