this post was submitted on 20 Oct 2025
93 points (100.0% liked)

Selfhosted

53408 readers
362 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

  7. No low-effort posts. This is subjective and will largely be determined by the community member reports.

Resources:

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

Questions? DM the mods!

founded 2 years ago
MODERATORS
 

It is a major version update. It contains some breaking changes. Please read the migration guide carefully if you want to upgrade from v1 to v2.

top 10 comments
sorted by: hot top controversial new old
[–] datalogen@feddit.dk 45 points 1 month ago (2 children)

Sort of an ironic day to release an update for such a toolπŸ˜†

[–] bishoponarope@lemmy.world 12 points 1 month ago

@dear Mr bezos. Plz fix your shit. Sincerely. The uptime bear.

[–] non_burglar@lemmy.world 3 points 1 month ago (1 children)

Why? I don't think any part of uptimekuma relies on aws...

[–] dabaldeagul@feddit.nl 14 points 1 month ago (1 children)

No but uptime tracking is relevant due to other services being down.

[–] non_burglar@lemmy.world 1 points 1 month ago
[–] EarMaster@lemmy.world 7 points 1 month ago (1 children)

Setting aside the funny (if you're not affected) coincidence of AWS being down I have to say this is an exemplary way on how upgrades should be announced, executed and documented. There is a migration guide, but even if you don't read it - in most cases the software will take care of it itself. Well done!

[–] cron@feddit.org 0 points 1 month ago

Only downside I see is how long it took for version 2.0 to get released. The previous stable release (1.23.16) was released almost one year ago.

[–] cron@feddit.org 4 points 1 month ago* (last edited 1 month ago)

I've been using this new version a few weeks now (since beta 3). The most significant advantage is the performance improvement. With 100+ monitors, the "old" version was very sluggish and took a long time to start.

Edit: I migrated my existing install to mariadb following this thread on github.

[–] clifmo@programming.dev 3 points 1 month ago

If your host is using Debian / Raspbian Buster, you should not upgrade. Due to a bug in the libseccomp2 library, it will run into a startup problem. Read more: https://github.com/louislam/uptime-kuma/issues/41#issuecomment-896164516

I read this, but it seems to be ARMv7 only, per the issue title. A little wary still, tho my docker host is x86. I guess I'll try running a stand alone test to see if it boots.

[–] Appoxo@lemmy.dbzer0.com 1 points 1 month ago

Thank you very much!