Google Chrome is marking Umami self-hosted installation as dangerous, and now I'm concern using the tracking code

[Pureinfotech]

Hi,
I'm new to Umami.
I installed Umami on a VPS using Ubuntu, Docker, and Nginx.
I had a domain that I wasn't using, so I added it to this website for a better integration when adding the tracking code to the different websites.
Also, I set up Let's Encrypt to make everything more secure.
Soon after everything was set up, I wanted to access the site from the mobile browser, but I got the first "Dangerous" message.
The Google Safety system noted this: The site contains harmful content, including pages that: Try to trick visitors into sharing personal info or downloading software.
I can't find any resources from Umami about this.
One thing I thought was the redirect from the domain to the login page, so I just created a landing page with a button to the actual login. Now, I'm waiting to see if that makes any difference.
The installation in question is on WinSurBox dot COM.
Since this happened, I'm afraid to add the tracking code to the websites I want to track because if Google sees the domain embedded in the site, I don't know if it's going to mark the sites as dangerous, too.
Any help or recommendation will be helpful.

[michelmelo]

@Pureinfotech Hello, this could be the certificate that is wrong, try to look in the browser and the data of the certificate that you created contains the domain in question.

[Pureinfotech]

Hi, @michelmelo
Apparently, the certificate is correct.

[fulldump]

Hi, I am having the same issue, Have a SaaS application (https://flowtest.io) and I have installed umami in other domain: https://umami.hola.cloud . Now all hola.cloud has been marked as dangerous, even I have received a strike in youtube because one video links to hola.cloud.

Certificates seems to be OK

Google says it is dangerous:
https://transparencyreport.google.com/safe-browsing/search?url=umami.hola.cloud
https://transparencyreport.google.com/safe-browsing/search?url=hola.cloud

[maubut]

Same here.

I requested a review from Google Search console, still waiting.

[maubut]

Hey there,

I had the same issue with Chrome flagging my subdomain as a “Dangerous Site.” Yesterday, I added my domain to Google Search Console, verified it, and requested a review for the harmful content warning. This morning, the warning is gone, and everything works fine in Chrome.