starred/uptime-kuma

Fork 0

mirror of https://github.com/louislam/uptime-kuma.git synced 2026-03-02 22:57:00 -05:00

settings proxy import / export #3110

New issue

Closed

opened 2026-02-28 03:18:20 -05:00 by deekerman · 5 comments

deekerman commented

2026-02-28 03:18:20 -05:00

Owner

Originally created by @jacoballen55 on GitHub (Feb 8, 2024).

there is no option for proxies import. I raised this last year but no response.

🏷️ Feature Request Type

Settings

🔖 Feature description

adding proxy import would be good.

✔️ Solution

adding in settings to setup new proxy import in format
ip:port:username:password

❓ Alternatives

No response

📝 Additional Context

No response

Originally created by @jacoballen55 on GitHub (Feb 8, 2024). ### 📑 I have found these related issues/pull requests there is no option for proxies import. I raised this last year but no response. ### 🏷️ Feature Request Type Settings ### 🔖 Feature description adding proxy import would be good. ### ✔️ Solution adding in settings to setup new proxy import in format ip:port:username:password ### ❓ Alternatives _No response_ ### 📝 Additional Context _No response_

deekerman

2026-02-28 03:18:20 -05:00

closed this issue
added the
feature-request

A:settings

wontfix
labels

deekerman commented

2026-02-28 03:18:26 -05:00

Author

Owner

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

Proxy backup

I raised this last year but no response.

Not true, #2426 was closed as the backup feature introduced too many bugs and was unmaintainable.
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): # Proxy backup > I raised this last year but no response. Not true, #2426 was closed as the backup feature introduced too many bugs and was unmaintainable. 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

deekerman commented

2026-02-28 03:18:27 -05:00

Author

Owner

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

Proxy import

Why do you need this?
I am not quite convinced that adding such a feature would benefit the general user, as (at least the way I think our users use proxies => see #4456 for a relevant discussion)

I think the third party API might be a better fit¹ for your use case (you did not specify the WHY).

https://uptime-kuma-api.readthedocs.io/en/latest/api.html#uptime_kuma_api.UptimeKumaApi.add_proxy ↩︎

@CommanderStorm commented on GitHub (Feb 8, 2024): # Proxy import Why do you need this? I am not quite convinced that adding such a feature would benefit the general user, as (at least the way I think our users use proxies => see #4456 for a relevant discussion) I think the third party API might be a better fit[^1] for your use case (you did not specify the WHY). [^1]: https://uptime-kuma-api.readthedocs.io/en/latest/api.html#uptime_kuma_api.UptimeKumaApi.add_proxy

deekerman commented

2026-02-28 03:18:27 -05:00

Author

Owner

@bcookatpcsd commented on GitHub (Feb 12, 2024):

.. just wanted to add

K12 here.. 10 buildings.. heavy into proxying..

Migrated from a docker uptime-kuma to a standalone for db/latency issues..

Seems all the 'proxy checks' we had on defined hosts were not the the backup/migrations (in whatever state that is in)

It was not clear they were not in all that we migrated/moved.

@bcookatpcsd commented on GitHub (Feb 12, 2024): .. just wanted to add K12 here.. 10 buildings.. heavy into proxying.. Migrated from a docker uptime-kuma to a standalone for db/latency issues.. Seems all the 'proxy checks' we had on defined hosts were not the the backup/migrations (in whatever state that is in) It was not clear they were not in all that we migrated/moved.

deekerman commented

2026-02-28 03:18:27 -05:00

Author

Owner

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

@bcookatpcsd I don't fully know what you wanted to add.
Your comment does not go into why adding this via the thrid party API (https://github.com/louislam/uptime-kuma/issues/4465#issuecomment-1934470071) is not a better fit.

Migrated from a docker uptime-kuma to a standalone for db/latency issues

I don't know what you are trying to do, but docker and standalone should not have latency differences to access the SQLite database. If you are trying to access an external DB to execute checks on, the latency should also be basically the same.

If you are trying to run many monitors (~500 on regular disks) or have lots of retention configured, the proper fix for this is to upgrade to v2.0 (or 1.23.X if you have not yet, there are some fixes in said release such as incremental vacuum) once it is out.
We have made some deep performance improvements, like storing data in an aggregated form.

It was not clear they were not [in the backup]

That is why this feature will get removed in v2.0 as stated in https://github.com/louislam/uptime-kuma/issues/4465#issuecomment-1934462816.
I think the warning on the backup page is enough to discourage the usage or to not expect that the export will be complete:

deprecation warning on the Settings > Backup

@CommanderStorm commented on GitHub (Feb 12, 2024): @bcookatpcsd I don't fully know what you wanted to add. Your comment does not go into why adding this via the thrid party API (https://github.com/louislam/uptime-kuma/issues/4465#issuecomment-1934470071) is not a better fit. > Migrated from a docker uptime-kuma to a standalone for db/latency issues I don't know what you are trying to do, but docker and standalone should not have latency differences to access the SQLite database. If you are trying to access an external DB to execute checks on, the latency should also be basically the same. If you are trying to run many monitors (~500 on regular disks) or have lots of retention configured, the proper fix for this is to upgrade to `v2.0` (or `1.23.X` if you have not yet, there are some fixes in said release such as `incremental vacuum`) once it is out. We have made some deep performance improvements, like storing data in an aggregated form. > It was not clear they were not [in the backup] That is why this feature will get removed in `v2.0` as stated in https://github.com/louislam/uptime-kuma/issues/4465#issuecomment-1934462816. I think the warning on the backup page is enough to discourage the usage or to not expect that the export will be complete: <details><summary>deprecation warning on the <code>Settings > Backup</code></summary> <p> ![image](https://github.com/louislam/uptime-kuma/assets/26258709/2b0cff75-d056-4ac1-8f9a-c92f6e039241) </p> </details>

deekerman commented

2026-02-28 03:18:27 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Jun 1, 2024):

I think my argument from above why this can and should be solved via the third party api, the third party cli or in the future also the first party api (#118).
I don't see a reason for a dedicated proxy export/import to exist.
=> closing as not planned.

If I am missing a part, we can reopen this issue.

@CommanderStorm commented on GitHub (Jun 1, 2024): I think my argument from above why this can and should be solved via the [third party api](https://uptime-kuma-api.readthedocs.io/en/latest/api.html#uptime_kuma_api.UptimeKumaApi.add_proxy), the [third party cli](https://github.com/BigBoot/AutoKuma?tab=readme-ov-file#kuma-cli--) or in the future also the first party api (#118). I don't see a reason for a dedicated proxy export/import to exist. => closing as not planned. If I am missing a part, we can reopen this issue.