# How do you deal with OS updates on servers you can't afford to break? — retained record

> Retained reddit record from reddit:selfhosted.

Canonical: https://highsignal.app/data/records/a916bd974dae7388

[← sources](https://highsignal.app/data)


source: [reddit](https://highsignal.app/data/reddit) (reddit:selfhosted)  published 2026-09-14 14:38 ingested 2026-09-15 02:38

[original source ↗](https://www.reddit.com/r/selfhosted/comments/1wg58zk/how_do_you_deal_with_os_updates_on_servers_you/)

## retained text



```
I run a few VPS with webapps on them (Coolify + Docker). I'm a developer, not a sysadmin, and every time I think about updating the host OS I find a reason to do it next week instead.

Last time I did it, a service came back up but one container didn't, and I found out days later because nobody complained immediately. Since then I mostly just don't touch them, which I know is worse.

So, genuinely curious how other people handle this:

* do you update the host at all, or run it until the LTS goes EOL and rebuild?
* has an update ever actually broken something for you? what broke?
* when it broke, did you roll back or just fix it in place?
* do you snapshot first, or just hope?

Not looking for "use Ansible" - I'm sure that's right, I just want to know what people actually do in practice.
```



document fetched 2026-09-15 00:31 · canonical https://reddit.com/r/selfhosted/comments/1wg58zk/how_do_you_deal_with_os_updates_on_servers_you
