#Cannot connect to cloud remote routing issue

1 messages · Page 1 of 1 (latest)

grand quartz
#

Hi, I think there is a routing problem to one of the Nabu Casa SniTun servers from Indonesia.

My Home Assistant Cloud Remote suddenly stopped working.

Environment:

  • Location: Indonesia
  • ISP: MyRepublic
  • Home Assistant: HA OS 2025.12.2
  • Nabu Casa region: ap-southeast-1-2.ui.nabu.casa

Cloud status in HA:

  • logged_in: True
  • can_reach_cloud: ok
  • remote_enabled: True
  • remote_connected: False
  • remote_server: ap-southeast-1-2.ui.nabu.casa

Log error spammed every few seconds:

Can't connect to SniTun server ap-southeast-1-2.ui.nabu.casa:443 with: [Errno 113] Connect call failed ('137.184.248.28', 443)

From a Windows PC on the same LAN:

Ping:

ping 137.184.248.28

Result:
Reply from 119.110.114.22: TTL expired in transit (0% packet loss, but never reaches 137.184.248.28).

curl test:

curl -I https://ap-southeast-1-2.ui.nabu.casa/

Result:
curl: (28) Failed to connect to ap-southeast-1-2.ui.nabu.casa port 443: Could not connect to server

Traceroute:

tracert 137.184.248.28

Output (shortened):

1 192.168.1.1
2 192.168.2.1
3 host-93-129-104-129.myrepublic.co.id [103.129.93.129]
4 172.16.19.49
5 * * * Request timed out.
6 119.110.126.24
7 119.110.114.25
8 119.110.114.22
9 119.110.114.22
10 119.110.114.21
11 119.110.114.21
12 119.110.114.22
13 119.110.114.22
14 119.110.114.21
15 119.110.114.22
(then continues looping between those 119.110.x.x hops)

So the traffic seems to loop inside my ISP’s network and never reaches 137.184.248.28:443.

I also tested from a mobile data connection (different ISP) and I still cannot reach:
https://ap-southeast-1-2.ui.nabu.casa/ (browser and curl both time out).

Questions:

  • Is there a known issue with the SniTun node at ap-southeast-1-2.ui.nabu.casa (137.184.248.28)?

I can provide my support package if needed. Thanks!

barren fog
#

It would be expected to time out at the final hops. On the mobile data do you get the same loops?

grand quartz
# barren fog It would be expected to time out at the final hops. On the mobile data do you ge...

from Android (Termux, Wi-Fi OFF, pure mobile data):

$ ping -c 4 137.184.248.28
--> 4 packets transmitted, 0 received, 100% packet loss

$ traceroute -n 137.184.248.28
1 * * *
2 * * *
3 * * *
4 * * *
5 36.95.255.93 45.579 ms 61.94.4.121 44.992 ms
6–30 * * *

$ curl -I --max-time 20 https://ap-southeast-1-2.ui.nabu.casa/
--> times out / cannot connect

So from a completely different ISP (mobile network) the IP 137.184.248.28 / ap-southeast-1-2.ui.nabu.casa is also unreachable (ping loses 100%, traceroute stops after a few hops, curl can’t connect).

barren fog
#

Ping will fail, as tracert. The infrastructure won't respond to pings unless that is made available. So these aren't going to be good tests.

How long has it been for you @grand quartz ?

#

I know you have a ticket in, and now there's the other thread here that you joined. Just coming back here because you were first 😅

#

It could be that certain countries will need to be moved back if the ISP does not eventually deal with the new endpoint

grand quartz