Are you suggesting a roll back of supervisor? IF so, how?
what does it say if you type âsupervisor logsâ into the cli?
Yes seems like itâs 2023.6.1 but there are a newer 6.3 , thats why i suggested earlier to do âcore updateâ as i recall there was recently some âconnectionâ issues with initiall release ( for some people )
You can search the Forum for this(itâs in the past month)
But as mention, disable your NB account ! and all local settings you have done related to this, you donât have NB installed/enabled in your HA, so this could mess it up for you
It always says so, but the following shows itâs up and running fine, so itâs nothing to be concern about
i forgot on the monitor it will continue to say that! from terminal it doesntâŚ
either way, supervisor logs and core logs would be good for troubleshooting.
true, but we can most likely only get a screenshot of last 30rows or so, but always good with âmore infoâ
Notice the IP address is different, itâs 172.30.32.1 with the port being 8123
i wonder if its a similar issue to this one
thatâs probably the docker address, not the ipV4
1 Like
seeing something interestingâŚnot sure if it helps but after clearing web browser cache, every time I enter http://192.168.1.174:8123 the browser says cannot connect with www.192.168.1.174:8123. Canât get rid of the www except if I use https:// which is not going to help.
Can you show; how you set your VM container to the external host interface (network)?
That is IPv4 addressing and I doubled checked that is the internal VM container IP address. Off to double check how that is to be tied to the external host network settings.
clearly you previously said that ha had changed to192.168.1.176:8123, are you saying it has change again ?
You canât have a âServerâ that change IP-number after each reboot/reinstall !, fix it in your Router, as i mentioned, ⌠it should always have the same IP, as i.e mDNS builds up a list, and if im not wrong NC also needs to knows which internal IPv4 HA is running on etc.
Also i wonder, are you running HA on a machine over WIFI ?
Im not sure what you are talking about, but if you use homeassistant in VM, im sure youâll know and can see that his screenshot of âcore infoâ is perfectly correct, and this means he should not care about the 172⌠IP-number, itâs HA internal, set by HA, and nothing he(anyone) should tamper with.
PS: you said you double-checked ?, does that mean you ran ânetwork infoâ and âcore infoâ in your setup ?
in that case im curious what âinstallationâ you have, and how you came to the conclusion that he should tie a 172. number to
Scott, these are a few things you can do:
- Reserve an IP address in your (modem-)router since it seems youâre using DHCP and your HA is using different IP adresses all the time
- Try another browser or device, AFTER you are sure what the correct IP address is from your HA
I donât know how safari handles http vs https URLâs: I know there are settings for this behavior in FF.
Are you using add-ons/integrations, if so: which ones?
okâŚset the static ip to 192.168.1.99. Confirmed in VM window as ip address. http://192.168.1.99:4357 shows observer ALL GOOD, but every browser I have changes http://192.168.1.99:8123 to www.192.168.1.99:8123. In addition homeassistant.local:8123 can not be reached by safari or chrome.
Also have you disabled IPv6 , in your router, and HA , as i mentioned earlier ?( ânetwork infoâ screenshot )
And do you run your HA over WIFI ?
And did you download the latest VM-image ( or is it âbackupâ of previous ha-installation, with potential âbadâ settings ?),
NEW download so there is a chance you get core 2023.6.3, and latest supervisor/fronted ?
Other than that would it be âimportantâ to know if you have done other Router-settings, and firewall setting in your Router. and/or use any DDNS ?
(and make sure your windows-firewall allow ALL ports LOCALLY, or make sure âtemporaryâ to disable the firewall)