#Is 37 223 x y the same as DuckDNS admin
1 messages · Page 1 of 1 (latest)
Well, given that HA listens on 8123, I'm not sure how any of those are going to work for you
You need to forward some port on your router to port 8123 on the HA IP
This of course assumes you only have a single modem/router box, and not more than one
sorry I typed wrongly
8123
are the opened port
I have the main router and then an access point connected via ethernet
Go to https://www.yougetsignal.com/tools/open-ports/ and enter port 8123 in the port box and test it
And how is HA connected?
ethernet to the main router
I'm not at home now, I will try ASAP
sorry for that... 🙏
It always surprises me how many people try to troubleshoot something they have no access to
I spend a lot of time and it's so frustrating for me, I use every second during the day even I'm not in home
There's a good guide on the forum that walks through almost everything you need to know/test
I agrre with you, we are not experts on that and probably we have not the mind set for that..
agree*
okay!
firstly I will test the 8123 port with the url and then I will read the guide
thanks for your time!
Finally I’m able to access HA through the Internet
Installing SSH addon ans running it
Now I’m have troubles using HA app
The certs are not valid (this is the error)
If you're doing SSL in HA then you can only use the hostname the certificate is for to connect
If your hostname is whale.example.org then you have to use that - you can't use the LAN IP or homeassistant.local
The solution is to use a proxy server for SSL (and remote access)
I know that it’s me the problem, I can access via web browser with https://blablabla.duckdns.org:8123 but when I try to set the external URL in HA app It’s shows me the certificate error
I don’t want to wear you out
I’m only sharing this with you
I will keep investigating
Well, it'll only show the certificate error if you enter something other than the name in the certificate - the port is irrelevantt