I can't access HA locally

Installation
1

I know that this topic has been said prior but my situation is a bit different. I’m going through the process to create a duck.dns URL so I can connect HA to Alexa. after going through all the steps I can gain access to my HA on my phone off of my local network but when I use my wifi which HA is connected to I no longer have access. I’m thinking its because of the port forwarding. I’ve set up my router to port forward both 8123 and 443. When I check, 8123 is open but 443 is still closed no matter what I do.

2

Is it? :wink:

Update your local bookmarks to use https

You will also have to add a security exception to your web browser when accessing the local ip address or mdns url as the SSL certificate is only valid for your your DuckDNS domain. You will be given a warning page that you can do this through the first time you try to access the local https address.

The port forwarding is only for external access, has nothing to do with local access.

For security reasons you should ensure you are only forwarding the minimum number of ports required for this. The less ports you have open the better. So only one of:

internal to external ports

8123 to 8123 (requires :8123 at the end of your DuckDNS URL)

OR

8123 to 443 (no port required at end of your DuckDNS URL, 443 is the default https port)

1 Like
3

I have been using HTTPS… The HA login page pulls up but it just wont connect.

4

Are you using the ip address or mdns (e.g. homeassistant.local)?

Which web browser are you using?

5

I’m using chrome. Which worked before. And I’m using my new duck.dns domain name.

6

Hi, welcome to the forum!

What happens if you try to connect from your local network, not with your mobile and/or the companion app?
Try it with a pc and use as address: http://‘IP-address of your HA’:8123
Also, by not adding the protocol in front of the address, your browser might use httpS (depends on configuration)

8

I’ve tried that as well… the IP address no longer work because of the new duck.dns domain name. I’ve used both https and http. No Bueno

9

I also think it has something to do with my port forwarding. I was told to make sure the port 8123 and port 443 is forwarded in NAT/Gaming. after completing that process 8123 is open but 443 is closed. No matter what I do.

10

AFAIK you should be able to connect locally (on your network) wit the IP address of your HA over http.
That has nothing to do with port forwarding.