Ethernal "Loading Data" accessing from Android browser or local network

Configuration
1

Hi,

Homeassistant 0.99.3 installed in a RB. SSL correctely configured on https://xxxx.duckdns.org:port.

I can access HA web interface from my desktop computer in my local wifi. I can access from my Android mobile by the use of 4G or from another wifi LAN. But I don’t know why, when I navigate to https://xxxx.duckdns.org:port from my Android mobile phone in my local Wifi, afer authentication, the browsers stalls in an eternal “Loading Data” message.

What can I do or check?

2

I update my thread with some information.

It seems as a problem with DNS resolution.

My desktop computer works properly because it resolves domain name as the local ip (192.168.x.x) of the homeassistant server.

On the other hand, on the mobile phone, when I connect to hass server by wifi using the domain name, it resolves domain name with my own WAN IP (router IP). In network information, I can see that /default_view has “pending” state forever and the page is in eternal “Loading Data”

However, If I use the local IP of the hass server from my mobile, it works properly. The problem is SSL certificate isn’t valid for plain IP addresses.

3

hass problem NAT reflection problem

After a lot of testing I have been able to fix this problem. It’s a NAT Hairpinning or NAT reflection problem (Network address translation - Wikipedia)

If you want to use public domain name inside your local network, your router must support NAT reflection. If your router doesn’t, when you browse to https://mydomain.name.org:1234 from inside your local network, the connection fails because the client try to connect to the hass server by the use of the public IP. Then, the router redirect the query to the HASS server and the conecction is a mess.

There are three options if your router doesn’t support NAT reflection:

  1. Use IP (for example https://192.168.1.123:1234) and accept the advise in your web browser. In this case your connection won’t be private inside your local network. If you can deal with it, go ahead!
  2. In your local DNS server (probably your router), assign the local IP HASS server to your public domain name. For example:
Host name = mydomain.name.org --> IP address = 192.168.1.123
  1. In your host file (Linux /etc/hosts o Windows <) add a line to resolve mydomain.name.org to 192.168.1.123
192.168.1.123  mydomain.name.org