Adding proxy / proxies to the backup file #2117

New issue

Closed

opened 2026-02-28 02:43:37 -05:00 by deekerman · 2 comments

deekerman commented

2026-02-28 02:43:37 -05:00

Owner

Originally created by @ahmadipiralvan on GitHub (Apr 17, 2023).

⚠️ Please verify that this feature request has NOT been suggested before.

I checked and didn't find similar feature request

🏷️ Feature Request Type

Other

🔖 Feature description

When the backup is taken, the proxies are missing and must be manually added again.
Now if we have 50 or more proxies it is very difficult!

✔️ Solution

Add the proxies to the backup file

❓ Alternatives

No response

📝 Additional Context

No response

Originally created by @ahmadipiralvan on GitHub (Apr 17, 2023). ### ⚠️ Please verify that this feature request has NOT been suggested before. - [X] I checked and didn't find similar feature request ### 🏷️ Feature Request Type Other ### 🔖 Feature description When the backup is taken, the proxies are missing and must be manually added again. Now if we have 50 or more proxies it is very difficult! ### ✔️ Solution Add the proxies to the backup file ### ❓ Alternatives _No response_ ### 📝 Additional Context _No response_

deekerman

2026-02-28 02:43:37 -05:00

closed this issue
added the
feature-request
label

deekerman commented

2026-02-28 02:43:41 -05:00

Author

Owner

@chakflying commented on GitHub (Nov 21, 2023):

Obsolete as the backup feature has been dropped in #3892.

@chakflying commented on GitHub (Nov 21, 2023): Obsolete as the backup feature has been dropped in #3892.

deekerman commented

2026-02-28 02:43:42 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Feb 8, 2024):

Chiming in with a more in-depth explainaition:

Please see https://github.com/louislam/uptime-kuma/issues/2141#issuecomment-1272360952

In 1.18.3, the backup feature was deprecated due to [being left] unmaintained.

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.0 the deprecated backup tool is being removed because of this reason.
Please consider using SQL, API based¹ or infrastructure based² 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:

#2496
#477

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 ↩︎

@CommanderStorm commented on GitHub (Feb 8, 2024): Chiming in with a more in-depth explainaition: Please see https://github.com/louislam/uptime-kuma/issues/2141#issuecomment-1272360952 > In 1.18.3, the backup feature was deprecated due to [being left] unmaintained. 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.0` the deprecated backup tool is being removed because of this reason. Please consider using SQL, API based[^1] or infrastructure based[^2] backup instead. New approaches to these features should use [SQLite dump](https://www.sqlitetutorial.net/sqlite-dump/) or [MariaDB dump](https://mariadb.com/kb/en/mariadb-dump/) respectively. (Here is our [contribution guide](https://github.com/louislam/uptime-kuma/blob/master/CONTRIBUTING.md)) You can subscribe to these issues meanwhile: - #2496 - #477 [^1]: using the third-party API: https://uptime-kuma-api.readthedocs.io/en/latest/ [^2]: see https://github.com/louislam/uptime-kuma/issues/477#issuecomment-1557966187 for a setup example