starred/uptime-kuma

Fork 0

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

Backup doesnt restore monitor notifications #1076

New issue

Closed

opened 2026-02-28 02:09:12 -05:00 by deekerman · 3 comments

deekerman commented

2026-02-28 02:09:12 -05:00

Owner

Originally created by @ARPABoy on GitHub (May 10, 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

I have installed last uptime-kuma version: 1.15.1 under Ubuntu22.04/amd64 and node: v16.15.0
The steps to reproduce are:

I configure some notifiation methods
I configure one monitor enabling some notification methods
I backup uptime-kuma
I restore uptime-kuma

The monitor is restored but with all notification methods disabled.

👟 Reproduction steps

The steps to reproduce are:

I configure some notifiation methods
I configure one monitor enabling some notification methods
I backup uptime-kuma
I restore uptime-kuma

The monitor is restored but with all notification methods disabled.

👀 Expected behavior

A complete restoration including monitors and the linked notification methods of each monitor.

😓 Actual Behavior

The monitors are restored but with all notification methods disabled.

🐻 Uptime-Kuma Version

1.15.1

💻 Operating System and Arch

Ubuntu22.04/amd64

🌐 Browser

Version 101.0.4951.54 (Build oficial) (64 bits)

🐋 Docker Version

No response

🟩 NodeJS Version

16.15.0

📝 Relevant log output

No response

Originally created by @ARPABoy on GitHub (May 10, 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 I have installed last uptime-kuma version: 1.15.1 under Ubuntu22.04/amd64 and node: v16.15.0 The steps to reproduce are: - I configure some notifiation methods - I configure one monitor enabling some notification methods - I backup uptime-kuma - I restore uptime-kuma The monitor is restored but with all notification methods disabled. ### 👟 Reproduction steps The steps to reproduce are: - I configure some notifiation methods - I configure one monitor enabling some notification methods - I backup uptime-kuma - I restore uptime-kuma The monitor is restored but with all notification methods disabled. ### 👀 Expected behavior A complete restoration including monitors and the linked notification methods of each monitor. ### 😓 Actual Behavior The monitors are restored but with all notification methods disabled. ### 🐻 Uptime-Kuma Version 1.15.1 ### 💻 Operating System and Arch Ubuntu22.04/amd64 ### 🌐 Browser Version 101.0.4951.54 (Build oficial) (64 bits) ### 🐋 Docker Version _No response_ ### 🟩 NodeJS Version 16.15.0 ### 📝 Relevant log output _No response_

deekerman

2026-02-28 02:09:12 -05:00

closed this issue
added the
bug
label

deekerman commented

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

Author

Owner

@lucas-alcantara commented on GitHub (May 16, 2022):

Hi, I am experiencing the same thing. Before upgrading to 1.15.1, I backed it up. Even though all configured notifications are there after restoring the backup, they are all disabled. I am using Ubuntu 20.04 and Docker 20.10.15.

@lucas-alcantara commented on GitHub (May 16, 2022): Hi, I am experiencing the same thing. Before upgrading to 1.15.1, I backed it up. Even though all configured notifications are there after restoring the backup, they are all disabled. I am using Ubuntu 20.04 and Docker 20.10.15.

deekerman commented

2026-02-28 02:09:18 -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:09:18 -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