Solved - HassIO suddenly gives Connection Refused

Installation Home Assistant OS
1

I have HassIO installed on an Ubuntu 17.10 VM with Docker.

It’s been running fine for months and I haven’t changed anything recently. I am currently on .87.1 was going to upgrade. Logged onto run the configuration validator and none of my add-ons were working. They’d throw a brief error when trying to start that I couldn’t really see before it disappeared.

I rebooted the whole VM and the Hassio containers start:

root@hassio:/usr/share/hassio/homeassistant# docker ps
CONTAINER ID        IMAGE                                    COMMAND                  CREATED             STATUS              PORTS                    NAMES
5bc336d549ad        hassioaddons/ide-amd64                   "/init"                  4 minutes ago       Up 4 minutes        0.0.0.0:8321->8321/tcp   addon_a0d7b954_ide
86beb5d91e2a        homeassistant/amd64-addon-samba          "/run.sh"                4 minutes ago       Up 4 minutes                                 addon_core_samba
31ef8f085bb2        homeassistant/amd64-hassio-supervisor    "python3 -m hassio"      4 minutes ago       Up 4 minutes                                 hassio_supervisor
cfbc907f9f2a        homeassistant/qemux86-64-homeassistant   "/bin/entry.sh pytho…"   4 weeks ago         Up 4 minutes                                 homeassistant
root@hassio:/usr/share/hassio/homeassistant#

But when I go to http://IPADDRESS:8123 I get a connection refused.

The home-assistant.log just shows:

2019-04-16 22:58:59 WARNING (MainThread) [homeassistant.components.http] legacy_api_password support has been enabled. If you don't require it, remove the 'api_password'   from your http config.
2019-04-16 22:59:00 WARNING (Recorder) [homeassistant.components.recorder] Ended unfinished session (id=430 from 2019-04-17 02:48:26.202532)

My configuration.yaml:

homeassistant:
  # Name of the location where Home Assistant is running
  name: Home
  # Location required to calculate the time the sun rises and sets
  latitude: !secret home_zone_lat
  longitude: !secret home_zone_long
  # Impacts weather/sunrise data (altitude above sea level in meters)
  elevation: 156
  # metric for Metric, imperial for Imperial
  unit_system: metric
  # Pick yours from here: http://en.wikipedia.org/wiki/List_of_tz_database_time_zones
  time_zone: America/Toronto
  customize: !include customize.yaml

# Show links to resources in log and frontend
#introduction:

# Enables the frontend
frontend:

http:
  # Uncomment this to add a password (recommended!)
  api_password: !secret http_password
#  cors_allowed_origins:
#    - http://hassio.area51.local:7080
  #server_host: 192.168.12.11
#  use_x_forwarded_for: True
  ip_ban_enabled: True
  login_attempts_threshold: 5

# Checks for available updates
updater:

# Discover some devices automatically
discovery:
  ignore:
    - denonavr

# Allows you to issue voice commands from the frontend in enabled browsers
conversation:

# Enables support for tracking state changes over time.
recorder:
  # Delete events and states older than 2 weeks
  purge_interval: 5
  purge_keep_days: 7

# Enables support for tracking state changes over time.
history:

# View all events in a logbook
logbook:

# Track the sun
sun:

# Weather Prediction
#sensor:
#  platform: yr

ecobee:
  api_key: !secret ecobee_api_key

ios:

influxdb:
  host: 192.168.12.10

system_health:
lovelace:
  mode:  yaml
config:
device_tracker: !include device_tracker.yaml
zone: !include zones.yaml
#mqtt: !include mqtt.yaml
sensor: !include sensors.yaml
group: !include groups.yaml
#camera: !include cameras.yaml
notify: !include notifiers.yaml
input_boolean: !include inputboolean.yaml
automation: !include automations.yaml
media_player: !include media_players.yaml
zwave: !include zwave.yaml
remote: !include remotes.yaml
cover: !include covers.yaml
panel_iframe: !include panel_iframe.yaml
binary_sensor: !include binary_sensor.yaml
input_select: !include input_select.yaml
google_assistant: !include google_assistant.yaml
geofency:

It doesn’t seem to be complaining about anything in the config that it’s choking on yet I can’t get the front end.

Thanks for any help!

2

Welp. It turns out my Unifi controller docker which lives on another VM STB because of “low” disk space on the volume. MongoDB was complaining that 3GB free wasn’t enough to do some maintenance and as a result the Unifi controller hung up.

For some reason HassIO seems to think this is the end of the world and it would not initialize after a restart until I freed up enough disk space for the Unifi controller to finish doing it’s thing and come back from the dead!

Of course I’d already completely blew away my HassIO install and started from scratch only to discover that didn’t fix the problem. That led me to start removing configuration.yaml lines one by one until I finally figured out it was the device_tracker.yaml/Unifi that was causing the problem all along.

A little feedback would have been nice there, HassIO :wink: You know…like a log entry or something saying you couldn’t connect to Unfi?

Not my best troublehshooting day!