Having installed HASS.IO and having tried logging in using KeenDNS service without any success, I have obtained a fixed external IP. I have forwarded port 8123 to HASS.IO to the host running HASS.IO and tried logging in over http.
Unfortunately, nothing changed. OK, there might be issues with reverse proxies that can be understood. Having a fixed IP, I cannot understand what I am doing wrong.
Could you please point me to fixed IP configuration manual?
I am sorry for inaccurate question. I have released KeenDNS and do not used anymore. I am trying logging in merely typing my fixed IP and port in a browser: http://AA.BB.CC.DD:8123. Port number 8123 has been forwarded to fixed IP in a local network.
I am interested in manual how to configure access through fixed IP’s.
Sorry for mess in my thoughts. Being newbie, your input would be appreciated.
Adding correct IP to base_url in http section has solved the problem. Thanks again.
Willing to secure connection, I have configured SSL via DuckDNS following the instruction posted here. After that HASS.IO stopped responding even in local network.
Nevertheless, HASS.IO can still be accessed through SSH.
Is there any way how to disable DuckDNS plugin through SSH or I will have to reinstall HASS.IO completely?
Finally, local and external connections work. I do really appreciate your help. Am I right that DuckDNS supports only one active session and an attempt to connect from two different locations at the same time will be rejected?
No. DuckDNS doesn’t have anything to do with number of connections.
DuckDNS is merely a dynamic DNS provider. It maps your dynamic public IP address to a hostname. The add-on in hassio also takes care of getting SSL certificates.
You can connect to your Home Assistant with as many devices as you desire.