Ip ban added to configuration.yaml but no ip_ban.yaml file

Configuration
1

I have added the IP ban enabled and login thresholds to my configuration.yaml under http and restarted. I am getting blocked attemps but cannot find the ip_ban.yaml file anywhere, am i missing something?

Thanks

2

Should be:

/config/ip_bans.yaml

If it isn’t then share this config:

3 

# Loads default set of integrations. Do not remove.
default_config:

# Load frontend themes from the themes folder
frontend:
  themes: !include_dir_merge_named themes

automation: !include automations.yaml
script: !include scripts.yaml
scene: !include scenes.yaml


http:
  ip_ban_enabled: true
  login_attempts_threshold: 3
4

File isn’t created until HA actually bans one (first) IP.
And, setting attempts to just 3 is pretty bold, i’d say…sooner or later you’ll lock yourself out…
And, make sure you always have “a reserve IP”… like connecting via GSM, or from a friend’s IP…and install SSH access!

5

Thanks for the reply I have increased the attemps. But after testing i am still not getting the ip_bans.yaml file. and I have no idea why.

6

are you saying to setup remote ssh? please do NOT.
local ssh would be useful if that’s what you mean. with keys and no password is better.

Its not a big deal if you have physical access to machine. just access with keyboard and mouse. unless you ban your entire local ip range you can just set another IP and use that to login as well when you get locked out.

As was previously said, this fail is not created until an IP is actually banned. Are you testing this with bad login attempts?

7

Hi Yep still no bans file. So removed the 2 lines from the configuration.yaml. Retsarted Home assitant. Then readded. then tried again now banning correctly from remote test machine. Very strange.

8

Hm… where did you read that i suggested REMOTE ssh? With installing “advanced ssh&web terminal you get local ssh access only. It’s way easier than via HA’s limited command line.