False positive for Google Chrome dangerous website flag #6223
Description
📑 I have found these related issues/pull requests
N/A
🛡️ Security Policy
- I have read and agree to Uptime Kuma's Security Policy.
📝 Description
I've updated to version 2.0.1
No later than a few minutes after the update and my instance was up, my browser (Google Chrome) flagged all subdomains of my Uptime Kuma instance as dangerous.
I believe this has something to do with the update adding a /migrate-status route, and Chrome did not like it.
Unfortunately, Google Search Console does not show any sample URLs for "Deceptive pages", as they call it.
The ping was deemed necessary as this issue would prevent any sane access to a status page for non-tech people.
👟 Reproduction steps
Update from v1.x to 2.0.1
👀 Expected behavior
No false positive from my browser.
😓 Actual Behavior
A "Dangerous page" warning from Google Chrome, preventing normal access to the website.
🐻 Uptime-Kuma Version
2.0.1
💻 Operating System and Arch
Ubuntu Server 22.04
🌐 Browser
Google Chrome Version 141.0.7390.54 (Official Build) (64-bit)
🖥️ Deployment Environment
- Runtime Environment:
- Docker
- Database:
- SQLite: Embedded
- Database Storage:
- Filesystem: ext4
- Storage Medium: NVMe
- Uptime Kuma Setup:
- Number of monitors: 170
- 13.3 GB database
📝 Relevant log output
N/A