Ok, your problem is probably something wrong with your HTTP configuration in HA, or the port forwarding on your router. You can look through these forums to find help, but I’ll provide a bit of background for you and anyone else who might run into similar problems.
First, did you add this to your configuration.yaml and restart HA?
If so, HA will now be using HTTPS (instead of HTTP) on port 8123.
Then, you need to use port forwarding on your router to map whatever external address:port you want to the private internal HA address:port.
For example, this would map port 12345 (number selected for no particular reason) on an external IP of 126.96.36.199 (just an example) to a private internal HA IP address located at 192.168.0.8 (again, just an example):
- 188.8.131.52:12345 → 192.168.0.8:8123
Following that, and assuming that
my-hostname.my-godaddy-domain.com is your domain name, then this URL would be able to access your HA from the Internet:
If you used 443 (the default port for HTTPS) instead of 12345 for your external port, then this URL would also work (but only if your router or something else doesn’t block or use 443):
If you try to access this URL from inside your private network, your router’s port forwarding may not support hairpinning (aka NAT loopback or NAT reflection), especially if it is older, and so you might only be able to access HA from the external Internet. If that’s your problem, then I’d suggest leaving HA with HTTP for internal private network access (by removing the
http section from
configuration.yaml), and using the NGINX Home Assistant SSL proxy add-on to provide HTTPS for external Internet access to HA. But, that’s beyond the scope of what I’m going to get into here.