New setup issue: homeassistant.local:8123

@madmycal Actually this

image

test and then give me the output of

route print -4

Well - waiting on some responses from you. Have you tried as suggested from @_dev_null

Probably won’t hear from him, it’s the little thanks that us hard working people put in for free that would be appreciated rather than just bullying and steam rolling the community for support that isn’t really homeassistant related

Like me you probably have a stressful high paying day job and family to run or busy lifestyle, yet find some time to help contribute here

With a smile, lets move on :sparkling_heart:

1 Like

Yeah, I think the network was wrong. It is a single IP address entry and it is set with a range of /24 at the end. The IPv6 has a /64 on the end of it’s normally single IP address.
EDIT:
Well I just checked mine and it has those /24 and /64 added on the end now. A update must of made a change to how the network is setup. Wasn’t like that a few months ago.

So I’m back to my theory about it being a browser issue with forced https: versus http: settings that have to be over-ridden. MS just made a change with that it’s called “Auto-HTTPS” what a pain to find that setting. It is well hidden now by MS

As the address bar shows in FF it has https in it, so it needs to http:

those /24 and /64 is a different way to write the netmask ie 255.255.255.0

Sorry guys, my new user account had a excruciating 20 hour pause on posts yesterday… I really appreciate the effort in trying to get me online!


My home network is very basic right now… The windows machine with Virtual Box/Home Assistant is connected directly to a Verizon router. Verizon router does see “homeassistant” and the IP/mac addresses do match up. Those addresses are different from the Windows machine-which I assume is okay in this situation?

I can still reach the Home Assistant observer directly from the windows machine and from different computers hardwired and via wifi.


Rebooting: I have rebooted the HA VM several times in between changes and nothing… The windows box hosting the VM has been rebooted at least two times as well. For shits and giggles I also rebooted the router and same issue is present.

Maybe I should reboot the windows box a third time? Reminds me of this oldie :expressionless::gun:

http://www.thewebsiteisdown.com/salesguy.html


Next Step:

route print -4

Hmmm, thats odd?


After running the route print command and seeing some strange IP’s I uninstalled and completely removed the VPN from the Windows box. Route print again after removal:

Screenshot 2024-01-20 154414

I do see a strange IP destination (127.255.255.255) on that list… Also, no idea what the 192.168.1.255 is either. No traces of this on the router, and its not pingable. That last route print was after running ipconfig release/renew.

I rebooted the VM and Windows box in hopes that may have been the problem all along (VPN was previously disabled, not fully uninstalled) and still no dice, I don’t think this is a VPN issue.

Using Mozilla FF as requested (previously tested using http on that first tab):

http

https
Screenshot 2024-01-20 155434

Again, I appreciate all your efforts here!

I have an old Raspberry Pi Model B laying around… I know its a bit below the HA recommended specs, but would it be worth tossing out this Virtual Box install?

Can you open the settings on FF then go to Privacy/Security and scroll down to the bottom to: HTTPS-Only Mode I have “Don’t enable HTTPS-Only Mode”

Looks like the same settings as you.

Okay we eliminated that as a possible cause for FF.

Now studying the Network settings returned by “route print -4”

You: I do see a strange IP destination (127.255.255.255) on that list…

My reply: That is the broadcast IP for the localhost/loopback on the machine/card. Normal

See: 127.255.255.255 - Loopback Address | IP Address Information Lookup

You: Also, no idea what the 192.168.1.255 is either.

My reply: That is the broadcast address for the LAN subnet. Normal

From You: Now I’m looking at the 224.0.0.0 that is tied to the 127.0.0.1, I’ve not come across that. I have to look that one up.

That is multicast IP broadcast to the local host:

That is needed by IoT devices to lookup devices and link up and hand off to regular IP traffic.

1 Like

Did you by chance setup external/remote (coming from the web to inside your network) access for the HA at the same time?

Also check on your main router if you have device isolation turned on/enabled if it is please turn it off/disable

That is a negative… This is a fresh copy of Windows 11 (days old) and besides the VPN that was just uninstalled nothing else network related has been touched.

I did just perform and entire “network reset” on the windows box. This uninstalled all the adapters, reinstalled, etc… Rebooted the VM and can get to observer but not the HA login URL.

I just scanned through all the Verizon router settings and don’t see an option for anything related to device isolation.

I feel like I’m going crazy here… This shouldn’t be rocket science, what the hell am I missing? I have another router and may try connecting the Windows box to that to see if its the Verizon router or a setting therein causing this issue.

Can you give the model/model# of the Verizon router?

Verizon G3100

Firmware version: 3.2.0.15
Hardware version: 1104

thank you!

1 Like

So when you return, login into your router. Find the host and HA device. Expand it to see all settings. Screen cap and paste into your response. Thanks

As requested:

homeassistant:


Windows machine:


I have to hop offline for a bit, will be back on later tonight!

The HA is recommended to be a static IP. It is recommended to be a hardwired connection. These are set to DHCP and you have portable under mobility on your Verizon router. Having it mobile and maybe on a laptop that moves around could be a issue. I could only find reference to a Windows11 and running a VM with VirtualBox.

More clarity would be helpful.

The Windows box (Dell T7400) is hardwired (see below).

I set both the Windows box and Home Assistant VM in the router as “stationary.” I’ll work on setting static IP’s for the Windows 11 box and homeassisant VM tomorrow morning. Keep you posted with results!

Screenshot 2024-01-20 213839

Windows box static IP set:

Screenshot 2024-01-21 144810


With that said, I’m having trouble setting static IP on the HA VM.

When I get to the CLI main screen, and attempt:

  1. Run ‘login’
  2. Run ‘nmcli connection show’

I see the following:

Does that look right? From my research others are showing different connections.

If I try to set the IP I get the following:

image