New auth system owntracks problem

Configuration
1

I enabled the new auth system on my Hassio (pi) last night and then couldn’t work out how to configure it as this page: https://developers.home-assistant.io/blog/2018/07/02/trying-new-auth.html is pretty sparse.

“If you are using Hass.io, you must enable legacy API password support.” Great. How do I do that?

“This rest of the instructions are no longer necessary in Home Assistant 0.74 or later.” Fine. There’s nothing to configure then?

So I gave up and commented out the the following in my configuration.yaml:

homeassistant:
  # auth_providers:
  #  - type: homeassistant

Then I restarted Hassio.

Unfortunately now Owntracks (HTTP) is reporting 403 errors when trying to connect. Is there any way to fix this?

2 
# Example configuration.yaml entry
homeassistant:
  auth_providers:
   - type: homeassistant
   # Uncomment next line if you want to enable legacy API password support
   # - type: legacy_api_password

Did you saw “Uncomment next line if you want to enable legacy API password support”?

3

No, I overlooked that. Sorry. Should I commet out - type: homeassistant as well as un-commenting - type: legacy_api_password

Edit:

I tried with and without - type: homeassistant in both cases I get the following warning and Owntracks is still not connecting:

Please change to use bearer token access /api/error/all

This is my current config:

homeassistant:
  auth_providers:
   - type: legacy_api_password
  #  - type: trusted_networks
   - type: homeassistant
4

Solution: IP ban had blocked the phone Ownracks was running on.

Also I finally see the new login page after a few HA restarts and forcing a web browser cache refresh.