this post was submitted on 17 Oct 2026
99 points (100.0% liked)

Selfhosted

63910 readers
896 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:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.

  8. AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

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

Questions? DM the mods!

founded 3 years ago
MODERATORS
 

So I'm relatively new to server hosting. (But experienced with remote web hosting from providers.) After about a year of fighting to run Nextcloud on a hosting company and finally losing everything from the cPanel vulnerability a few months ago, I broke down and launched my own home server. I'm looking for advice to maximize security.

CachyOS Linux with ClamAV Docker via Portainer Nextcloud (E2EE), Immich, DocuSeal and NoteTrace Routed through a domain and subdimains via Zero Trust Cloudflare Tunnel and Cloudflare DNS.

I have regular redundant backups both onsite and offsite with Duplicati.

My passwords for OS and all admin dashboards are extremely long, unique, random strings managed by Bitwarden.

I know just enough about this stuff to get into trouble. What else should I setup? I have little to no monitoring going on and don't know much about that direction.

you are viewing a single comment's thread
view the rest of the comments
[–] Appoxo@lemmy.dbzer0.com 7 points 1 month ago (1 children)

Why should they take over the outer router if they can just take over the destination they were routed to?

[–] Treczoks@lemmy.world 1 points 1 month ago (1 children)

That is a separate issue. Hardening a single service that happens to offer a login is easier than hardening a whole bunch of services that were never intended to face the net.

[–] Appoxo@lemmy.dbzer0.com 4 points 1 month ago (1 children)

No I mean why would the attacker even attempt to attack your outside if they can just figure out what sits behind it, follow it through the NAT and then exploit it from there.

[–] Treczoks@lemmy.world 1 points 1 month ago (1 children)

I know that risk, but that has been mitigated by other means. There is no open port exposed to the net waiting to be hacked. It only opens on demand for a single connection.

[–] Appoxo@lemmy.dbzer0.com 1 points 1 month ago (1 children)

May I ask with what you initiate the connection?
Are you using some kind of STUN server/service?

[–] Treczoks@lemmy.world 1 points 1 month ago

Multiport Knock patterns.