I used let’s encrypt and nginx addon to use DNS from my Asus Router and now it works fine. Duckdns addon is turned off. Only thing is my external url changed for now
I had the same until I remembered that I had to remove the lines from the config.yaml file, and then I was able to remove it. Not that it helped fix the problem, but at least you now know what was causing that.
Can also confirm with my own paid domain it works fine now. Had the same issues with DuckDNS over the past couple of days.
Same problem since a couple of days, works intermittently. I created new project with the same results, none are stable. I use duckdns and the home assistant is reach from internet. My internet provider is DIGI(spain), the public IP is located in Spain or Romania, depending on pool availability.
I am exactly in the same situation. With the exception is, I am in Romania. Your description matches exactly the behaviour I am experiencing. Not sure this is an ISP thing or something else though. Very stramge.
just switched from DuckDNS to personal domain, and no difference - have created an A record for Home Assistant which I’ll let percolate through the Interwebz before testing again later
Same problem here with my set up with duckdns as well. Out of nowhere it stopped working correctly 2 days ago.
For some reason I could turn on lights but not turn off lights with google home.
Thinking it was something with my set up I redid the entire setup process but now I cannot link Home Assistant with Google Assistant at all.
I can enter my credentials but then it indicates that “Something went wrong. Try again later”.
@mhendu This video seems to be a pretty good example of what you can do: Free Cloudflare Tunnel To Home Assistant: Full Tutorial! - YouTube
The main essence is to just not use duckdns anymore, because several of their name servers were down atleast yesterday. The video shows most of it, I think they use a free domain provider, but idk how reliable that domain will be after the reservation expires. So what i’d recommend you do is to buy a domain for like 5-10 dollars/euros a year, migrate it over to cloudflare’s DNS, install the tunnel addon for HA and then replace your google assistant console’s HA domain links that are currently example.duckdns.org with your own (sub)domain.
Now people might not like this, since it costs money, but it’s still a hell of a lot cheaper than 5 bucks a month for nabu casa(no hate to HA team, they do great work and support if you can afford it.), plus you get your own domain as bonus, you can maybe use to make a website in the future, or host your own private file server, w/e you like. Also you get the benefit of cloudflare’s speed as a DNS provider and all their other services too. Pick a good domain name.
Alternatively @levercrafts posted a different DNS solution a few comments above mine: Google Assistant Keeps losing connection with Home Assistant - #59 by levercrafts
Although i’d still prefer cloudflare so long as it stays free, since it offers alot more options and some routers may not have a local DNS.
I am having the exact same issue. I can reach my HA instance remotely though duck DNS but google side of things has broken.
Same here. I used google for a long time without any problems. I also use DuckDNS. I restarted configuring google assistant, but same issue. Google says can not connect. Also Google Calendars integration stopt working. Tried to re-add integration but same issue can not connect.
Thought I was going nuts until I finally found this thread…everything I found online yesterday was from a few years back.
For me it has been intermittent for the last 24 hours. It’s offline most of the time but looking at the Google home app, I can see it going online once in a while but only for a few seconds and then going back offline. Also using duckdns but as everyone said, have no issue reaching home assistant using duckdns myself.
If you’re running in Docker, you don’t have Supervisor or those add-ons readily available. Is there a solution for the Docker HA variant? Traffic for HA and a few other containers is behind NGINX reverse proxy. I’ve got lazy and forgotten how I set it all up because it just worked for 2+ years and I haven’t had to touch it. I’m sure it will come back to me once I start tinkering.
Mine configuration is working at this moment
Change DuckDNS for Synology DDNS did the trick for me. (for now)
Remember too replace the new DNS name in Google actions and the Homeassistant configurationfile (external_url).
I also use gBridge Google Assistant, giving problems too! is also fixed althoug i didn’t change anything related too gBridge, it still uses DuckDNS.
Thanks for pointing in the right direktion.
Hope it helps.
anyone else back up? all my lights came on as they’re supposed to this morning
1 Like
The video I linked shows a part where they add the tunnel as a trusted proxy, not sure if something similar would apply for a docker instance, but surely this connection can be tunneled in some way. I’m not experienced with running HA in virtual containers though, so I cannot really assist you with your use case.
A quick google search led me to this cloudflared tunnel docker daemon, with incidentally has also the same development name of the HA addon I use: Docker Hub
If you’re using a different DNS service, you’d have to set up a proxy tunnel some-other way to bypass NGINX.
Seems like duckdns is up now! Have been checking the last few hours and everything seems to be working again! 
2 Likes
Working properly now!
duckDNS? Google?
Mine is working too again
Mine is working as well.