Cannot connect to Home Assistant Remotely

[humble pond]

Another threads of Home Assistant Cloud suddenly stopped working. My Home Assistant Cloud (Nabu Casa) status shows Connected, but I’m unable to access my instance remotely.

Environment:
Version core-2025.12.2
Installation type Home Assistant OS
Development false
Supervisor true
Docker true
Container architecture amd64
User root
Virtual environment false
Python version 3.13.9
Operating system family Linux
Operating system version 6.12.51-haos
CPU architecture x86_64

Home Assistant Cloud
Logged In true
Relayer connected true
Relayer region ap-southeast-1
Remote enabled true
Remote connected true
Alexa enabled true
Google enabled true
cloud_ice_servers_enabled true
Remote server ap-southeast-1-0.ui.nabu.casa
Certificate status ready
Instance ID
Reach certificate server ok
Reach authentication server ok
Reach Home Assistant Cloud ok

• Local access within LAN works fine
• Nabu Casa shows Connected
• Remote access fails both via Companion App and when accessing the ui.nabu.casa URL from outside the LAN

Has anyone encountered this before or knows what could cause Cloud to appear connected but still be unreachable? Any help or guidance would be much appreciated.

[hidden lake]

can you check your internal network, e.g. dns server(s) and NTP (time) is running fine? test if you can ping google.com in cli.

[humble pond]

yep it is fine in the terminal within HA

[hidden lake]

Set a static ip lease/reservation for haos in your router and set haos to ipv4/6 automatic. Then reboot and check again from chrome/edge browser on pc using http://yourlocalipaddresshere:8123

haos= home assistant os

[humble pond]

have tried so, my HA is accessible through http://yourlocalipaddresshere:8123/ just not remotely

[hidden lake]

ok, are you using any special dns servers or add blocking software?

same LAN (no vlan...)

[humble pond]

nope. No DNS changes or ad-blockers on either the server or router.

[hidden lake]

try to log out of nabu casa, reboot and wait a minute and log back in to nabu casa

if this does not work, delete your tokens and reset your companion app

i am off for a bit, will be back later. Other users might hop in and continue 😉

[humble pond]

no luck there, and I don't think it's token issue as I've tried accessing remotely through the browser from my phone as well

[humble pond]

thanks for the support, appreciate it

[hidden lake]

np, have to go shopping with my wife, woohooh.. last thing for now, check https://my.home-assistant.io/redirect/people/ user setting if remote access is allowed

[sturdy jolt]

I am having this exact issue too. No luck so far with customer service email. I thinks its nabu issue on this southeast 1 node

[humble pond]

same thought here, seem likely to be an issue on the nabu casa side

[crude osprey]

also ap-southeast?

If so, any ISPs in common here?

[humble pond]

yep, but it's all good now

[crude osprey]

oh? did you have to do anything in particular?

[humble pond]

nope, I just let it be so I suppose it's the node having issues

was not able to connect to my HA remotely for almost 8 hours

[crude osprey]

the node was migrated from AWS to Digital Ocean, so I suspect it is an ISP issue with routing. A large number was migrated and seemingly ok.

Is Indonesia a commonality here?

@sturdy jolt?

[sturdy jolt]

Mine still dark. Indonesia, ISP MyRepubic and Telkomsel (4G) fails. Where are you located @humble pond ? What ISP are you on? So I'll just wait then..

[humble pond]

Malaysia