I’m not sure that it has something to do with the dns but who knows, some settings in HA also need an active internet connection to be saved so i won’t be surprised 
How would he be able to access 31.30.90.11 from ha ?, it’s a public NS
It works anyway, only if HA’s internet access is blocked it won’t work. This setting won’t affect direct access via HA’s ip but like i said, he should try it
I still dont fully understand how did my ISPs DNS ended up in the settings of HA. I dont recall messing with them.
It is called DHCP 
If you didn’t change settings on the router it could be that the router gave out this settings via dhcp
True, but his settings are wrong anyway, as he has removed DuckDns, and run HA entirely local, who know his Mdsn has his external ip pointed to HA, so it’s better to make sure all settings are default “again” , Mdns should be flushed after
EDIT: the ISP should only provide dns on the wan-connection not lan, the Router should fix this
Is there a option to install and configure NGINX via CLI?
type net reload
Maybe because your network settings are set via dhcp and not static. Don’t know if you are able to change these settings then, i’m not sure.
My router shouldn’t give my modems is DNS to home assistant. Makes no sense to me.
Nothing changed after this
edit: I am still not convinced that DNS is the culprit, since I cant even connect to the IP directly, while I am able to ping the IP and, what is interesting, open the supervisor page on the port 4357
I know it shows the port 8123 at ur startpost, but did you ever changed the port in yaml?
check your router, and make sure this doesn’t come from your dhcp settings, no matter how they got there , should point to your Routers ip
There is absolutely no point in having an external DNS, to resolve local-addresses ( doesn’t work ) , and if you have try to access from windows, open console and type " ipconfig /flushdns "
i know you “should” be able to access through ip-number, but better to have proper default setting , AND also make sure you use http not https
As i don’t know what setting DuckDns does i can’t help you there … i assume/hope it reverts all settings, when you removed it
I have only my routers internal ipnumber as dns, and rely on my ISP route external traffic properly ( have to go through them one way or another anyway, (even if i hardcode an external DNS somewhere)
if this address is used, there is no dns involved (hence, dns cannot be an issue)
Why not make a backup and secure it somewhere re-image the drive, and restore the backup?
If that results in the same situation, it is probably one of the addons causing it, so restore the backup step by step 
try to check whether you still have ssl enabled in HA )as it started after you removed DuckDns(for external access) you might have enabled ssl then (when you tried to install/configured it)
" ha core inf "
1 Like
!!! SSL is still on. how do I disable it then?
try
core options
core info
if not
then …
core options --ssl
core options
core info
PS: Do you remember whether you added SSL (i.e in configuration.yaml) when you fiddled with DuckDns ?
PS:2 Remember to type
core restart
before you test if you can access now ( after you cleared your browser cache for everything ! ) 
1 Like
i added http: to config, based on your suggestion i logged into console and edited the config (deleted all the ssl stuff)
It still showed ssl: true in the ha core info.
So I asked chat gpt for advice, and it nudged me to try ha core check. it took a while and then when i tried core info, it showed SSL: False
then i restarted my router and voiala! I am in. Thank you so much for help, it was 2 months I couldnt solve this.
2 Likes