mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
Backup and restore issues #2883
Labels
No labels
A:accessibility
A:api
A:cert-expiry
A:core
A:dashboard
A:deployment
A:documentation
A:domain expiry
A:incidents
A:maintenance
A:metrics
A:monitor
A:notifications
A:reports
A:settings
A:status-page
A:ui/ux
A:user-management
Stale
ai-slop
blocked
blocked-upstream
bug
cannot-reproduce
dependencies
discussion
duplicate
feature-request
feature-request
good first issue
hacktoberfest
help
help wanted
house keeping
invalid
invalid-format
invalid-format
question
releaseblocker 🚨
security
spam
type:enhance-existing
type:new
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/uptime-kuma#2883
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @leochen12-rgb on GitHub (Dec 5, 2023).
⚠️ Please verify that this bug has NOT been raised before.
🛡️ Security Policy
Description
No response
👟 Reproduction steps
When using the backup function, restore the docker mapped data directory using the web interface after the backup is complete. These two restoration methods have bugs, can not restore the group information, all the hosts are restored together
👀 Expected behavior
Restore a backup
😓 Actual Behavior
Grouping disappears, hosts are all put together
🐻 Uptime-Kuma Version
1.23.8
💻 Operating System and Arch
centos stream 9
🌐 Browser
Google Chrome 119.0.6045.200
🐋 Docker Version
Docker 20.10.21
🟩 NodeJS Version
No response
📝 Relevant log output
No response
@rezzorix commented on GitHub (Dec 5, 2023):
There is a big warning written on the backup page: