Updating is not worth it! #1953

Closed
opened 2026-02-28 02:38:14 -05:00 by deekerman · 1 comment
Owner

Originally created by @wilcochris on GitHub (Mar 1, 2023).

Copied the data directory as was suggested in the backup section of the dashboard.

Followed the guide to update Uptime Kuma

Restored data directory.

Everything is gone.

How do I get back the work I put into creating the monitors?

If there isn't a way then I will just ditch this as updating the container shouldn't kill all of the setup I have done. Extremely annoyed at this

Originally created by @wilcochris on GitHub (Mar 1, 2023). Copied the data directory as was suggested in the backup section of the dashboard. Followed the guide to update Uptime Kuma Restored data directory. Everything is gone. How do I get back the work I put into creating the monitors? If there isn't a way then I will just ditch this as updating the container shouldn't kill all of the setup I have done. Extremely annoyed at this
deekerman 2026-02-28 02:38:14 -05:00
Author
Owner

@github-actions[bot] commented on GitHub (Mar 1, 2023):

@wilcochris: Hello! 👋

This issue is being automatically closed because it does not follow the issue template. Please DO NOT open a blank issue.

@github-actions[bot] commented on GitHub (Mar 1, 2023): @wilcochris: Hello! :wave: This issue is being automatically closed because it does not follow the issue template. Please DO NOT open a blank issue.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/uptime-kuma#1953
No description provided.