this post was submitted on 29 Oct 2025
96 points (99.0% liked)

Selfhosted

63843 readers
241 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
 

Or asked the other way around: How long do you keep your servers running without installing any software updates?

update means something like

sudo dnf update

or something ....

apt-get upgrade
apt-get update
top 50 comments
sorted by: hot top controversial new old
[–] mjr@infosec.pub 54 points 1 year ago (1 children)

Those apt commands are in a less-good order. It's usually better to update apt, then upgrade the system.

I upgrade as soon as reasonably possible after the notification appears, if the system isn't on auto-upgrade.

[–] njordomir@lemmy.world 3 points 1 year ago

I do sudo apt update && sudo apt upgrade

Is there any reason to not combine the commands since the output always prompts prior to changes anyway?

[–] dust_accelerator@discuss.tchncs.de 39 points 1 year ago (6 children)

Every night at ~ 12-1am

unattended updates / transactional-update are awesome.

Stuff has been running for years, and it's still up to date.

[–] southernbeaver@lemmy.world 22 points 1 year ago

This guy scares me

[–] DasFaultier@sh.itjust.works 5 points 1 year ago

This is the way! At least install security upgrades nightly using unattended-upgrades and reboot from time to time to get the latest Kernel version.

[–] gopher@programming.dev 2 points 1 year ago

Once per week for me. Works really great on openSUSE MicroOS. Had to roll back maybe a couple of times the last few years.

That said, I run basically everything in containers so the OS installed things are lean.

load more comments (3 replies)
[–] Dran_Arcana@lemmy.world 21 points 1 year ago (1 children)

Unattended-upgrade does security-only patching once every 4 hours (in rough sync with my local mirror)

Full upgrades are done weekly, accompanied by a reboot

I find that the split between security patching and feature/bug patching maintains a healthy balance knowing when something is likely to break but never being behind on the latest cve.

[–] cenzorrll@piefed.ca 3 points 1 year ago

For me, unattended-upgrade does it's thing. Updating other packages happens whenever I think about it. Very few things are not containerized and there's very little added beyond the base Debian install, so when I do update its maybe a dozen packages.

I would previously reboot during thunderstorms if we lost power, but now that I've got a UPS I probably ought to come up with a different plan.

[–] sneezycat@sopuli.xyz 17 points 1 year ago* (last edited 1 year ago) (3 children)

Well, one of the reasons I'm using debian on my server is so I can kinda forget about it...

I'll update maybe once a month, or every couple months. I don't always restart though, so my kernel is probably a bit behind :'D

[–] eksb@programming.dev 7 points 1 year ago (1 children)

I use Debian stable and subscribe to the debian-security-announce mailing list, so I update each time I get an email from it.

load more comments (1 replies)
[–] atzanteol@sh.itjust.works 4 points 1 year ago (7 children)

That's... Not how it works.. Debian is "stable" not "secure". You use Debian so that is easier to run updates frequently since they'll be unlikely to break things.

load more comments (7 replies)
[–] PlanterTree@discuss.tchncs.de 4 points 1 year ago* (last edited 1 year ago)

lol. Same issue for me. I run it for months, and surprisingly (for me) nothing breaks at all.

But fucking ssh shows warnings regarding some "post quantum crypto" stuff; recommending software update, that was not there before lol.

[–] CompactFlax@discuss.tchncs.de 13 points 1 year ago (1 children)

When I remember. About once a month.

[–] spacelord@sh.itjust.works 5 points 1 year ago* (last edited 1 year ago) (1 children)

Same here. No auto updates, no touching of a stable system without my manual intervention. 😅

[–] CompactFlax@discuss.tchncs.de 4 points 1 year ago

Last thing I need in my life is a broken system at home when I don’t have time for it!

[–] pHr34kY@lemmy.world 11 points 1 year ago

Whenever I ssh into it.

[–] slazer2au@lemmy.world 7 points 1 year ago

Once a week. I have a bash script that does an apt update upgrade and pulls new docker images.

[–] rikudou@lemmings.world 6 points 1 year ago

Monthly unless I learn about a vulnerability that would require it sooner.

[–] hexagonwin@lemmy.sdf.org 5 points 1 year ago

maybe like once in 3 months. i usually update when i need to setup something new on the server that needs to install new packages.

[–] Sir_Kevin@lemmy.dbzer0.com 5 points 1 year ago

On Windows, almost never since it was a disruptive shitshow. Now that I've got everything running Linux it's weekly. Often sooner if I happen to be remoting in and manually update.

[–] deleted@lemmy.world 4 points 1 year ago

I do it every 3 to 5 days. I usually do it when I have time to fix things if it goes south.

[–] lambalicious@lemmy.sdf.org 4 points 1 year ago

Only mostly when I want to. Which tends to be on Mondays and Saturdays.

I'm running Sid on servers, so automatic updates are actually a risk. Used to be Debian Stable, but maaan the docker and podman improvements.... make me drool.

[–] hydrian@twit.social 3 points 1 year ago (2 children)

@PlanterTree Systems facing public internet, security updates are applied daily automatically.

[–] PlanterTree@discuss.tchncs.de 4 points 1 year ago

up to now I install all my updates manually, maybe I should look into this: how to auto-update.

[–] Passerby6497@lemmy.world 2 points 1 year ago* (last edited 1 year ago) (1 children)

Can I ask how you do that? I have some debian and fedora boxes I should configure for that

[–] First_Thunder@lemmy.zip 3 points 1 year ago

Using nix :P

I update the flake every now and then via nix flake updated and then do a rebuild

[–] Shimitar@downonthestreet.eu 3 points 1 year ago* (last edited 1 year ago)

Gentooer here. Emerge sync &; world daily at night.

Weekly a manual check for stuff that doesn't autoupdate for reasons.

Monthly / biweekly podman compose pull for containers. Manual, because i don't trust that kind of autoupdate.

Edit: opnSense updates are manual only when I remember because if it breaks, I must be at home to fix it or i lose remote access and that's bad.

[–] reseller_pledge609@lemmy.dbzer0.com 3 points 1 year ago* (last edited 1 year ago)

I SSH in and run an update manually, once a week.

I'm not knowledgable and comfortable enough to let updates happen automatically and feel like I could trust it to keep running. Not yet, anyway.

Edit: But at some point I might do what another commenter said and make sure security updates run automatically and check other updates weekly.

[–] lemming741@lemmy.world 3 points 1 year ago

Probably every 2 months. When I have a day off work with nothing to do. I have a few VMs that are more fragile than I want to admit and if something breaks I want to have time to tinker instead of just restoring a backup.

[–] confusedpuppy@lemmy.dbzer0.com 3 points 1 year ago (2 children)

On Alpine Linux I update my two Pi servers at 2 in the morning daily. It's simpler compared to Debian which needs unattended-updates. Just add apk update && apk upgrade to a cron job and you're good to go.

I only have three docker services which is simple enough to update manually.

I like to keep things as simple as possible for my already chaotic brain.

[–] non_burglar@lemmy.world 4 points 1 year ago (1 children)

Be careful with unattended upgrades, even on alpine. A recent breaking change in python3 broke my alpine 23 ansible instance. Thankfully I have backups, but if you're going to automate the upgrade, you should automate tests as well.

load more comments (1 replies)
[–] stratself@lemdro.id 2 points 1 year ago (1 children)

To make it even simpler, apk -U upgrade

apk seems to have some tricks in there that aren't as well known.

I managed to catch in the IRC channel that apk add doc will automatically download any related man pages for packages with any future downloads through apk. That made life a bit more convenient instead of downloading all those packages separately.

[–] eager_eagle@lemmy.world 3 points 1 year ago* (last edited 1 year ago)

everyday to once a month, depending how often I use the server

IME usually waiting longer to apply larger updates causes more issues than smaller and more frequent ones

[–] Evotech@lemmy.world 3 points 1 year ago

Weekly. Cronjob.

[–] Auli@lemmy.ca 3 points 1 year ago (1 children)

Every day or at least once a week. Should automate it.

load more comments (1 replies)
[–] Treczoks@lemmy.world 2 points 1 year ago

Apt update and upgrade happen automatically.

[–] jbk@discuss.tchncs.de 2 points 1 year ago

podman quadlets with auto updates running on opensuse microos

im not yet self hosting a ton of services tho

[–] illusionist@lemmy.zip 2 points 1 year ago

On my ubuntu I use unattended updates but that doesn't work reliably. I have to update it manually most of the time. Once every other month.

On my fedora server it auto updates every day at 4 reliably.

The next server is going to be atomic such that the server restart is even shorter (not that I would care about it at 4).

[–] snekerpimp@lemmy.world 2 points 1 year ago

Almost everything I have runs Debian or NixOS, so…….. once a month? Except for VMs I’m playing around with, which usually get updated every time I log into them, or instal stuff.

[–] jimmy90@lemmy.world 2 points 1 year ago

my nixos containers and the podman containers inside them update nightly around 03:00

[–] sobchak@programming.dev 2 points 1 year ago (2 children)

When something doesn't work. I.e. when an app update causes incompatibility with a service. I think I have one server that's a few years without an update (distro version may actually be EOL for all I know).

load more comments (2 replies)
[–] troed@fedia.io 2 points 1 year ago

All services are dockerized, updated nightly.

Server OS runs a kernel-patch service for real time exploit patching.

All other updates as soon as they appear.

Yeah, sometimes I'll need to go in a repair - but that's way better than having to clean up after having been exploited due to not keeping up on security patches.

[–] bjoern_tantau@swg-empire.de 2 points 1 year ago

Automatic upgrades handle the security patches. Everything else maybe once a month. My big services like Nextcloud auto update as well.

load more comments
view more: next ›