Can't bypass login. Shown "Login aborted: Your computer is not allowed"

Configuration
1

Hello, I am running HA in docker in windows 10. I now wish to bypass login using trusted network. However, I’ve encountered the error “Login aborted: Your computer is not allowed”.

I have tested this both on the same local network and on a reverse proxy. Same error in each case.

The error and my configuration.yaml:

[Album] imgur.com

This error was not reported on the forum as far as I know. Would anyone know why this is happening? Thanks!

2

Change 192.168.1.0 to 192.168.0.0, see if that helps.

3

And you’re misunderstanding allow_bypass_login. It means if you have just one user, you don’t have to choose from the one-item dropdown. You’ll still get an error if you aren’t in the right IP range.

4

Thanks for the reply but changing 192.168.1.0 to 192.168.0.0 did not help.

My local network is on the 192.168.1.x. However it is giving me the same “Login aborted: Your computer is not allowed" error.

I tried accessing HA with different device on my local network and it still gives me this error. I can’t figure out why HA is saying that I’m not allowed…

5

If you run ipconfig in CMD on the device, what do you get?

6

My computer is in another language but it’s basically:
DNS suffix . . . . . . . . : HOMELAN
IPv6 address. . . . . . . : fe80::b08e:58b5:85a1:fc08%18
IPv4 address. . . . . . . . . . . . : 192.168.1.132
Subnet mask. . . . . . . . . . . .: 255.255.255.0
Default gateway . . . . . . . . . . . . .: 192.168.1.1

7

Weird. Is HA on the same LAN as your PC? Do you see anything in logs?

8

Yes it is on the same lan, running on docker on the 192.168.1.132 machine.

Log doesn’t show any errors.

9

Does changing use_x_forwarder_for change anything? And change 192.168.0.0 back to 192.168.1.0.

10

Same error unfortunately regardless of if I include use_x_forwarder_for or not.

11

What ip address does home.whatever.com resolve to?

12

It resolves to my external ip. I tried adding that to the conf but it’s the same error

13

Make sure you rebooted. This is my config:

  auth_providers:
    - type: trusted_networks
      trusted_networks:
        - my.external.ip.address/32
14

Sorry to interrupt, but that looks interesting: so are we able to block (or allow) access to HA instance for specified IPs/IP ranges using auth_providers, right?

And the http directive looks exactly what I was looking for: Fail2Ban on HASS OS. :smiley:

15

Nope.
This lets anyone log in without a password, as long as they come from a certain IP.

Basically. And it works on all HA installs, not just HA os.

16

Ah okay, so less security for the first one and easy security for everyone running HA if needed. Thank you for clarifying.

17

Sadly adding the external ip didn’t work either.

18

Got it working by adding the following to nginx conf:

proxy_set_header X-Real-IP       $proxy_protocol_addr;
proxy_set_header X-Forwarded-For $proxy_protocol_addr;

And then adding the docker ip to Trusted Networks and Trusted Proxy, which in my case is 172.17.0.1 (You can find it in the docker command line when you click the login button)
I don’t actually know why tho…

1 Like
19

You know, this is the first mention of nginx in this thread. It would be helpful to mention everything relevant when you post a question.

2 Likes
20

I have this same problem. I cannot get HA to login on my google home device. I get the Login aborted. Your computer is not allowed error.