Go back to your installation documentation. Was a vital step missed, was there a bug when you were creating certificates, or is the web page actually supposed to be http, and not https? I donāt recall any mention of reducing or altering web browser security to access HomeAssistant in any documentation I have seen.
Do you have other network products such as DDNS, VLAN, VPN, etc installed? Have they been configured too?
What is the local network address for your laptop? (192.168.?.? - yes it is OK to post the full LOCAL address as explained earlier) The web browser IP Address you are attempting to access HomeAssistant from? The IP address of the VM? Has routing been configured for these?
Laptop IP:103.224.x.x (This is a Public IP from my ISP, Superloop/Origin).
VM IP:192.168.68.114 (This is a Private IP from my TP-Link Deco mesh system).
The Problem: It appears my laptop and my VirtualBox VM are on completely different subnets. My laptop is sitting on the public internet, while the VM has joined the local Deco network.
Certificates/HTTPS: I have confirmed I am not using any certificates. This is a fresh HAOS install. I am trying to access via http, but the connection is failing because of this network mismatch.
VPN: Confirmed disabled.
My Question: How can I get VirtualBox (or my laptop) to put both machines on the same 192.168.68.x subnet so the browser can finally see the Home Assistant dashboard?
Your laptop does not have a public IP. (Or if it does you have real problems)
Your router will have a WAN with a public IP. It will translate that to a 168.192.x.x or a 10.x.x.x subnet.
Network Setup: My home uses TP-Link Deco pods for Wi-Fi. My internet provider is Superloop/Origin.
The IP Mystery: I confirmed my laptopās IP using ipconfig, and it is indeed showing 103.224.x.x. My VirtualBox VM is somehow getting 192.168.68.114 from the Deco system.
Connection Detail: My laptop is currently connected via Wifi
It seems my laptop is bypassing the Deco router entirely while the VM is successfully finding it. How can I force my laptop to get a 192.168.68.x address like the VM?
Check your Router Settings, as people also trying to tell you.
Most home-network uses local-network, for additional security reasons, Some Routers can provide passthrough for internal devices if the Provider/Subscription provides more than 1 Xternal IPās ( Such service is mostly used for high traffic, high-end Devices, via ethernet )
So you have to remove this in Your Router, yo have absolutely no reason for this āFeature/Serviceā
Your Router should act as a gateway, for ALL your device in your Home-Network
So Start with your MainRouter, check this Wan-IP, if it differs from your laptop, it means your IP-Provider offer you more than 1 IP, in your subscription)
Most likely have you āpoked aroundā in your Router, and enabled something you thought sounded āCoolā , I sincerely doubt any Brands would have Such Feature enabled by Default, so most likely a Factory-Reset of your Router will fix this for you
( That is if you canāt figure out another reason why your Laptop have a Public IP, and where this IP comes from )
I thought of that to, but he insist his laptop is on Wifi, so somehow he should have an IP for that to then ⦠on the other hand we still havenāt seen any āfactsā, in regards to where he get his āinfoā from
EDIT: Could also be so, that his Deco-wifi-network, is not the same as his Wan-Router
You direct the device issuing an IP address on connection pairing request to give it one in the appropriate range by specifically configuring it to do so, usually by MAC address identification. In your case, it will be when the laptop connects to the WiFi SSID on the TP-Link. This is where DHCP and Static IP addressing becomes important, and you have to plan and understand what you are doing.
Dedicated IPv4 addresses are as rare as unicorn droppings - the world has basically run out of them and devised NAT strategies as a workaround until IPv6 addressing becomes popular. I strongly suspect that there may be some misunderstanding, however I read that there is a possibility of static external IPv4 address being allocated and I suspect they may not be cheap or easy to obtain. See IP Address Policy ā Help Centre - Superloop Smart Communities, and I quote āIn some locations, Superloop offers static directly accessible IPv4 public addressing.ā from there (my bold).
I also note the IPv4 address range you quote (103.224.x.x) appears to be allocated to Superloop. Iām wondering what sort of network equipment/router/switch you are connected to, to bring you internet connection from the outside world. For some reading here, the idea of a world without DuckDNS and the suchlike shenanigans must be strange, an utopia. IPv6 offers enough addresses for pretty much every molecule in the inverse to have an unique address.
I see some detailed network routing research and reading in your immediate future, combined with planning and reconfiguration. Your goal is to get the data packets from one subnet to the others so the logical devices can talk to each other. Research DHCP and routing tables configuration on your networking equipment also.