Put your external facing services behind the VPN, or at least put them in a separate VLAN that’s firewalled in such a way that they can’t reach the rest of the network if they become compromised.

Setup automatic security updates with unattended-upgrades. I don’t know alot about your security expect for the fact that outdated applications are more vulnerable.

Fail2ban is useful to set up.

Seems like your edge server is acting as a proxy for a media server on some other host on your LAN.

You want to make sure that the media server software is setup securely, patched, and properly isolated from anything else in LAN should that become compromised. Proxy closes off a lot of attack vectors but not application vulnerabilities. The Lastpass hack happened because of some vulnerability in an employees home plex server.

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.

Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I’ve seen in this thread:

[Thread #316 for this sub, first seen 30th Nov 2023, 20:35] [FAQ] [Full list] [Contact] [Source code]

Where possible, use that WireGuard VPN to access services when away from home. Only expose services publicly if they absolutely must be exposed publicly.

You should follow best practices for the server itself too, even if you don’t expose SSH publicly. Make sure you’ve disabled password login for SSH (set PasswordAuthentication to no in /etc/ssh/sshd_config), and have disabled the root user (passwd -d root; passwd -l root). You can use sudo -i to get a root prompt when needed.

Install Crowdsec or Fail2ban and ensure you properly configure it to watch all the relevant logs for all public-facing apps. Someone attempting a brute force on any public-facing app should block them from everything on the server.

I’m using free DuckDNS domains

IMO, drop DuckDNS and use your own domain. Using a domain controlled by someone else is a security risk since the actual owner of the domain could get hacked and point your subdomain somewhere else, MitM the traffic, etc. There’s a bunch of cheap TLDs - .top is about $4/year. If you don’t mind spending a bit more, .com is about $10/year.

I have a domain for my personal site, and use the home. subdomain for my home server.

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)