Same for me today, I can access via the red screen of doom using a browser but the app just crashes out. I filled out the Google link to unlock, let’s see if they resolve. I guess Google now owns the internet…
Resolved within 24 hours, Google can be my friend again
I have had this happen to me aswell on seemingly random occasions/periods and then it suddenly goes away, this also introduce a a problem connecting(authenticating) to HA as a custom app in Google assistant. I usually try a a few times and it goes away but since i reported it to google using the link/solution in the post by @anon63427907 and @Tinkerpop it works fine
There are multiple options to fix/work around this depending on your solutions.
In my case I’m using DDNS (dyndns.org) in combination with a reverse proxy NGINX and
I was able to fix it using this:
Go to https://search.google.com/u/1/search-console/welcome?pli=1
Enter my external HA URL under “URL prefix” and click “Continue”
Copy the html file name (e.g. google4199f7d8xxxxxxxx.html)
In the NGINX config, go to “Edit Proxy Host” and open the “Advanced” tab
Enter the following (of course replace the file name with yours):
location = /google4199f7d8xxxxxxxx.html {
rewrite ^/(.*) $1;
return 200 "google-site-verification: $uri";
}
Under “Custom Nginx Configuration” and “Save” the change.
Go back to the “Google Search Console” and click “Verify” (or similar).
Again, this solved the issue for my setup. Depending on your configuration, it might be different.
Your link doesn’t work to me. Can you use a different one so I can try your solution?
I need to review my instruction once I’m at a computer (only having my mobile phone with me). But you could check out Google’s support page for now:
https://support.google.com/webmasters/answer/34592
If you use DuckDNS you can also update the DNS TXT-Record with the google-site-verification token.
Any hint on how to do that DNS TXT-Record?
I’m running the duck dns addon
Just load this URL in a browser, ideally in incognito mode so the token doesn’t get stored in the history: https://www.duckdns.org/update?domains=YOURDOMAIN&token=YOURTOKEN&txt=YOURTXTRECORD
It took me some time but I eventually understood what @Hausanschlussraum meant:
google search console will give you a txt to add to your dns server. This is something that only a site owner can add.
Normally providers like namecheap have a control panel that give you the possibility of changing all your dns records, but unfortunately duckdns doesn’t. Apparently.
Indeed if you login to search console you will get the YOURTXTRECORD verification string. The other two fields (YOURDOMAIN and YOURTOKEN) come from your duckdns configuration.
Assemble the three strings in https://www.duckdns.org/update?domains=YOURDOMAIN&token=YOURTOKEN&txt=YOURTXTRECORD and paste the string in a browser. You’ll get an OK reply from duckdns when the record is properly added.
I did this and now you can reach my Fritzbox from the Internet. How can I undo this?
I clicked on the link on the left, i.e. took the domain
https://search.google.com/u/1/search-console/welcome?pli=1
I have the problem with a different URL
NET::ERR_CERT_AUTHORITY_INVALID
I updated the DNS TEXT entry on my duckdns domain and google was able to verify the token successfully. However, when I clear my cache and relaunch Chrome, I still get the deceptive error. How long does this take to go into effect? Should it be immediately?
I don’t think adding the TXT is enough, as it just opens up the access to google console, where it’s clearly said that the site has malicious actions and phishing too.
I think only the hassio team can fix it
2 days ago this started for me as well. I have sent 4 reports to google about white flag my page, still no response and it’s still red flagged. What have you done to resolve this?
Same here. Very annoying red warning. I can use alternative browser , but main issue is the HA app on my android 
Hit the wrong button.
Update: it has started flagging the site again so back square one and the fact that app does not work anymore
@mint_and_stone70 's method worked for me
This is where you would get the “yourtxtrecord”
Had the same problem, whitelisted the site by google, then it worked again. Now it stopped working again, though interestingly enough, the App now works just fine. Chrome and Firefox block it though…
The search console had no effect as far as I can tell…
Any suggestions? Happy about any hint in the right direction…
Same problem here 
Same here with a duckdns domain.
Does Google own internet ?!
Tried multi times the form without any result.
I had the nginx proxy manager add-on but no idea where to put the verification file.
I tried the nginx SSL proxy add-on with the same problem ; where put the verification file ?
Without access to the containers, how to do ?
Has someone any detailed instructions on how to do that on home assistant OS, please ?
Edit : so, I tried the below method :
https://www.duckdns.org/update?domains=YOURDOMAIN&token=YOURTOKEN&txt="YOURTXTRECORD" (with quotes)
and it prints “OK”.
Waiting for the good news…
This is driving me insane. Sent multiple requests to Google over the past week and still no response or fix. I did the duckdns verification method through google search console and sent a request for review with a very passive aggressive message since the last 4 requests done through the dangerous website popup were seemingly ignored. Hopefully this fixes the issue but I don’t have much hope.
Google seems to increasingly be a complete wasteland of software bugs and inoperability and I am getting to a point where I completely hate their services. This is partially why I switched to Home Assistant in the first place as Google Home is super buggy, crashes constantly on multiple devices, and increasingly nonfunctional.
Maybe this can be fixed such that the website does not get flagged by Google with future updates from the HA team?
It works with the duckdns address “trick” ! I hope it will last forever…
… And I think to go away of Google services when possible.