mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
proxy not exported when taking backup #1645
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#1645
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 @jacoballen55 on GitHub (Dec 16, 2022).
⚠️ Please verify that this feature request has NOT been suggested before.
🏷️ Feature Request Type
UI Feature
🔖 Feature description
With multiple proxies, when taking backup, proxies are not exported in json.
✔️ Solution
in settings page, if you could add dedicated proxy import/export using csv it would be amazing.
also when doing export, an option to export with proxies.
❓ Alternatives
No response
📝 Additional Context
No response
@jacoballen55 commented on GitHub (Dec 25, 2022):
any update here?
@chakflying commented on GitHub (Nov 21, 2023):
Obsolete as the backup feature has been dropped in #3892.
@CommanderStorm commented on GitHub (Feb 8, 2024):
Chiming in with a more in-depth explanation:
Please see https://github.com/louislam/uptime-kuma/issues/2141#issuecomment-1272360952
Backup & Restore with JSON has been deprecated and issues will not be fixed due to the amount of problems it has been causing for our users and us.
The current design is just not maintainable, causing countless bugs.
In
v2.0the deprecated backup tool is being removed because of this reason.Please consider using SQL, API based1 or infrastructure based2 backup instead.
New approaches to these features should use SQLite dump or MariaDB dump respectively. (Here is our contribution guide)
You can subscribe to these issues meanwhile:
using the third-party API: https://uptime-kuma-api.readthedocs.io/en/latest/ ↩︎
see https://github.com/louislam/uptime-kuma/issues/477#issuecomment-1557966187 for a setup example ↩︎