Cannot bind port 1900 | Home Assistant | Page 1

pearl sedge Mar 13, 2025, 3:00 PM

#

Due to performance reasons I'm switching from HAOS in VirtualBox to running homeassistant directly in a Docker container. So far most is going good, but during one of the reboots I noticed that the container is unable to bind to port 1900 because it is already in use.

After some investigating it seems that the process that is binding to that port is com.docker.backend.exe, but only when the homeassistant container is running. It seems that somehow the container is trying to bind the same port twice? :S

The logs in homeassistant are not showing any issues, neither are the docker logs, but my autodiscovery (uPNP/SSDP) devices on the network are not (automagically) found. For example my Sonos: I can add the integration fine, but it won't do anything until the device itself was found by homeassistant.

Container image: homeassistant/home-assistant:latest (pulled today)
Network: system default 'host' network
Running Docker Desktop on Windows with WSL2 integration

hoary smelt Mar 13, 2025, 9:12 PM

#

Run ss -lntp | grep 1900.

pearl sedge Mar 14, 2025, 7:06 AM

#

ss is not a valid command within the Homeassistant image, and I'm running on Windows

#

#

Homeassistant itself seems to be binding to that port twice

hoary smelt Mar 14, 2025, 7:15 AM

#

What does it say if you stop the container?

pearl sedge Mar 14, 2025, 7:23 AM

#

It just stops the container, how do you mean?

#

https://www.home-assistant.io/installation/windows/
They do have guides on Windows installations as well.
Running VirtualBox causes big performance issues, especially if you assign more then 1 CPU, which is why I'm no longer using that.

https://www.home-assistant.io/installation/alternative#install-home-assistant-container
And there are installations for running a container on a Synology, but that should work on most systems

hoary smelt Mar 14, 2025, 8:19 AM

#

It should only cause issues if you don't have virtualization or windows itself is virtualized.
You could also use Hyper-V.

pearl sedge Mar 14, 2025, 8:20 AM

#

Windows itself is not virtualized and running on a NUC

#

I'll see if HyperV works any better, was trying a docker container inside a Debian WSL terminal now but that doesn't seem to be easy to do either

hoary smelt Mar 14, 2025, 8:22 AM

#

If you have WSL2/docker it likely is. See here: https://stackoverflow.com/a/35812945

Stack Overflow

How to disable Hyper-V in command line?

I'm trying to open VMware, it says that VMware player and Hyper-V are not compatible. I found it here, but it's not working using the command it offers.

I tried to see the help, found that there's /

#

For a production HA you likely want to use a proper virtualization software like Proxmox VE.

pearl sedge Mar 14, 2025, 8:26 AM

#

I'm fully new to Proxmox.
From their website I understand there is only a paid version?

hoary smelt Mar 14, 2025, 8:27 AM

#

No. It's free and open source.

#

I have linked a quick start guide for HA here: https://gist.github.com/Impact123/c23c36eafe1672ec056233e450a86ae2

pearl sedge Mar 14, 2025, 8:27 AM

#

Thanks

hoary smelt Mar 14, 2025, 8:37 AM

#

pearl sedge It just stops the container, how do you mean?

As in what does netstat say now.

pearl sedge Mar 14, 2025, 8:37 AM

#

On Windows it shows that port 1900 is not in use

hoary smelt Mar 14, 2025, 8:38 AM

#

Hmm.

#Cannot bind port 1900