Bizarre UI Access Issue

rickje · April 1, 2019, 4:36pm

I’m calling it a issue.
Still getting errors in my log.
The configuration isn’t that diffucult. Hopefully i’ve done nothing wrong

sabbath · April 1, 2019, 4:59pm

I agree, hope they find something

Akovano · April 1, 2019, 9:13pm

I have the same issue, upgraded to 90.2 and lost access to the UI.
I’m using a let’s encrypt wildcard cert

I was able to SSH in and this is what’s in the logs.
I don’t know why it’s looking for sslv3? It’s been deprecated years ago.

2019-04-01 16:56:27 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.7/ssl.py", line 763, in do_handshake
    self._sslobj.do_handshake()
ssl.SSLError: [SSL: SSLV3_ALERT_CERTIFICATE_UNKNOWN] sslv3 alert certificate unknown (_ssl.c:1056)
2019-04-01 16:56:27 ERROR (MainThread) [homeassistant.core] Error doing job: SSL error errno:1 reason: SSLV3_ALERT_CERTIFICATE_UNKNOWN
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.7/ssl.py", line 763, in do_handshake
    self._sslobj.do_handshake()
ssl.SSLError: [SSL: SSLV3_ALERT_CERTIFICATE_UNKNOWN] sslv3 alert certificate unknown (_ssl.c:1056)
2019-04-01 16:56:29 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.7/ssl.py", line 763, in do_handshake
    self._sslobj.do_handshake()
ssl.SSLError: [SSL: SSLV3_ALERT_CERTIFICATE_UNKNOWN] sslv3 alert certificate unknown (_ssl.c:1056)
2019-04-01 16:56:29 ERROR (MainThread) [homeassistant.core] Error doing job: SSL error errno:1 reason: SSLV3_ALERT_CERTIFICATE_UNKNOWN
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.7/ssl.py", line 763, in do_handshake
    self._sslobj.do_handshake()
ssl.SSLError: [SSL: SSLV3_ALERT_CERTIFICATE_UNKNOWN] sslv3 alert certificate unknown (_ssl.c:1056)

rickje · April 3, 2019, 8:24am

Please do let the people also know in Github with your logfiles and configuration!
See https://github.com/home-assistant/home-assistant/issues/22625

rosie · April 12, 2019, 8:11am

Upgraded to 0.91.3 the other day, and this morning my https://domain.duckdns.org:8123 is dead. I can access via local IP if I ignore browser cert errors.

Trying to access the frontend on an external connection via duckdns, I get the following error instantly in my logs. Unable to connect to homeassistant in the browser.

Error doing job: SSL handshake failed
Traceback (most recent call last):
  File "uvloop/sslproto.pyx", line 500, in uvloop.loop.SSLProtocol._on_handshake_complete
  File "uvloop/sslproto.pyx", line 484, in uvloop.loop.SSLProtocol._do_handshake
  File "/usr/local/lib/python3.7/ssl.py", line 763, in do_handshake
    self._sslobj.do_handshake()
ssl.SSLError: [SSL: SSLV3_ALERT_CERTIFICATE_UNKNOWN] sslv3 alert certificate unknown (_ssl.c:1056)

The DuckDNS add on says my cert is still in date.

Valid till Jun 22 11:38:14 2019 GMT Certificate will not expire
(Longer than 30 days). Skipping renew!

My hadashboard seems to still be working and my automations are firing as expected. I’m stumped.

igorovich664 · April 15, 2019, 12:17pm

I’ve found the solution:

Turn off DuckDns Add-on
Use DuckDns component
Use Let’s Encrypt add-on and generate new fullchain.pem and privkey.pem files.

Restart, done!

fixer · April 15, 2019, 5:56pm

Can you write exact steps you made? Based on your points, it’s still not working for me. Thanks

maurizio53 · April 15, 2019, 6:06pm

I have the same issue, but not on HASSIO… how to fix it when running hassbian?

noahj96 · April 16, 2019, 4:03pm

Hey Rosie,

I had the same issue. What worked for me (in hass.io) was to remove the duckdns component in the configuration.yaml and simply keep the settings for the duckdns add-on in 0.91.3.

sabbath · April 16, 2019, 5:31pm

Epic @igorovich664 worked perfectly!
Thnx so much for this, have been running http for weeks now

B1G · May 3, 2019, 7:12pm

I have the same issue with hass.io 0.92.2 and 0.92.1 before. Let’s encrypt certificate is valid and I use duckdns but configured directly on my fritbox.

Error doing job: SSL handshake failed
Traceback (most recent call last):
File “uvloop/sslproto.pyx”, line 500, in uvloop.loop.SSLProtocol._on_handshake_complete
File “uvloop/sslproto.pyx”, line 484, in uvloop.loop.SSLProtocol._do_handshake
File “/usr/local/lib/python3.7/ssl.py”, line 763, in do_handshake
self._sslobj.do_handshake()
ssl.SSLError: [SSL: SSLV3_ALERT_CERTIFICATE_UNKNOWN] sslv3 alert certificate unknown (_ssl.c:1056)

How could I fix it?

antonholmstedt · May 17, 2019, 4:03pm

I’ve got the exact same problem! Have you found any solution?

B1G · May 17, 2019, 5:21pm

Unfortunatly not

galewis · May 18, 2019, 5:25pm

Mentioned above, but these are the specific steps that worked for me:

In configuration.yaml rem out any references to base_url. Save.
Stop the duck dns add on and disable auto-run at boot
Restart. I waited 5-10 mins to give the system a chance to fully initialize.
Re-enable duckdns
Un-rem base_url
Restart

Martino · June 3, 2019, 8:35pm

+1 on the issue. @galewis solution didn’t work for me unfortunately and neither did @igorovich664’s solution . However, my problems started to occur when I switch ISP over the weekend, so I am guessing that might be the culprit somehow… just don’t know how to start digging into that.

galewis · June 3, 2019, 8:56pm

Make sure your DuckDNS updater is doing its job, updating their servers with your new IP address.

Koen · August 11, 2019, 7:43pm

Hi there,

I had the same issue. It occurd to me that I had a Duck-DNS token for two years.
I was getting these error messages in the log file and I only could access the UI by using the “https://ip-of-HomeAssistant”

2019-08-11 21:30:28 ERROR (MainThread) [homeassistant.core] Error doing job: SSL error errno:1 reason: SSLV3_ALERT_CERTIFICATE_UNKNOWN
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: SSLV3_ALERT_CERTIFICATE_UNKNOWN] sslv3 alert certificate unknown (_ssl.c:841)

I solved the issue by renewing the token at https://duckdns.org and plugging this into the settings, restarting duckdns + ssl addon and it fixed all issues. Now I can access my UI again.
Guess there happens something weird when a token is being used for 2 years.

Hope this can help others.

Cheers!

haqwin · August 13, 2019, 7:46pm

Having the same issue from today on my home assistant on rasbian, stopped working without warning. Obviously the DuckDNS updater is working since the error occur for each request done from the outside. When the error appeared:

No updates were done (currently running 0.96.5).
Plenty of time left on my Certs for let’s encrypt (october).
The DuckDNS token was around a year old.

To be on the safe side>

I updated the token from DuckDNS and in config (as @Koen suggested)
Renewed the cert as well (now valid to nov 11)
Restarted my rPi a number of times

Only way in from the outside is now via HA Cloud and on the inside with the direct IP number

Any suggestions?

Koen · August 14, 2019, 7:17am

Hi,

Sorry to hear that my recommendation did not work, but I am not an expert on this platform however. Do you have a log which can tell something more that is happening inside Hassio?

Cheers

haqwin · August 15, 2019, 10:39am

Thanks for the input @Koen.

Today, it was all back to normal without any more changes. Now I can’t recreate the issue. Seems there was something odd going on outside of my control.

The error that appeared in my log for each call to home assistant via DuckDNS was:

2019-08-13 20:07:38 ERROR (MainThread) [homeassistant.core] Error doing job: SSL handshake failed                     
Traceback (most recent call last):                                                                                    
  File "/usr/local/lib/python3.7/asyncio/sslproto.py", line 625, in _on_handshake_complete                            
    raise handshake_exc                                                                                               
  File "/usr/local/lib/python3.7/asyncio/sslproto.py", line 189, in feed_ssldata                                      
    self._sslobj.do_handshake()                                                                                       
  File "/usr/local/lib/python3.7/ssl.py", line 763, in do_handshake                                                   
    self._sslobj.do_handshake()                                                                                       
ssl.SSLError: [SSL: SSLV3_ALERT_CERTIFICATE_UNKNOWN] sslv3 alert certificate unknown (_ssl.c:1056)

So basically the exact same as yours. I think it’s an outside issue with DuckDNS sending incorrect data when redirecting, something out of my control. That solution working might have been pure coincidence.

Ah well, I guess I’ll never know