I’m trying to set up Home Assistant on my mini PC running Windows 11. I followed the installation steps and everything seems to work fine within the VirtualBox Linux machine (set to minimum requirements for Home Assistant). However, whenever I try to access the Home Assistant dashboard at http://192.168.x.x:8123 (replace x.x with your IP address) my entire PC crashes and requires a restart.
I initially thought it might be a RAM issue, but I’ve adjusted various settings with no change. Has anyone else encountered this problem? Any advice would be greatly appreciated.
It seems that the device that you use to open the HA dashboard has an issue, not your HA, right?
Don’t you have another system to access your HA, or did you try another browser?
ps: you don’t have to mask your PRIVATE/LAN IP addresses; most of the users here have their network configured that way/with that IP range.
If your concerned about security, do not post you WAN IP.
Just to be clear, your server where HA is installed crashes or your PC (or laptop) with which you call the HA webpage (http://IP:8123) crashes? Or do you use the HA server as “desktop” as well, meaning you call the HA webpage on the same machine where HA server is installed?
The problem is from the device that hosts HA. For example I tried to host it with the same settings but on my main PC and it works perfectly.
When I do it on my mini pc, the pc crashes completely and I have to restart the pc and eventually the HA server.
FWIW, I ran my production and development copies of Home Assistant for over 2 years in exactly this way (Windows/Virtualbox) and never ran into problems or limitations that would justify calling it “the worst way”.
I guess you know very well that by using a desktop version of Windows, especially if you just use it to install a desktop virtualization software to run a server is not the best option. (and in my opinion one of the worst)
At first, you just waste resources and depending on your knowledge, your server might go down with every Windows update.
Of course, there are ways to prevent that, but still if someone thinks he/she has to hide a LAN IP would you still advise to go that route?!
On top of that: the issue that OP has, how would you advise to solve this, with Windows & VirtualBox in the game?
No, I agree on the IP masking discussion. I find many people on this forum take on complex setups they don’t seem to understand. Every person has to decide on their own if something is beyond their knowledge and experiences.
As to why this scenario crashes the PC, I couldn’t begin to speculate with the information provided. Makes me appreciate the job of a veterinarian.
+1 on what @francisp says but of course that’s because I know the capabilities of Proxmox since I use it for some years now and with 16Gb RAM (if that’s the config that you bought) what will you do with that much, only for HA.
With Proxmox you get an easy way to install extra services (virtual servers).
Now, with Windows, you waste already a few Gb’s on Windows itself and then on VirtualBox.
Also, performance wise, this is not ideal.
TBC: on my desktop & laptop, I use Windows myself, and this is for MANY years, so I have nothing against it!
Home Assistant crashes on my mini PC, but works perfectly on my main PC. Any ideas why? I’d prefer to fix it on the mini PC rather than installing Proxmox.
