Firstly, I want to thank all developers and community members for their time and effort in making H.A.
It just gets better and better!
I’ve been having issues with logging into the web interface of H.A since upgrading to version 0.32.
Browsing to the URL for H,A with Chrome (as well as Firefox) on a desktop PC would show the message “Home Assistant had trouble connecting to the server. Try Again”.
I have tried this on a local connection (i.e on the same network as H.A and using a different PC) as well as remotely (via duckdns) with the same results.
I have emptied the cache on Chrome and disabled all plugins, with no affect.
Using Internet Explorer; the H.A logo is displayed, but it does not then load the main dashboard.
However, going to the same address on a mobile device would should H.A as expected.
I have subsequently newly installed Hasbian 1.0 to see if this would remedy the issue, but it is still behaving as above.
This indicates to me that the issue is with my desktop environment - I’ve been searching for answers on the forum and web; however I’ve now run out of ideas and talent to fix the issue!
Has anyone else come up against this issue or have any clues to a solution?
In your browser, have you tried looking at your dev tools (the browser’s dev tools - F12 on Win will open) to see if everything’s loading correctly? Check the “network” tool to make sure everything is loading. No errors, no 404s. And the console may list a javascript error if you’re getting any.
So, we’re going to need some more info about how you connect, I think. Do you have any proxies in place? I wonder if permission issues could cause 500 errors. Do you have encryption (LetsEncrypt) in place? Do you have an API password set?
Anything showing up in home-assistant.log?
Not sure I can help, but anyone pitching in to help will need to know this kind of stuff.
I’m connecting to the new “boxfresh” Hasbian installation on the same local network (i.e. no LetsEncrpt or DDNS)
and I’ve checked there’s no proxy on my desktop. There’s no password or any changes to the stock *.yaml files.
This is an excerpt of the log when I refresh the H.A (there are multiples of the same “KeyError”)
KeyError: “Key not found: ‘Accept-Encoding’”
16-11-17 16:20:34 aiohttp.web: Error handling request
Traceback (most recent call last):
File “/srv/homeassistant/lib/python3.4/site-packages/aiohttp/server.py”, line 261, in start
yield from self.handle_request(message, payload)
File “/srv/homeassistant/lib/python3.4/site-packages/aiohttp/web.py”, line 88, in handle_request
resp = yield from handler(request)
File “/srv/homeassistant/lib/python3.4/site-packages/aiohttp/web_urldispatcher.py”, line 505, in handle
ret = yield from self._file_sender.send(request, filepath)
File “/srv/homeassistant/lib/python3.4/site-packages/homeassistant/components/http.py”, line 181, in send
if ‘gzip’ in request.headers[hdrs.ACCEPT_ENCODING]:
File “multidict/_multidict.pyx”, line 124, in multidict._multidict._Base.getitem (multidict/_multidict.c:3296)
File “multidict/_multidict.pyx”, line 119, in multidict._multidict._Base._getone (multidict/_multidict.c:3231)
KeyError: “Key not found: ‘Accept-Encoding’”
Was this resolved I am getting the same problem running version 0.33.4. Works fine via mobile, but nothing getting a “Home Assistant had trouble connecting to the server” error in all desktop web browsers.
