Yesterday I pasted a password from Chrome’s saved passwords and instantly all of my duckdns self-hosted sites start with the Deceptive site ahead warning.
Interesting though that I have the same page loaded in two tabs now and this is what the address bars look like:
Google recently seem to be blocking our prefixed duckdns addresses as unsafe/dangerous, You can ask google to permit this as safe following a rewiew at Report Incorrect Phishing Warning
Supplying your address.
https://youraddress.duckdns.org/
It’s very annoying but I guess google have had to step up their client protection given the recent cyber defence intitieves instigated from Russia.
It’s not just duckdns. I got this for my own domain, and I doesn’t let me through at all.
Fortunately, I have another domain I’m using as backup.
This seem to be affecting the android app too. Get this when I open the app but when i choose to let me to the site anyway the app crashes.
Access through chrome still seems ok for me for now.
If you have your own domain, you can create a Google Search Console account, take control of your domain, and report that it is not deceptive. There is also a way to report a false deceptive alert for any domain (don’t have the link handy).
I did both of those and the next day everything was cleared.
Used your links the register my duckdns address and now warning has gone from both chrome and the home assistant app no longer crashes.
Many thanks.
My Nginx Proxy Manager settings seemed to have erased (although public access was still working). However, when I reinstalled the add-on, I am now getting the same ‘Deceptive Site Ahead’ screen when trying to access HA through my duckdns URL.
I dont see how supplying my URL to google’s “report incorrect phishing site” will suddenly resolve it when it was working before? Report Incorrect Phishing Warning
Am I missing something here? I have DuckDNS and Nginx Proxy Manager addons. Let’s Encrypt is set-up through Nginx.
I had the issue with missing settings too. After a while of troubleshooting, I found that I had created hosts and certificates with a user account that I removed later, which “broke” the DB relations. Eventually I was able to work around this by reactivating the account directly in the DB using the MySQL PlugIn. I also believe that I later changed the owner in the DB to my new account and could safely disable the “obsolete” account.
I’ve had this today as well. It started as I was setting up Alexa Media Player. I think the trigger was the callback url that is used for Amazon login. But that’s just a hunch.
I’ve requested delisting. we’ll see…
Same exact thing here. Always worked since a year and, after setting up Alexa media player integration yesterday, every browser started to say that my domain may be deceptive. Apparently the “domain name and the input do not match”.
God it is so frustrating to set up things just following tutorials and without knowing what you’re doing, but why should the integration affect the certificates?
Bernardo let us know if you have managed to resolve your issue. Same story… Once AMP installed suddenly site is marked as deceptive and mobile app crashes once reaches Lovelace !!!
Same thing here … I installed Alexa Media Player and Deceptive site is shown, after that Home assistant app keeps crashing on Android.
I want to buy Nabu Casa subscription but I only wanted to send text to voice notification to my Alexa echo device and I can’t see that Nubu supports that.
Do any of you know how any alternative to Alexa Media Player or simply a fix to Alexa Media Player and Deceptive site.
Thank you
My Android app has started crashing too now, I’ve not even added any new integrations. I do have Alexa Media player already installed. I’ve submitted the incorrect Phishing log, so let’s see if that fixes it. HA opens on my chrome browser once I click past the message, but on Android it loads for about a second then crashes
I’m having the same issue, except I’m not using DuckDNS. I have my own legal registered domain that I am using.
Mine was fixed same day once I submitted the request to Google
Adding Alexa to Home Assistant caused my Duckdns subdomain to get the Google warning splash page and that kills the app. Firefox did the same.
I switched to Nabu Casa remote access and it’s fine for now.
DuckDns is still totally blocked
You just need to submit the page to Google to get it unblocked, took less than 2 hours for it to resolve my issues
I think you may be onto something here… I setup Amason/ Alexa media player 2 days ago and now i’m getting this with my CloudFlare connection.
Anything here? I got the same and have been using Alexa media player for more than a year so I’m not sure this is the issue.
