Container runs but no PORTS mapping

I’m running Home Assistant on an Intel NUC and all of a sudden (worked fine for 2 years) the UI is not loading (no connection). I’m stuck in a strange state where Home Assistant Core runs, but port 8123 is not exposed, so the UI is unreachable from my network.

Current Situation

  • NUC boots normally.
  • homeassistant container is running (docker ps shows it as “Up”).
  • However, the PORTS column is empty** (no 0.0.0.0:8123->8123/tcp).
  • As a result, the UI is not accessible via http://<NUC-IP>:8123.
  • Inside the container, HA appears to be running.

When I run:

docker exec homeassistant curl -v http://localhost:8123

I get a successful connection, so HA is listening internally.

But externally, the port is not published.

Anyone has a clue how to fix this?

You’d need to post the docker config

Are you another entso-e user? Another job is running for job group home_assistant_core / fails to start

HA recommends running the container in “host” networking (network_mode: host), in which case explicit port mapping is irrelevant.

Yes I am, thanks so much!

1 Like