Nabu Casa - Unable to reach the Home Assistant cloud

Configuration
1

After tying to login I get: Unable to reach the Home Assistant cloud.

Tried to Restarted Hass, restart RaspberryPi4, put cloud: in the configuration.yaml

I tried to create another account using Hass interface, it also showed “unable to reach…” but an email arrived at my account…so it reaches, and there should be some problem I didn’t know…

In the past week, I tried Hass in my OSX using docker and used this another Hass to create the account, I logged out there and trying to set up a new Hass using Raspberry Pi4…don’t know it could be the problem.

If I see the LOG, nothing is written there after the error…

Home Assistant 0.108.9

2

I also reinstall a fresh copy and right after login in HA, tried to login and had the same problem…

Home Assistant 0.108.9

3

I have the same problem…
Runnning hassio in Docker on a Ubuntu server
Home Assistant 0.108.9
Nothing in HA log
No problem in reaching htps://cloud.nabucasa.com from an other machine.

4

I found a workaround.

My Workaround was change TPLink Deco M5 from ROUTER to ACCESS POINT so, every device in my network is 192.168.0.x and DHCP is now controlled by Cable Modem. After doing that, Nabu Casa works pretty fine.

Explanation / More details:
I have a Cable Modem that is also a Router (net 192.168.0.x), then connected to it I have a WIFI Router TPLink Deco M5 net 192.168.68.x).
If I connect HA directly to the Cable Modem LAN port, Nabu Casa works like a charm.
Change back HA to TPLink and even configuring the Cable Modem to DMZ to TPLink, it didn’t work.
But could reach HA if open 8123 port and access directly via WAN IP, but this is not SECURE, so I disabled it.
Strange issue because TPLink Deco also has an APP that can connect from cloud without any configuration in Modem side but Nabu Casa can’t.

5

I’m with my fingers crossed to my workaround could help you, @bentcold

6

My problem isn’t quite the same, then
My HA server is ‘directly’ connected by ethernet cable to my router/NAT/firewall.
HA server is allowed to connect to the Internet. No forwarding from outside to inside.
Ping / TraceRoute to cloud.nabucasa.com from HA server works fine. (aside from the fact that cloud.nabucasa.com dont respond to pings)
But still the HA server is unable to connect to cloud.nabucasa.com. (“Unable to reach the Home Assistant cloud”

I am able to login to my account from any other computer (via a browser)

7

But what about your Modem, where is it connected? You only mentioned router/nat/firewall…

8

hi guys, I am having the same problem as

"After tying to login I get: Unable to reach the Home Assistant cloud.

Tried to Restarted Hass, restart RaspberryPi4, put cloud: in the configuration.yaml"

my HA has been working correctly for months, but again my SD card died (2nd SD Card died while running HA for 2 years :(, and I don’t have a fullbackup, so download the img on my PI4 and reinstalled the whole thing,

I haven’t changed anything around my network… so I would expect this is a HA problem more than a networking problem?
is there going to be a fix from HA for this?

9

Ater changing my ISP, I could connect to Nabucasa without problems. Now, after a SD failure, reinstalling HA even without restore anything…I still face “Unable to reach the Home Assistant cloud.”…

It was working for a month, and now, I cant make it connect again…I believe it is really an issue with Home Assistant or NabuCasa system…

10

@wilsonmanmcp, have you found anything else to make it work?

11

Having the same issue this morning. I think Nabu Casa may be having some kind of outage. I wish they had a service status on their support page.

1 Like
12

@Justin_Young @wilsonmanmcp @bentcold

I got it working again.

Just disabled my router and let ISP Gateway DHCP manage HA IP and then I could connect to Nabu Casa. After reenabling my router, it maintain Nabu Casa connected without issues.

***** This is the trick in my case…connect HA just once and before configuring Nabu Casa…afterwards, no problem, activating router with another network address. *****

I think there is some issue with TCP packets from HA to NABU that isn’t redirected when we have a network routed from a gateway…my ISP GW is 192.168.0.x and my router is 192.168.68.0 and all devices belongs to the same 192.168.68.x

1 Like
13

I know this is an old conversation, but I’m hoping for some help…

I’ve just had to start fresh with HA on a Rpi 4, my pi is connected directly to my Router but I can’t log in to my Nabucasa Account the above error is displayed ( uUnable to reach the Home Assistant cloud.)

can anyone offer any help?

14

This is still an ongoing issue. It is not a DNS issue or any other such thing.

15

Interesting that you and I are both reviewing this thread from nearly a year ago at the same time. I am also trying to diagnose this issue after purchasing a new router.

16

I do not have an answer yet but I can tell what it was not. I have an HA Blue (ODroid2). That uses Docker. I did a reimage with a version of HA ODroid 6 from a year ago but no change. I then setup a fresh install of OS on a Raspberry PI. Same network and that works fine so I do not believe this has anything to do with the network. I also set the DNS as all the other threads suggested. Sadly, I now have an HA Blue that is useless to me with this error.