this post was submitted on 29 Jan 2026
83 points (82.7% liked)
Selfhosted
60177 readers
874 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:
-
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.
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
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
IDK, if I were running the show, I'd probably have done the same thing especially when it started to involve other servers. I would assume that there would be some legal ramifications should it have just been ignored. It would have been good to observe to see if I could come up with who the puppeteer was, but I was super green then and probably wouldn't have known where to start as far as forensics. I mean, if you get hacked, the knee jerk reaction is to pull the plug, but it would be more productive to do some forensics before killing the server.
Yeah, I agree with 'nuke first ask questions later' when your compromised host is impacting other devices. If and only if i knew the attempts weren't going anywhere or doing anything would I consider unicing the vm/container to see what happened.
Now that I reflect on the embarrassment, it was a cheap, shared VPS and I'm pretty sure I was dogging the share. LOL Ahhhh....innocence. However, it was evident I needed some personal edification. Now, I am told, I over engineer security, but it works, so keep it the way it is.
At the very least, you could cut off Internet access and reduce vCores to 0.5, instead of completely shutting it down and only offering the user to book 4 hours of access during business hours as if they didn't have work too.