this post was submitted on 12 Feb 2026
30 points (100.0% liked)

Selfhosted

61189 readers
288 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
 

Can someone recommend some self-hosted or not, tool that I could schedule for periodical scans of all I host and is exposed to public internet?

I think I did all by the book now, including crowdsec and/or fail2ban, but recently for example I got an email from German CERT that my n8n is out of date and has some CVEs. All of them were not exploitable in my case but that got me thinking that if CERT can do it, maybe there are some services or tools that I could use and get alerts sooner if something is vulnerable in my infrastructure.

Any recommendations welcomed! Ideally self hosted and FOSS of course.

you are viewing a single comment's thread
view the rest of the comments
[–] KairuByte@lemmy.dbzer0.com 2 points 5 months ago (2 children)

Auto updating can be a problem. Take a look at the CrowdStrike fiasco a couple years back.

[–] moonpiedumplings@programming.dev 1 points 5 months ago* (last edited 5 months ago)

If your software updates between stable releases break, the root cause is the vendor, rather than auto updating. There exist many projects that manage to auto update without causing problems. For example, Debian doesn't even do features or bugfixes, but only updates apps with security patches for maximum compatibility.

Crowdstrike auto updating also had issues on Linux, even before the big windows bsod incident.

https://www.neowin.net/news/crowdstrike-broke-debian-and-rocky-linux-months-ago-but-no-one-noticed/

It's not the fault of the auto update process, but instead the lack of QA at crowdstrike. And it's the responsibility of the system administrators to vet their software vendors and ensure the models in use don't cause issues like this. Thousands of orgs were happily using Debian/Rocky/RHEL with autoupdates, because those distros have a model of minimal feature/bugfixes and only security patches, ensuring no fuss security auto updates for around a decade for each stable release that had already had it's software extensively tested. Stories of those breaking are few and far between.

I would rather pay attention to the success stories, than the failures. Because in a world without automatic security updates, millions of lazy organizations would be running vulnerable software unknowingly. This already happens, because not all software auto updates. But some is better than none and for all software to be vulnerable by default until a human manually touches it to update it is simply a nightmare to me.

[–] exu@feditown.com 1 points 5 months ago

That's why you have regular snapshots, backups and monitoring