Selfhosted

63012 readers

1691 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

Be civil.
No spam.
Posts are to be related to self-hosting.
Don't duplicate the full text of your blog or readme if you're providing a link.
Submission headline should match the article title.
No trolling.
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.
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:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

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

Questions? DM the mods!

founded 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

What else should I do for my home server security? (lemmy.world)

submitted 1 day ago* (last edited 1 day ago) by KingDingbat@lemmy.world to c/selfhosted@lemmy.world

29 comments fedilink hide all child comments

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

[–] stoy@lemmy.zip 4 points 1 day ago (3 children)

Have you read the TOS of your ISP, are you allowed to run a home server exposed to the internet?

It might be a good idea to at least read what the TOS says just so you are aware of potential consequences.

[–] dieTasse@feddit.org 9 points 1 day ago (1 children)

Can an ISP forbid you having your own home server? That doesn't sound legal. And if I am not mistaken the cloudflare tunnel is a lot like tailscale (which i would recommend over cloudflare anyway) it doesn't need open ports or anything like that.

[–] possiblylinux127@lemmy.zip -1 points 16 hours ago

They can forbid you from anything and they can terminate your service for any reason

[–] hendrik@palaver.p3x.de 6 points 1 day ago* (last edited 1 day ago)

And if you do, make sure to read them thoroughly. Most of these rules apply to for-profit hosting only. Or they're vague and they can't enforce them. And most contracts don't have rules anyway. They're mostly concerned with you not attracting DCMA complaints or a virus hosting some spam email server.

[–] zlatko@programming.dev 3 points 1 day ago

If the OP has it only reachable via a VPN, that might be good enough, it's not directly exposed. But otherwise yes.

Another, more important problem with publicly available home server: they lost their data when their setup was maintained by a professional hoster. According to the OPs words, they themselves "know just enough to be dangerous".

Exposing any of this to the public internet wouldn't be a good idea however you put it.