SSL Errors wrong version number?

Configuration
1

Running Hassio and Duckdns. I’m getting these errors - any ideas?:

Mon Nov 12 2018 11:11:22 GMT+0000 (Greenwich Mean Time)

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)


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: WRONG_VERSION_NUMBER] wrong version number (_ssl.c:841)
2

Same here. Several versions now. A lot of these posts in the forum without answers @balloob. Any pointers?? Intermediate don’t work.

3

Same here!

Solution?

4

Nothing yet - everything seems to work for me (as in I can access from outside my network) but in reality, I have no idea how secure I am!

5

Hi there.

@ThePapaMaan @AcidSleeper I think i have found out the problem.
Fist deactivate the Multi-factor Authentication Modules on the GUI. Then setup everything for SSL. And then activate again the Multi-factor Authentication Modules. Then it works like a charm.
My suggestion is that the generated QR Code has the http: link inside and not the https:.
Does it work for you guys?

6

Not sure I get you?? I don’t even have multi factor running.

1 Like
7

No I dont have that!

8

I don’t use MFA (yet). Still getting the errors with 83.2. Nothing in 83.3 hints to any fix related to ssl.

9

I have the same errors, seems to have started around version 83.

10

The same issue here. Version 83.3, no MFA running.

11

Hello guys!

All my SSL errors has stop after installing the addon NGINX. I believe these errors came from local machines accessing Hassio over a browser using HTTPS. Since there is no certificate on LAN I’ve always got errors on Chrome.

Please give it a try! Just install NGINX, use this settings:

{
  "domain": "yourddns.duckdns.org",
  "certfile": "fullchain.pem",
  "keyfile": "privkey.pem",
  "hsts": "max-age=31536000; includeSubDomains",
  "customize": {
    "active": false,
    "default": "nginx_proxy_default*.conf",
    "servers": "nginx_proxy/*.conf"
  }
}

Don’t forget to take these lines out from the http component:

#ssl_certificate: /ssl/fullchain.pem
#ssl_key: /ssl/privkey.pem

Don’t worry, it takes a long time to start the addon for the first time. Like 2 to 5 minutes, just wait for it.

You can now access your local HASSIO machine without HTTPS and still use SSL outside your home network.

Works great now, good luck!

1 Like
12

After NGINX installation I’ve entered your config where I’ve changed duckdns address only.
When I pressed save, this error message popped up above the setting window:

not a valid value for dictionary value @ data['options']. Got {'domain': 'myweb.duckdns.org', 'certfile': 'fullchain.pem', 'keyfile': 'privkey.pem', 'hsts': 'max-age=31536000; includeSubDomains', 'customize': {'active': False, 'default': 'nginx_proxy_default*.conf', 'servers': 'nginx_proxy/*.conf'}}

And this warnig in the HASSIO Syslem log:

19-01-06 06:59:47 WARNING (MainThread) [hassio.addons.validate] Unknown options domain
19-01-06 06:59:47 WARNING (MainThread) [hassio.addons.validate] Unknown options certfile
19-01-06 06:59:47 WARNING (MainThread) [hassio.addons.validate] Unknown options keyfile
19-01-06 06:59:47 WARNING (MainThread) [hassio.addons.validate] Unknown options hsts
19-01-06 06:59:47 WARNING (MainThread) [hassio.addons.validate] Unknown options customize
13

Hello sir! Have you commented the lines about ssl certificates on HTTP component?

#ssl_certificate: /ssl/fullchain.pem
#ssl_key: /ssl/privkey.pem
14

Gave that a blast and ended up with no GUI :frowning:
CORRECTION - could only access locally

15

Hello. That is odd. Have checked your syntax? No errors? These lines does not brake the GUI, only HTTP SSL certificates. Can you access it over LAN? Is your NGINX server running?

16

Should I continue to have the duckdns add-on running too?

17

Yes sir. It needs to create the certificates but NGINX will now handle them.

18

I just restored, so I’ll give it another blast.

19

So I can access it locally, but not using the duckdns url?

20

Getting this error in the logs:

Traceback (most recent call last):
  File "/usr/local/lib/python3.6/site-packages/aiohttp/web_protocol.py", line 242, in data_received
    messages, upgraded, tail = self._request_parser.feed_data(data)
  File "aiohttp/_http_parser.pyx", line 523, in aiohttp._http_parser.HttpParser.feed_data
aiohttp.http_exceptions.BadStatusLine: invalid HTTP method