SQLITE_CONSTRAINT: FOREIGN KEY constraint failed

[MisterCT42]

⚠️ 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 saw that there was a new version so I did the described steps: https://github.com/louislam/uptime-kuma/wiki/%F0%9F%86%99-How-to-Update

But after updating everything was gone.. thankfully I made a backup right before updating. But the restore is showing this error:

👟 Reproduction steps

Restore backup after updating to latest version.

👀 Expected behavior

Restore the backup with all my monitors

😓 Actual Behavior

Error popup message that show: insert into monitor_notification (monitor_id, notification_id) values (11, '7') - SQLITE_CONSTRAINT: FOREIGN KEY constraint failed

🐻 Uptime-Kuma Version

1.23.2

💻 Operating System and Arch

Portainer

🌐 Browser

Chrome

🐋 Docker Version

Latest

🟩 NodeJS Version

Latest

📝 Relevant log output

No response

[chakflying]

Please do not use the deprecated json backup feature.

If your previous data is missing after updating to 1.23, its likely due to a previously misconfigured data path. Please read this issue to check if you are affected and the solution to restore the old data: #3714 (comment)

[louislam]

Change to help as the backup feature is unmaintained and deprecated already.

[github-actions]

We are clearing up our old issues and your ticket has been open for 3 months with no activity. Remove stale label or comment or this will be closed in 2 days.

[github-actions]

This issue was closed because it has been stalled for 2 days with no activity.

[hvspa]

hello,
i am on .23 version, and was trying to backup restore with override option and got all my monitors deleted. are there any ways to restore them? maybe something to drop the database and have it re-created? or downgrade to older version restore there and upgrade?

now getting error

 insert into monitor_notification (monitor_id, notification_id) values (2, '1') - SQLITE_CONSTRAINT: FOREIGN KEY constraint failed

thanks

[CommanderStorm]

was trying to backup restore with override option and got all my monitors deleted. Are there any ways to restore them?

What did you do precicely?

[hvspa]

what i did is i exported the config, copy pasted one of the monitors' json, replaced the ID-s (+1 to the highest ID) and imported back with override option selected. then it started to complain about foreign keys. tried to import the original json, still same complaint, then wiped the databases, still same complaint about foreign keys

[hvspa]

what i did now, i deleted the kuma.db file, and then restarted the deployment, then imported the json again, and monitors appeared, but

1. they are not in groups, grouping them manually
2. my grpc monitors are down and UI does not allow me to edit them, when i click on them, nothing happen in the right frame of UI

[CommanderStorm]

Sorry to say, but the backup functionality is deprecated for a reason.
We recomend you to just backup the database instead in the UI.

Given that you deleted the db, there is nothing that can be fixed.

Things like groups, status pages, maintenances or the grpc monitor never got fully adopted into that feature.
The feature has been dropped in v2.0 (#4500)

If you want to import existing data sources of monitors, please use a third party tooling like AutoKuma or https://uptime-kuma-api.readthedocs.io/ instead

[hvspa]

Sorry to say, but the backup functionality is deprecated for a reason. We recomend you to just backup the database instead in the UI.

Given that you deleted the db, there is nothing that can be fixed.

Things like groups, status pages, maintenances or the grpc monitor never got fully adopted into that feature. The feature has been dropped in v2.0 (#4500)

If you want to import existing data sources of monitors, please use a third party tooling like AutoKuma or https://uptime-kuma-api.readthedocs.io/ instead

thanks for the links, this will be indeed useful. ended up re-creating some kafka monitors, manually adding the grpc monitors' proto-s, some postgres connection strings, but the main monitors got recovered on a blank database, which was a day saver.
thanks again!