Is the problem solved?
I configurated my remote access today and I am getting these errors.
Running Hass 0.75.2
access through Chrome and IOS app.
access via Wifi and 4G is possible
Is there already a solution?
my config:
Issue still ongoing with 78.3. With allowed_cords, and all other “fixes” mentioned above still the
same error every 1 second in the log but the SSL connection does work.
2018-09-23 11:38:32 ERROR (MainThread) [homeassistant.core] Error doing job: SSL error errno:1 reason: HTTP_REQUEST
Traceback (most recent call last):
File "uvloop/sslproto.pyx", line 504, 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/local/lib/python3.6/ssl.py", line 689, in do_handshake
self._sslobj.do_handshake()
ssl.SSLError: [SSL: HTTP_REQUEST] http request (_ssl.c:841)
only solution is to make the base_url HTTP only and comment out the SSL file locations.
Any ideas on when this will be fixed? A full disk just about crashed my instance yesterday night!
Error doing job: SSL error errno:1 reason: WRONG_VERSION_NUMBER
Traceback (most recent call last):
File "uvloop/sslproto.pyx", line 504, 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/local/lib/python3.6/ssl.py", line 689, in do_handshake
self._sslobj.do_handshake()
ssl.SSLError: [SSL: WRONG_VERSION_NUMBER] wrong version number (_ssl.c:841)
I am still getting these errors despite the fact that I am on the latest version of Hassio and the the issue has been closed:
2018-09-30 17:09:14 ERROR (MainThread) [homeassistant.core] Error doing job: SSL handshake failed
Traceback (most recent call last):
File “uvloop/handles/stream.pyx”, line 609, in uvloop.loop.UVStream._on_eof
File “uvloop/sslproto.pyx”, line 171, in uvloop.loop._SSLPipe.feed_ssldata
File “/usr/local/lib/python3.6/ssl.py”, line 689, in do_handshake
self._sslobj.do_handshake()
ssl.SSLError: [SSL: HTTP_REQUEST] http request (_ssl.c:841)
2018-09-30 17:09:14 ERROR (MainThread) [homeassistant.core] Error doing job: SSL error errno:1 reason: HTTP_REQUEST
Traceback (most recent call last):
File “uvloop/sslproto.pyx”, line 504, 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/local/lib/python3.6/ssl.py”, line 689, in do_handshake
self._sslobj.do_handshake()
ssl.SSLError: [SSL: HTTP_REQUEST] http request (_ssl.c:841)
I’ve read every thread I could find discussing the issue and tried every suggested solution to no avail. Some reference open bug tickets but these are all closed as being resolved yet there is no explanation as to how they were resolved.
I’m going to cut out some of the logging as suggested above by @henkie86, but that is not an ideal solution but I have to do something to stop the log spam.
My Hass is accessible via the duckdns domain outside the local network.
Initially I thought the errors might be because I was accessing the Hass front end locally and securely (https) via the IP address and the certificate is only valid for the duckdns domain. And the errors did seem to occur at these local access times. So I exclusively used the duckdns domain, when inside and outside my local network.
I still saw the SSL errors.
So I figured it must be something to do with NAT loopback redirecting my browser to the local IP (which the certificate is not valid for) - but I also saw these errors logged for times I was not accessing the front end. So (discounting intrusion) some component was also generating them.
Possibly my cert_expiry sensor which also tries to access the duckdns domain from inside the network.
I think this would explain it.
Any sensor or attempt to access your duckdns domain from within your local network will be NAT loopbacked by your router to the Hass IP address. The SSL certificate is not valid for the IP address, only the duckdns domain. Hence the SSL errors, even though everything seems to work.
Sound reasonable? Or am I barking up the wrong tree?
Worked for me also and makes sense. The same URL as you use to access your HA is the URL that HA will use to access itself.
So the trick is to skip the :8123