Is Uptime Kuma 2.5.7 safe to update?

Probably yes. Bug fixes and minor features only, per the release notes. No breaking changes mentioned.

What users are reporting

2 public report(s) mention this version, 1 describing a bug or breakage. Most-discussed: “Connection to TCP port with SSL with self-signed certificate fails after update to 2.5.7”. Sources: GitHub · checked 2026-10-23

• Connection to TCP port with SSL with self-signed certificate fails after update to 2.5.7 (GitHub, describes a problem)
• Missing docker tag: `next-slim-rootless` (GitHub)

Reports are from public issue trackers and forums. Their count isn't a failure rate, and an empty list doesn't prove an update is safe.

⚠️ What breaks

Nothing in the release notes suggests breaking changes. This looks like a bug-fix or minor release. The usual precautions (backup, read notes) still apply.

Read the full official release notes →

✅ What to do first

1. Read the official release notes (linked in “What breaks”).
2. Back up config and data (snapshot the VM/volume if you can).
3. Note the version you are on now, so you can roll back.
4. Update, then check logs and core functions before walking away.

↩️ How to roll back to 2.5.6

Docker: snapshot/back up the data volumes first, then if needed change the tag back, e.g. image: louislam/uptime-kuma:2.5.6, and run docker compose up -d. Tag format varies by image (some drop the “v”), so check the registry’s tag list.