Oh I know I broke something , I have been working on getting https and Duckdns working on my HA. I am using a Linux VM on a MacOS Host, I have HA OS 18,2. with Core 2026.8.3. I actually had it working for a half a day. Now When I boot HA comes up showing my 10.0.1.10. with 8888 port assigned. which is I intended. HA does NOT respond on this port but responds on 8123. Ok I figured why fight city hall. The HA I log on using that port is from. about a month back. . Some aps work some don’t HA reports I need about 14 repairs. and 9 updates. It only shows me two of the repairs. and two of the updates. which it won’t uodate . Oh and from time to time I lose connection which is automaticallluy restored. All the terminal apps are dead. I THINK I still have SMB but the password isn’t work (the fact I can’t see what I am typing makes me SO HAPPY for the absurd and useless piece of security). I figure a stiff drink go to bed and try SMP password in the morning. When tha fails. time to rebuild another VM,
Where did you assign this?
The configuration has moved from YAML to the UI.
Well I am now able to get into my “machine” via SMB. The version of configuration, yaml I have now on it has a HTTP in the VDI So the attached VDI is several months old.. Time to rebuild
I actually went though all the repairs and warnings and get my HA back on the the 8888 port with the current VM.Then with Duckdns back on line. I have external https access . Now I can gat back ti trying to fix z-wave That effort is what started this whole mss