starred/uptime-kuma

Fork 0

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

Imports for `docker-container` monitors are not correctly restored. #1350

New issue

Closed

opened 2026-02-28 02:18:17 -05:00 by deekerman · 2 comments

deekerman commented

2026-02-28 02:18:17 -05:00

Owner

Originally created by @mmuenker on GitHub (Aug 25, 2022).

⚠️ Please verify that this bug has NOT been raised before.

I checked and didn't find similar issue

🛡️ Security Policy

I agree to have read this project Security Policy

Description

The container-name and the selected docker host is not restored but empty.

The properties container-name and docker host are correctly exported and appear in the JSON file.

👟 Reproduction steps

Create docker-container monitor and create a backup. Then import the backup (with overwrite)

👀 Expected behavior

The docker-container monitor is restored with the container-name and docker host.

😓 Actual Behavior

The restored docker-container monitor has empty container-name and docker host inputs.

🐻 Uptime-Kuma Version

1.18.0-beta.0

💻 Operating System and Arch

Ubuntu 22.04 amd64

🌐 Browser

Chromium 104.0.5112.101

🐋 Docker Version

Docker 20.10.17

🟩 NodeJS Version

No response

📝 Relevant log output

No response

Originally created by @mmuenker on GitHub (Aug 25, 2022). ### ⚠️ Please verify that this bug has NOT been raised before. - [X] I checked and didn't find similar issue ### 🛡️ Security Policy - [X] I agree to have read this project [Security Policy](https://github.com/louislam/uptime-kuma/security/policy) ### Description The `container-name` and the selected `docker host` is not restored but empty. > The properties `container-name` and `docker host` are correctly exported and appear in the JSON file. ### 👟 Reproduction steps Create `docker-container` monitor and create a backup. Then import the backup (with overwrite) ### 👀 Expected behavior The `docker-container` monitor is restored with the `container-name` and `docker host`. ### 😓 Actual Behavior The restored `docker-container` monitor has empty `container-name` and `docker host` inputs. ### 🐻 Uptime-Kuma Version 1.18.0-beta.0 ### 💻 Operating System and Arch Ubuntu 22.04 amd64 ### 🌐 Browser Chromium 104.0.5112.101 ### 🐋 Docker Version Docker 20.10.17 ### 🟩 NodeJS Version _No response_ ### 📝 Relevant log output _No response_

deekerman

2026-02-28 02:18:17 -05:00

closed this issue
added the
bug
label

deekerman commented

2026-02-28 02:18:23 -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:18:23 -05:00

Author

Owner

@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

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 explanation: 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