I just updated my HA version to 0.77, created a new username/password combo, and set up the multifactor authentication. All of a sudden my system became unresponsive, and my attempts to log in again have left me locked out of the system. This is what appears when I go to my https duckdns login url:
Basic url:
Basic url/states:
Apart from what is shown here, the login pages are blank.
Clicking the link does nothing and when I do get to the “blank” login page, I can enter my password, and upon pressing enter the system attempts to log in. After a while, however, I just go back to the “blank” login page.
A couple of notes:
I was in the process of setting up NodeRED when I started experiencing the issue. I had set up a simple port forwarding rule on my router (which wasn’t working), but reverting to my old router setup doesn’t seem to make any difference.
The post-update profile and authentication setup didn’t go as smoothly as in the video. The profile bubble didn’t appear immediately in the top left corner (as in the video), and I had to log out and log in a couple of times before I was able to continue with the multifactor authentication.
I have restarted my RPI3 through SSH, but to no avail. I can still access the config files through samba/explorer, but I just can’t seem to log in through Chrome or the iOS app.
I haven’t experienced that, but I’ve read you can remove .storage/auth* and .storage/onboarding to restart the onboarding process. Maybe you get trough it without problems on the 2nd try
Just to make sure: You’ve restarted home assistant after deleting the files?
I saw the comment “Fix redirect to login page on offline server” attached to release 0.77.2. Sounds a little cryptic but maybe that will solve your issue.
I’m also having the same issue.
Looking at the HA log file it reports:
2018-09-02 16:21:32 WARNING (MainThread) [homeassistant.components.http.ban] Login attempt or request with invalid authentication from 127.0.0.1
Have toyed around changing settings in configuration.yaml with no luck.
auth_providers:
I’m having the same issue without multifactor authentication.
If I try to open home assistant with the browser in private mode no page is shown…
Nevertheless I’m able to control my devices with google home so it’s only the front-end that has some issues…
I’ve narrowed the problem to not having “module named 'voluptuous_serialize”. Every time I attempt to load the web page the following error is generated in the HA log file.
2018-09-02 21:11:52 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
File “/srv/homeassistant/lib/python3.6/site-packages/aiohttp/web_protocol.py”, line 390, in start
resp = await self._request_handler(request)
File “/srv/homeassistant/lib/python3.6/site-packages/aiohttp/web_app.py”, line 352, in _handle
resp = await handler(request)
File “/srv/homeassistant/lib/python3.6/site-packages/aiohttp/web_middlewares.py”, line 106, in impl
return await handler(request)
File “/srv/homeassistant/lib/python3.6/site-packages/homeassistant/components/http/static.py”, line 66, in staticresource_middleware
return await handler(request)
File “/srv/homeassistant/lib/python3.6/site-packages/homeassistant/components/http/real_ip.py”, line 34, in real_ip_middleware
return await handler(request)
File “/srv/homeassistant/lib/python3.6/site-packages/homeassistant/components/http/ban.py”, line 67, in ban_middleware
return await handler(request)
File “/srv/homeassistant/lib/python3.6/site-packages/homeassistant/components/http/auth.py”, line 68, in auth_middleware
return await handler(request)
File “/srv/homeassistant/lib/python3.6/site-packages/homeassistant/components/http/real_ip.py”, line 34, in real_ip_middleware
return await handler(request)
File “/srv/homeassistant/lib/python3.6/site-packages/homeassistant/components/http/ban.py”, line 67, in ban_middleware
return await handler(request)
File “/srv/homeassistant/lib/python3.6/site-packages/homeassistant/components/http/auth.py”, line 68, in auth_middleware
return await handler(request)
File “/srv/homeassistant/lib/python3.6/site-packages/homeassistant/components/http/view.py”, line 113, in handle
result = await result
File “/srv/homeassistant/lib/python3.6/site-packages/homeassistant/components/http/data_validator.py”, line 47, in wrapper
result = await method(view, request, *args, **kwargs)
File “/srv/homeassistant/lib/python3.6/site-packages/homeassistant/components/http/ban.py”, line 77, in handle_req
resp = await func(view, request, *args, **kwargs)
File “/srv/homeassistant/lib/python3.6/site-packages/homeassistant/components/auth/login_flow.py”, line 173, in post
return self.json(_prepare_result_json(result))
File “/srv/homeassistant/lib/python3.6/site-packages/homeassistant/components/auth/login_flow.py”, line 116, in _prepare_result_json
import voluptuous_serialize
ModuleNotFoundError: No module named ‘voluptuous_serialize’`
I’m up and running again. For what it’s worth, I did the following:
Restored a “safe” snapshot through SSH (after a few hours of running into brick walls while troubleshooting). I don’t know if this was necessary in the end, but I didn’t get the error messages in the log that informed me to remove the api_password until after rolling back to an earlier snapshot, and updating to version .77 (see steps 2 and 3).
Updated version to .77 and repeated the authentication setup process. It went flawlessly this time around, compared to my first experience.
Removed api_password from the http component in configuration.yaml.
Changed the URL in my Duck DNS addon settings to a new url (along with any other references to the original URL in my config files). For some reason using my original url for my remote access defaulted to the faulty login pages shown in OP, even after I had made substantial changes to my config/authentication setup (in an effort to come up with a solution). I tried clearing my browser history/cache but to no avail (until now, 24+ hours later). No idea what was going on there.
Thanks but unfortunately don’t have a safe version.
…how do you create a snapshot?
Android app, appdaemon & HADashboard work fine with legal API enabled.
Have upgraded the system many times in the past and managed to resurrect HA but this time I’ve lucked out.
My only option is to start with a new flash card and reinstall. Which is not such a bad idea to have a clean install anyway.
Above commands should install the missing lib for you, but it may mask the root cause of the failure since this lib should be installed along with upgrade process.
My install has been messy and since moved on to a fresh install…that particular issue has gone away.
But I’m stuck with the following error as reported by HA log file:
homeassistant.components.http.ban] Login attempt or request with invalid authentication from 192.168.1.102
The above address is the remote machine.
See other post floating around and having the same issue.
I get ERR_CONNECTION_REFUSED. I can ping both eth0 and wan0 but the connection is refused with no other info to go on. is there a log I can examine to see what caused the problem?
