Connectivity Issues - duckdns

ronvl · October 8, 2018, 8:52am

I had the same problem and I noticed that my fritzbox wasn’t updating DuckDNS anymore… there seemed to be some changes that broke the updates after installing a new firmware on my Fritzbox. So had to rreconfigure the URL/token etc an now it started working again…

Javier_Dst · October 11, 2018, 4:39pm

I removed the yr sensor from sensors and the port for hassio in the configuration.yaml and it worked as a charm.
It would be nice to hear from the developers if this is correct. So far, the SSL service is working fine.

http:
  api_password: !secret http_api
  base_url: https://hassio0domain.com #:8123 (Removed)

sensors.yaml
# Weather prediction
#  - platform: yr (Removed)

Martin_Granger · October 11, 2018, 8:08pm

So I’m having pretty much the same problem.

I have tried the above solutions but nothing is working. I can access my hassio using the duckdns address, but the browser gives me a certificate warning telling me that it’s out of date.

Jay.Gordon-Rolfe · October 15, 2018, 10:42am

I too am having the same issues:

 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()

wilsonmanmcp · October 19, 2018, 10:55am

any updates on this please? I am on hassio ver 80, still having same issue if I enable

http:
base_url: https://XXXX.duckdns.org:8123
ssl_certificate: /ssl/fullchain.pem
ssl_key: /ssl/privkey.pem

I tried removing https or port no from the base_url but still errors with Handshake problem.

and then Hassio won’t start up correctly in the UI…

any help please?

javicalle · October 20, 2018, 7:12pm

I think that this issue can be related with local acces to HA.
In my case after closing IDE web browser (http://hassio.local:8321/ide.html) all trace errors have gone.

fcollingwood · October 29, 2018, 1:06am

Add the following in configuration.yaml in the http: section:

ssl_profile: intermediate

Courtenay_Watson · November 2, 2018, 12:12am

That didn’t resolve my problem @fcollingwood

pangit · November 4, 2018, 4:34am

I’ve tried all the fixed above too, still spamming my log with the same message…

Anything else I can try?

ccollinscj · November 4, 2018, 5:01pm

I am in the same boat, every minute I get the error.

au190 · November 4, 2018, 5:13pm

same here

2018-11-04 17:44:02 ERROR (MainThread) [homeassistant.core] Error doing job: SSL error errno:1 reason: NO_SHARED_CIPHER
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: NO_SHARED_CIPHER] no shared cipher (_ssl.c:841)

Peter_Iliev · November 6, 2018, 7:16am

I have the same errors. There have to be a reason? What is the main initiator for that errors?

chris1 · November 10, 2018, 8:43pm

same here. error every minute

DieterClaeys · November 12, 2018, 6:34am

I have something very strange as well.
I’ve installed HASSIO on a raspberry PI and installed DuckDNS with LetsEncrypt.
I can connect via HTTPS://xxxx.duckdns.org if I am on a 4G network or if I am on another location.
However, If I am on my own network, I can only connect with one laptop that I have.
All my other devices fail with Error Connection.
I tried with 2 iPads and 2 Windows 10 devices.
I don’t understand that I am able to connect with one device, but all others fail

fcollingwood · November 14, 2018, 12:54am

Still an issue on 0.82:

2018-11-14 00:19:21 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)
2018-11-14 00:19:22 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-11-14 00:19:22 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)

kayhanbelek · November 14, 2018, 6:04am

same here.

homeassistant on ubuntu 16.04.
duckdns.org with port 8123.
api_password enable or disable, doesn’t matter.
base url with https:// or without https:// doesn’t matter.
log size 1,5 MB in 10 minutes… and counting

DieterClaeys · November 14, 2018, 6:27am

Same here - and getting frustrated.
I have 5 Google Homes that I can’t integrate in Home Assistant due to this.
I know that you can choose for the cloud version, but paying $5/month is, in my humble opinion, ridiculous.

alagarath · November 20, 2018, 2:26pm

I created an account just to hopefully help with this, no longer a lurker. I found that any traffic attempting to touch Home Assistant with anything other than the CN in the cert the SSL error message will appear (i.e accessing with the 127.0.0.1, private/local IP, or public IP with http or https protocols).
It looks like a couple issue have cropped up in this one thread. Log bloat from the SSL error message being written multiple times a minute and the Google connection to Home Assistant. I’m using Home Assistant and not hass.io but I hope this will be helpful to all if it’s the same situation.

#### Log bloat from the ssl.SSLError: [SSL: HTTP_REQUEST] http request (_ssl.c:777) ####
As a reference point, when I set up my instance I used these instructions, migrating from a virtual environment.
My Home Assistant setup: RPi 3B, Docker Compose, Node-RED, SSL, client certs, etc…

Here’s how I fixed it first and then the explanation is below. Note, I don’t have NGNIX or organizr set up yet so that’s the main reason this is set up this way. I believe you would have a similar sitatuion if you decided to have a "ha.yoursubdomain.duckdns.org" and a Let’s Encrypt cert tied to that.

Navigated to /opt/ where my docker containers and docker-compose.yml file are stored
cd /opt/
Use a text editor of some sort to open docker-compose.yml
nano docker-compose.yml
Go down to the section for homeassistant and then find “healthcheck:” and it shoud look sometehing like this
This healthcheck seems to check in about every second or more to see if the webpage exists for health status in the console and tools like portainer

Look for this in docker-compose.yml homeassistant section…

    healthcheck:
      test: ["CMD", "curl", "-f", "http://127.0.0.1:8123"]
      interval: 30s
      timeout: 10s

Replace with something like this…changing “yoursubdomain” and/or the port based on your setup

    healthcheck:
      test: ["CMD", "curl", "-f", "https://yoursubdomain.duckdns.org:8123"]
      interval: 30s
      timeout: 10s

If you’re using nano hit Ctrl X and Ctrl S to save
Before doing this next step ensure that your homeassistant configuration isn’t stored IN the docker container
Or ensure you have a backup this would wipe your configuration if it is stored in the docker container
For me my configuration is under /opt/homeassistant and isn’t affected by blowing away the container
docker stop homeassistant
Removes homeassistant container
!!!Backup your config!!!
docker rm homeassistant
Creates new container without showing output and starts homeassistant
docker-compose up -d homeassistant
Check your Home Assistant log for the error and it shouldn’t be there if you were in the same situation.
That’s it! That’s what worked for me! I don’t have those entries in the log anymore

#### Google Connection Issue ####

I didn’t see this posted in the thread. I followed these instructions to a T for Google Assistant and it worked for me.
At first I thought this is what was generating the SSL error messages but it came down to docker-compose.yml
I had Google Assistant setup prior to .8 with old instructions and found I had to follow these new instructions and wipe the devices from my Google Home app after the changes
I created unique complex credentials for Google Home in my Home Assistant instance when I set it up in the Google Home app.

#### References ####
Someone in another thread said this error appeared with the installation of Home Assistant in docker.SSL handshake failed I wouldn’t say that’s the only time this will pop up but in this case that was the key ingredient for troubleshooting in my situation.

lolouk44 · November 20, 2018, 9:59pm

Thanks. I don’t have any healthcheck entry in my docker-compose so I’m wondering whether this is the issue…
I will try and add it and report…

PS you may want to format your code so it can be copied (check that blue bar on top of the page), e.g.

      healthcheck:
        test: ["CMD", "curl", "-f", "https://127.0.0.1:8123"]
        interval: 30s
        timeout: 10s

lolouk44 · November 23, 2018, 12:15am

I’m afraid no changes, I still get the error messages.