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

Selfhosted

63017 readers
2013 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
[–] foggy@lemmy.world 25 points 21 hours ago* (last edited 21 hours ago) (2 children)

Use authelia for 2fa

Disable root ssh

Disable password authentication for ssh. Keys only.

Set up Fail2ban

That's about all that's left; 2fa and brute force protection. Good job.

Sub fail2ban for wazuh. It does the same but so much more, and does everything with 0 config after fresh install.

[–] StateMachine@lemmy.zip 10 points 21 hours ago (2 children)

And move SSH to a non-default port. Without that, my public-facing servers get thousands of SSH attacks a day, and it basically goes to zero after moving it to a random-looking high port.

Also, totally agree with using public key login and disable password login.

[–] Ooops@feddit.org 11 points 19 hours ago (1 children)

That's generally good advice but not actually security related.

Removing all the stress on your ressources by using a non-standard port is good for your ressources, But those automated scanners looking for unsecured devices and trying out password like admin/admin are not actually a risk. It's just a case of security by obscurity and never actually serves its purpose.

[–] gastroglizzy@piefed.social 4 points 15 hours ago (1 children)

Very true. There are only ~65K ports. If someone decides they want to, trying all of them to see which one gives a valid response is trivial.

[–] foggy@lemmy.world 1 points 11 hours ago* (last edited 11 hours ago)

Literally a single nmap command will tell me where you "hid" your ssh port.

Like the poster you're responding to said, it is good advice but not for security. It takes you off the hacker spam list, essentially.

Rereading this it sounds like I am disagreeing with you sorry. Just trying to reiterate your point.

[–] possiblylinux127@lemmy.zip 0 points 15 hours ago* (last edited 15 hours ago)

OpenSSH rate limits authentication attempts so it isn't a big deal. My public VPS gets pounded but it doesn't matter as it doesn't really use any system resources.