Unable to log into webpage after upgrade

I am getting confused as to when this problem happened but I cannot for the life of me understand what has gone wrong. I have been running version 0.56.1 since I first set up HA. No problems with the web-interface. Running SSL and password, working on mobiles and computer.

Today I upgraded to 0.57.2 and I have tried to remove cookies, run browser in private/inkognito mode etc but I am not able to log in. Some devices worked by cached credentials but as soon as I try to log in again I get failed login attempts in the log. I have tried to remove the SSL settings, remove password, reboot the docker (I run the docker image on Synology), reboot the NAS, reboot the router which does the port-forward, etc, etc. Same error now on all devices, unable to log in. Of course I also tried to downgrade to the old version 0.56.1 docker but no success (this is the one I run right now).

I am running mysql/mariaDB, found the database to be 1,2 GB, trunkated this to zero also. No change.

Here are some things I found in the log:

017-11-07 21:22:47 ERROR (MainThread) [aiohttp.server] Error handling request
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/site-packages/aiohttp/web_protocol.py", line 278, in data_received
    messages, upgraded, tail = self._request_parser.feed_data(data)
  File "aiohttp/_http_parser.pyx", line 274, in aiohttp._http_parser.HttpParser.feed_data (aiohttp/_http_parser.c:4364)
aiohttp.http_exceptions.BadStatusLine: invalid HTTP method

If I open development console in Chrome to get some more debug info from the client side I find the following:

frontend-2de1bde3b4a6c6c47dd95504fc098906.html:1 Uncaught TypeError: Cannot read property 'root' of undefined
    at HTMLElement.forwardHostProp (frontend-2de1bde3b4a6c6c47dd95504fc098906.html:1)
    at Object.fn (frontend-2de1bde3b4a6c6c47dd95504fc098906.html:1)
    at a (frontend-2de1bde3b4a6c6c47dd95504fc098906.html:1)
    at e (frontend-2de1bde3b4a6c6c47dd95504fc098906.html:1)
    at HTMLTemplateElement.value (frontend-2de1bde3b4a6c6c47dd95504fc098906.html:1)
    at HTMLTemplateElement.value (frontend-2de1bde3b4a6c6c47dd95504fc098906.html:1)
    at HTMLTemplateElement.value (frontend-2de1bde3b4a6c6c47dd95504fc098906.html:1)
    at HTMLElement.value (frontend-2de1bde3b4a6c6c47dd95504fc098906.html:1)
    at HTMLElement.value (frontend-2de1bde3b4a6c6c47dd95504fc098906.html:1)
    at HTMLElement.value (frontend-2de1bde3b4a6c6c47dd95504fc098906.html:1)

I am loosing my mind over this crazy error. What the heck am I missing? #tired

@balloob could this be due to the changes of the front end in the latest release? Does the upgrade change something in the config directory hindering me in doing downgrade? (I get the same error when I run the old version…)

Since you running docker, just create new container with no config changes. Just to make sure networking ok and no other funny business.

Yes. Changes from 56 to 57 may have broke something but your errors are weird. Don’t look like config issue but should verify anyway.

No. Downgrade should be OK. I would try that to verify config is OK and then start upgrade from beginning

1 Like

Hello @tmjpugh, thanks for this guidance. I have now reverted to blank config and got my login back. I am now importing config piece by piece and it seems to be working. After a day or so I should be back to normal if everything goes well.

Sadly I opted to downgrade again (I am on 0.56.2 now and that works fine). I will wait until a new release before I try to upgrade again.

I am having the same issue but it happens with an upgrade from 0.57.3 to 0.58.0 and higher. I’m stuck at 0.57.3 and cannot upgrade until this issue is resolved. I’m going to keep digging around and see if I can figure out more.

My issue is actually Upgrade to 0.58 breaks frontend