HA No longer starts 0.90 --> Auth_Providers

Configuration
1

Hey again,

So I tried after upgrading to 0.90 to setup auth_providers after I removed api_password.

I added this:

  # Authenticated Users and Networks
  auth_providers:
   - type: myaccountname
   - type: trusted_networks
     trusted_networks:
       - 127.0.0.1
       - 192.168.1.0/24

Rebooted and now I only get the webpage with: ERR_CONNECTION_REFUSED

I tried removing the above again and rebooted through SSH, but no luck :frowning:.

Heeeeeelp

2

Well power cycle number 5 did the trick and I removed the above code, but that shouldn’t really prevent HA from starting right?

3

I have:
- type: homeassistant
not an account name. other than that, indentations maybe?

1 Like
4

Could be both, but after it came up and running again, I don’t feel like changing or trying it again :blush:

1 Like
5

I had the same issue, I followed the steps on to update to auth: and I was unable to get HA working, it would hang. I would only get some error related to auth and that was the end of the log and no more frontend. I had to move everything to http: component and power cycle my rpi.

I had my config more or less like this:

homeassistant:
  auth_providers:
   - type: homeassistant
   - type: legacy_api_password
   - type: trusted_networks
     trusted_networks:
		- 192.168.0.0/24
		- 172.16.0.0/12
		- 192.168.1.0/24
		
http:
  ssl_certificate: /ssl/fullchain.pem
  ssl_key: /ssl/privkey.pem
  api_password: mypasswordhere
  base_url: mybaseurl.duckdns.org
  cors_allowed_origins:
    - http://blablabla.com
  ip_ban_enabled: true
  login_attempts_threshold: 10
6

I was just under the impression that after 89.2 or when upgraded to 0.90, then it was no longer needed to keep it under http: ?

7

This is what I found on the docs regarding auth and api_password

Example:

homeassistant:
  auth_providers:
   - type: legacy_api_password

http:
  api_password: !secret http_password
8

For 89.2 forward, remove auth configuration from http:. Configure under homeassistant with auth_providers:. legacy_api_password is rapidly being phased out.

9

Exactly, but maybe the network part trigerred something unexpectedly.
But even if I created the above and the api_password being phased out, then I would end up with nothing - so maybe I will just continue without this.