I’m new here and to home assistant. I have a fresh hassio install runing in virtualbox on an ubuntu machine. I have difficulties getting remote access over https to work using the duckdns add-on. I did the following:
Router:
Forward rule:
Outside: port 8123
Type: TCP
Inside: port 8123 to ip of hassio server.
Duckdnd website
Create an free account. Add a domain name: xxxx.duckdns.org
The http: you see there is the name of the integration in Home Assistant, like you also have lights, media players etc.
This can be confusing and make you think this might need to be https, but that is not the case. It is underneath this http integration that you configure it by for example setting up ssl_certificate and ssl_key
i’m about to give up on all of this. i have been trying to get the remote access to HA in order to get HA geofencing to work and to be controlled from my android app
In duckdns addon have the following:
lets_encrypt:
accept_terms: true
certfile: /ssl/fullchain.pem
keyfile: /ssl/privkey.pem
token: 246*************************************
domains:
and if i insert the same url in my remote connection on my phone it always get an error asking me to review the settings.
The remarked out lines in my config.yaml are there because i was trying to install nginx to no avail
Am doing something incorrectly?
Is the an alternative to duckdns? (i was hopping to give access to my network to my daughter who lives abroad)
furthermore in my automation to leave home the automation should be notifying me on my android phone. If i run the scene in house it works however when i leave i get no notifications.
could this be caused by the same issue? .
PS. I do not know why the IP address here above is in different caps