All of a sudden, I think, I can not connect to the frontend of Home Assistant. it’s just stuck at “Connecting” and after some time the password prompt is shown.
Automations are working, so the system is running. I also see the \hassio from Samba.
I did not do anything (updating, editing etc) when this happend.
Running hassio, Ras. PI and duckdns.
Have tried turning it off and on again
Output from home-assistant.log:
> 2018-08-03 10:21:41 ERROR (MainThread) [homeassistant.core] Error doing job: SSL handshake failed
> Traceback (most recent call last):
> File "uvloop/sslproto.pyx", line 593, in uvloop.loop.SSLProtocol._on_handshake_complete
> File "uvloop/sslproto.pyx", line 171, in uvloop.loop._SSLPipe.feed_ssldata
> File "/usr/lib/python3.6/ssl.py", line 689, in do_handshake
> self._sslobj.do_handshake()
> ssl.SSLError: [SSL: HTTP_REQUEST] http request (_ssl.c:777)
> 2018-08-03 10:21:41 ERROR (MainThread) [homeassistant.core] Error doing job: SSL error errno:1 reason: HTTP_REQUEST
> Traceback (most recent call last):
> File "uvloop/sslproto.pyx", line 497, in uvloop.loop.SSLProtocol.data_received
> File "uvloop/sslproto.pyx", line 204, in uvloop.loop._SSLPipe.feed_ssldata
> File "uvloop/sslproto.pyx", line 171, in uvloop.loop._SSLPipe.feed_ssldata
> File "/usr/lib/python3.6/ssl.py", line 689, in do_handshake
> self._sslobj.do_handshake()
> ssl.SSLError: [SSL: HTTP_REQUEST] http request (_ssl.c:777)
> 2018-08-03 10:21:48 ERROR (MainThread) [homeassistant.core] Error doing job: Task was destroyed but it is pending!
> 2018-08-03 10:21:48 ERROR (MainThread) [homeassistant.core] Error doing job: Task was destroyed but it is pending!
> 2018-08-03 10:21:48 ERROR (MainThread) [homeassistant.core] Error doing job: Task was destroyed but it is pending!
> 2018-08-03 10:21:48 ERROR (MainThread) [homeassistant.core] Error doing job: Task was destroyed but it is pending!
> 2018-08-03 10:21:48 ERROR (MainThread) [homeassistant.core] Error doing job: Task was destroyed but it is pending!
renew your SSL Certificate?
Double check that your port forwarding on your router is still working (I have a Xiaomi R3P that regularly “forgets” that the port forwarding is in place and I have to reset it)
The errors you get are know and have been reported already, though they do not impact use of HA.
have you tried to set up SSL? Error doing job: SSL handshake failed
You log has loads of errors relating to this.
Once SSL is setup, it normally uses HTTPS (not HTTP) and port 443…
did you use the discovery feature for google cast ?
I found that caused this problem too …
delete the “core.config_entries” file in the “.storage” folder , solved the problem
I’m back in!!
Not sure why, doh… Tried to forward :80 and :443 in router config (to rass PI ip, right?) and restarted the router. Now it’s working! But yougetsignal.com/tools/open-ports/ still reports the ports as closed…
If you don’t have ssl those ports are showing as closed even though they are forwarded as nothing is listening on them. Having 8123 forwarded without ssl and api/auto is a really bad idea.
I think i might found the cause of error. I added a simple switch between my router and Raspberry PI, which messed up something with the port forwarding. It worked one minute, but not the next.
I’ve now connected the PI directly to the router and only forwarded port 8123. The connection seems to be stable with this setup.
do you know why this isn’t working? I primarily use Hass to google cast but can’t load the frontend anymore unless I delete that file. FYI I just upgraded from a really old version to the latest version of Hass.
Problems back…
After a few days, I have to restart the router and the raspberry to be able to connect… OR I can turn of wifi on my phone…
So this is only a problem if the phone is connected to the same wifi as the Raspberry… Could it be som ip-conflicts or something?
