Upgrade issues from 0.80.1 to 0.81.6

Installation
1

I’m having an issue upgrading Home Assistant from 0.80.1 to 0.81.6. I use Hassio for my HA infrastructure.

When I tell Hassio to upgrade, all seems well. The upgrade goes through, and I can look at homeassistant.log within the homeassistant directory and I see activity happening, just as I normally would as if the system was up.

But, I can’t access the frontend. When I do a netstat, I don’t see it listening over 8123. Not sure where to look in logs to fix this. Instead, I completely removed the homeassistant directory, rebooted the host, went through a fresh install, and restored a snapshot that I took from hassio, and that works - netstat once again shows it is listening over 8123. But, then I am still on 0.80.1.

There is likely something in my homeassistant directory that causes this to fail. Where do I even start to troubleshoot this?

Looks like it may be an issue within this container:
homeassistant/amd64-addon-configurator

2

so remove the configurator addon and try again…

3

I believe that is needed since that sets up port forwarding in docker?

4

no configurator is an addon… it doesn’t forward anything… it’s just an editor.

5

So, i looked further and found this error message in the homeassistant.log file:

2018-11-07 22:21:21 ERROR (MainThread) [homeassistant.config] Invalid config for [http]: value should be a string for dictionary value @ data[‘http’][‘base_url’]. Got [‘hassio.bdf0506.net:8123’]. (See /config/configuration.yaml, line 88). Please check the docs at HTTP - Home Assistant

Pretty strange, since the http section hadn’t changed in months in my config. I tweaked the http file a bit, then changed it back to what it was and then it still loads. Really strange.

Here’s what the http config looked like, I think it didn’t like that base_url was formatted like a list instead of a string? Not sure. Either way, upgraded now.

http:
  # Secrets are defined in the file secrets.yaml
  # api_password: !secret http_password
  # Uncomment this if you are using SSL/TLS, running in Docker container, etc.
  # base_url: example.duckdns.org:8123
  api_password: xxxxxxxxxx
  ssl_certificate: /ssl/ha.crt
  ssl_key: /ssl/ha.key
  cors_allowed_origins:
    - http://hassio.home:7080
  base_url: 
    - hassio.bdf0506.net
  trusted_networks:
    - 192.168.0.0/24
    - 172.21.0.0/24
  ip_ban_enabled: True
  login_attempts_threshold: 3