Connectivity Issues - duckdns

same issue here :frowning:

running latest hass.io + duckdns addon, can’t access xxx.duckdns.org from local wifi, but only via 4G.

I installed DNSmasq as suggested on some other topic, but that did not help.

I just setup duckDNS with SSL on hass.io 0.74.2
Everything is working perfectly and can access it from the home wifi and outside.

I do see the same error in the log:

Error doing job: SSL error errno:1 reason: HTTP_REQUEST
8:42 AM /usr/local/lib/python3.6/site-packages/homeassistant/core.py (ERROR)
Error doing job: SSL handshake failed
8:42 AM /usr/local/lib/python3.6/site-packages/homeassistant/core.py (ERROR)

So if people are referring to the “same issue” here on the messages of the past few days then I guess they refer to the errors in the log. Not connectivity issues.

Seeing the same error messages. Can connect but it is filling my logs. hassio 0.74.2

I also have the same behavior. No issues connecting but logs full of SSL errors. Duck DNS add on in Hassio. HA version 0.74.2

2018-08-01 18:04:08 ERROR (MainThread) [homeassistant.core] Error doing job: SSL error errno:1 reason: TLSV1_ALERT_DECRYPT_ERROR
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: TLSV1_ALERT_DECRYPT_ERROR] tlsv1 alert decrypt error (_ssl.c:841)
2018-08-01 18:04:09 ERROR (SyncWorker_1) [homeassistant.core] Error doing job: Task was destroyed but it is pending!
2018-08-01 18:04:09 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: TLSV1_ALERT_DECRYPT_ERROR] tlsv1 alert decrypt error (_ssl.c:841)
2018-08-01 18:04:09 ERROR (MainThread) [homeassistant.core] Error doing job: SSL error errno:1 reason: TLSV1_ALERT_DECRYPT_ERROR
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: TLSV1_ALERT_DECRYPT_ERROR] tlsv1 alert decrypt error (_ssl.c:841)

issue is already submitted -> https://github.com/home-assistant/home-assistant/issues/15579#
Just subscribe to the issue (fix it if you can) or wait for a fix.

1 Like

That fixed it.

This does seem to fix it! But why? What is Cors, and if it is now required to give it special access, why isn’t this in the documentation, or even just mentioned by the developers? Surely that would be an easy fix for the users of this add-on?

I do still see the occasional “Task was destroyed” error, but the majority of the spam is now gone.

Didn’t work for me Afterall, spam returned I’m afraid, I edited the post back there this morning if you want to check :frowning:

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:

configuration.yaml

http:
api_password: !secret http_password
base_url: https://my_url.duckdns.org:8123
ssl_certificate: /ssl/fullchain.pem
ssl_key: /ssl/privkey.pem

duckdns Addon

{
“lets_encrypt”: {
“accept_terms”: true,
“certfile”: “fullchain.pem”,
“keyfile”: “privkey.pem”
},
“token”: “my_token”,
“domains”: [
“my_url.duckdns.org”
],
“seconds”: 300
}

Error doing job: SSL error errno:1 reason: HTTP_REQUEST
17:18 /usr/local/lib/python3.6/site-packages/homeassistant/core.py (ERROR)
Error doing job: SSL handshake failed
17:18 /usr/local/lib/python3.6/site-packages/homeassistant/core.py (ERROR)
Error doing job: Task was destroyed but it is pending!
17:18 core.py (ERROR)
Error doing job: Task was destroyed but it is pending!
17:18 core.py (ERROR)
Error doing job: Task was destroyed but it is pending!
17:18 core.py (ERROR)
Error doing job: SSL error errno:1 reason: HTTP_REQUEST
17:17 /usr/local/lib/python3.6/site-packages/homeassistant/core.py (ERROR)
Error doing job: SSL handshake failed
17:17 /usr/local/lib/python3.6/site-packages/homeassistant/core.py (ERROR)
Error doing job: SSL error errno:1 reason: HTTP_REQUEST
17:17 /usr/local/lib/python3.6/site-packages/homeassistant/core.py (ERROR)
Error doing job: SSL handshake failed
17:17 /usr/local/lib/python3.6/site-packages/homeassistant/core.py (ERROR)
Error doing job: SSL error errno:1 reason: HTTP_REQUEST
17:17 /usr/local/lib/python3.6/site-packages/homeassistant/core.py (ERROR)
Error doing job: SSL handshake failed
17:17 /usr/local/lib/python3.6/site-packages/homeassistant/core.py (ERROR)
Error doing job: Task was destroyed but it is pending!
17:17 core.py (ERROR)
Error doing job: Task was destroyed but it is pending!

Hi,

I solved my problem by not including https

base_url: my_url.duckdns.org:8123

6 Likes

THANK YOU for posting this, @LoisChantada. This solved the problem I was having, too.

1 Like

worked for me!

1 Like

Well, CRAP.

Log Details (ERROR)
Wed Aug 29 2018 12:41:17 GMT-0400 (Eastern Daylight Time)

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: UNKNOWN_PROTOCOL] unknown protocol (_ssl.c:841)

Same issue here.

Mine also stopped working. I still get notifications even when i’m not on my LAN, but cant connect to my hassio with the app or web.

any news on this?

I have the same issue on hassio 0.77.3
after enabeling SSL my log is spammed with these errors.
I use letsencrypt only

tried to remove the “https” in configuration does not solve the problem

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)

Hi, all

Hot sure if this will help anyone else, but for me what worked was to remove the actual 8123 port from the config.yaml file:

http:
base_url: https://my_url.duckdns.org **(without ':8123')**
ssl_certificate: /ssl/fullchain.pem
ssl_key: /ssl/privkey.pem

Some components were also not working before and now everything works fine.

3 Likes

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!

Add this to your cofiguration.yaml
Error messages are then not stored anymore in your logfile. (other error messages also!)

logger:
  default: critical
1 Like