Can't access homeassistant

Configuration
1

Out of a sudden my homeassistant became inaccessible.
I log into it through http://192.168.0.xxx:8123 and now i’m getting

image

ssh is working fine
i can ping my google.com and my ip
I can access portainer and all other services running on docker

The homeassistant logs show some errors, but I can’t see if any of them is causing it:

image
image869×935 292 KB

any help will be very appreaciated, as I have no idea what I can do to fix this

i’m also not sure if this can be a firewall issue, i’ve tried to check and enable everything and the error persists
image

2

Look like your IP was ban, you can ssh into it, and configure configuration.yaml to disable the ban for now and try to fix it.

image
image782×45 27.7 KB

3

I already had my ip under trusted_proxies

I also included it in ip_ban_whitelist, but the problem persists

image

I’m also getting this error on the log, so I might have added it wrongly?

2023-04-02 14:05:19.750 ERROR (MainThread) [homeassistant.config] Invalid config for [http]: [ip_ban_whitelist] is an invalid option for [http]. Check: http->http->ip_ban_whitelist. (See /config/configuration.yaml, line 33). Please check the docs at HTTP - Home Assistant

4

Now I added ip_ban_enabled: false and the error went away, but I still can’t access HA :sleepy:

The log looks like this:

image
image891×686 184 KB

5

You also need to clear the ban IP.

1 Like
6

I don’t have an ip_bans.yaml in config

do you think that’s the problem?

7

Try to restart your home assistant machine, clear your cache or check your page in private/anonymous mode. And see if the log file has some information.

8

There is a mismatch with your IP, do you really have two network?

image

9

i’ve restarted and recreated it from portainer, and also tried to check through different devices and anonymous… still not going through

10

it was a typo, the right is 192.168.0.0/24
thanks for catching it

although I removed this ip_ban_whitelist as it was generating errors and added ip_ban_enabled: false

the error about ip_ban went away, but still cannot access HA

11

Was it working before, what is the url your are using to connect? Nothing about the problem in the log file?

12

it was working, and then my server went through some problems that I solved through fsck.
after fixing the server everything was back to normal except for HA

the url i’m using is http://192.168.0.200:8123

Should I try reinstalling HA from scratch? i’ve treated it as the last resource as I have never done it before and don’t know exactly if I will be able to recover everything as it was

13

How about the status on the observer site at port: 4357
http://192.168.0.200:4357

14

I can’t access this
i’m running HA core, if that matters

15

It just connected.
I’m not sure the exact reason, as I was trying different things

Last thing i did was to re-try disabling the firewall and rebooting… could be this :thinking:

Thanks a lot randomsnack! I really appreciate the time you dedicated to give support to a stranger! :slight_smile:

2 Likes
16

@markjohn can you please mark the answer that solved this for you as the solution?
That way this topic has more value for fellow HA-users who search for the same thing + no time/energy is wasted by others trying to help you.

1 Like