Admitted - I am new to home automation - and thus hass_io… and to networking…so bear with me.
I got “hass_io” running on a Raspberry Pi. It seems to work.
I have a main router (where my internet comes in the house) and set up an access point on that for the other end of the house, so I have full wifi coverage on same SSID. It works nicely. The Raspberry Pi is closest to the access point, so it is on this I guess.
On my router, I assigned a fixed IP for the hass_io/Pi - “192.168.0.20”. This works well. It stays on that IP.
On my router, I set up port forwarding. It looks like this:
Now - I would expect that I could get to the hassio by accessing my public IP with “:8123” appended. But I get nothing. I tried just entering the public IP +:8123 in my cell phone browser (while on 4g only). I also tried the android app “Home Assist” - no luck.
Actually, the public IP confuses me. If I use whatismyip_com, it gives me an adress that is 85.xxx.xxx.xx (x’s to anonymize). But the WAN info on my router has a 100.xx.xxx.xxx IP on it - with a default gateway also starting with 100.xx
I did not set up DuckDNS yet. Nor Let’s encrypt - but that is obviously next, once I can get in.
I read somewhere that “double NAT” could be an issue, but I took the steps to verify that I do not have double NAT issue (I did a tracert to 8.8.8.8, only first hop was internal IP (of my router).
Ideas?
Do I need to open up 8123 port on my router - and if so - how to? I am lost…
Any help is appreciated - greetings from a home automation noob in Denmark.
Thanks @Bobby_Nobble - but I still fail to see the solution.
My configuration.yaml has this on http:
http:
api_password: !secret http_password
And I have set the http password in the secrets.yaml. When accessing locally (192.168.x:xx:8123) no problem. I get prompted for password. From mobile on internal wifi also.
base_url (Optional): The URL that Home Assistant is available on the internet. For example: hass-example.duckdns.org:8123. Defaults to the local IP address. The iOS app finds local installations, if you have an outside URL use this so that you can auto-fill when discovered in the app.
An easy way to find your external IP address is to type “whatsmyip” (without the quotes) into your web browser. If your default search engine is Google it will return your external IP address
www.whatsmyip.org will return your external Ip address, Host Name and a bunch of other info.
Could be behind carrier grade NAT - will investigate
Tracert looks like this:
1 3 ms 1 ms 1 ms 192.168.0.1
2 28 ms 6 ms 13 ms 100.91.208.1
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 4 ms 4 ms 4 ms 10.236.20.18
7 4 ms 4 ms 4 ms 37.75.160.1
8 5 ms 4 ms 4 ms 87.116.38.121
9 18 ms 16 ms 16 ms 93.176.93.8
10 17 ms 17 ms 17 ms 77.233.230.165
11 * * * Request timed out.
12 25 ms 19 ms 17 ms 216.239.63.245
13 16 ms 17 ms 16 ms google-public-dns-a.google.com [8.8.8.8]
The second line corresponds with the “Default Gateway” I can see in my router setup.
if I understand you correctly - omitting this part, would default to the local ip. So I have to put in my public IP (explicitly or via for example duckdns). Thanks. As others have pointed out, I probably (also) have an issue with my ISP doing NAT.
@Elway Did’it work out for you ? I think I have the same issiue? A very strange thing happend to my router, it somehow did a factory reset on it’s own??? Everything worked just fine before the reset. I could connect it from the outside (dickdns) and now after the reset just to locally 192.168.x.xxx:8123. I have port forward WAN 8123 to LAN 8123 192.168.xxx.x. Is there any other router settings I missed? When I look up "whats my ip I also got 2 different IPV4: 109.203.xx.x and My router says WAN IP: 107.127.xxx.xx. Can’t access niether when I try xxx.xxx.xxx.xx:8123. Duckdns says same IP as (whats my ip) 109.203.xxx.xx .
Another strange thing is My Google Calander component still works and is connected to internet???
Quote from the link…