NorDroN / homebridge-wideq

MIT License
12 stars 5 forks source link

SSL error (Error: SSL routines:ssl_choose_client_version:unsupported protocol) during wideq auth step #7

Closed canadaohcanada closed 4 years ago

canadaohcanada commented 4 years ago

Howdy, I am unable to proceed with this system due to an SSL issue. Could this be caused by TLS improvements in node 12.x? Any support you can offer is greatly appreciated as this project will really round out my HomeKit setup.

/homebridge # node -v
v12.16.1
/homebridge # wideq auth
Log in here: https://us.m.lgaccount.com/login/sign_in?country=US&language=en-US&svcCode=SVC202&authSvr=oauth2&client_id=LGAO221A02&division=ha&grant_type=password
Then paste the URL where the browser is redirected: https://us.m.lgaccount.com/login/iabClose?access_token= access_token_was_here&refresh_token=refresh_token_was_here&oauth2_backend_url=https://us.lgeapi.com/
(node:6669) UnhandledPromiseRejectionWarning: Error: write EPROTO 140638656777544:error:1425F102:SSL routines:ssl_choose_client_version:unsupported protocol:../deps/openssl/openssl/ssl/statem/statem_lib.c:1929:

    at WriteWrap.onWriteComplete [as oncomplete] (internal/stream_base_commons.js:92:16)
(node:6669) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)
(node:6669) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
/homebridge # npm list
/homebridge
+-- homebridge-camera-ffmpeg@0.1.14
| +-- debug@2.6.9
| | `-- ms@2.0.0
| +-- googleapis@48.0.0
| | +-- google-auth-library@5.10.1
| | | +-- arrify@2.0.1
| | | +-- base64-js@1.3.1
| | | +-- ecdsa-sig-formatter@1.0.11
| | | | `-- safe-buffer@5.2.0
| | | +-- fast-text-encoding@1.0.1
| | | +-- gaxios@2.3.2
| | | | +-- abort-controller@3.0.0
| | | | | `-- event-target-shim@5.0.1
| | | | +-- extend@3.0.2 deduped
| | | | +-- https-proxy-agent@5.0.0
| | | | | +-- agent-base@6.0.0
| | | | | | `-- debug@4.1.1
| | | | | |   `-- ms@2.1.2
| | | | | `-- debug@4.1.1
| | | | |   `-- ms@2.1.2
| | | | +-- is-stream@2.0.0
| | | | `-- node-fetch@2.6.0
| | | +-- gcp-metadata@3.5.0
| | | | +-- gaxios@2.3.2 deduped
| | | | `-- json-bigint@0.3.0
| | | |   `-- bignumber.js@7.2.1
| | | +-- gtoken@4.1.4
| | | | +-- gaxios@2.3.2 deduped
| | | | +-- google-p12-pem@2.0.4
| | | | | `-- node-forge@0.9.1
| | | | +-- jws@4.0.0 deduped
| | | | `-- mime@2.4.4
| | | +-- jws@4.0.0
| | | | +-- jwa@2.0.0
| | | | | +-- buffer-equal-constant-time@1.0.1
| | | | | +-- ecdsa-sig-formatter@1.0.11 deduped
| | | | | `-- safe-buffer@5.2.0 deduped
| | | | `-- safe-buffer@5.2.0 deduped
| | | `-- lru-cache@5.1.1
| | |   `-- yallist@3.1.1
| | `-- googleapis-common@3.2.2
| |   +-- extend@3.0.2
| |   +-- gaxios@2.3.2 deduped
| |   +-- google-auth-library@5.10.1 deduped
| |   +-- qs@6.9.1
| |   +-- url-template@2.0.8
| |   `-- uuid@7.0.2
| `-- ip@1.1.5
+-- homebridge-dummy@0.4.1
| `-- node-persist@2.1.0
|   +-- is-absolute@0.2.6
|   | +-- is-relative@0.2.1
|   | | `-- is-unc-path@0.1.2
|   | |   `-- unc-path-regex@0.1.2
|   | `-- is-windows@0.2.0
|   +-- mkdirp@0.5.3
|   | `-- minimist@1.2.5
|   `-- q@1.1.2
`-- wideq@1.1.1       ***** I've also attempted installing this globally, but with no luck
  +-- axios@0.19.2
  | `-- follow-redirects@1.5.10
  |   `-- debug@3.1.0
  |     `-- ms@2.0.0
  +-- commander@3.0.2
  +-- debug@4.1.1
  | `-- ms@2.1.2
  +-- lodash@4.17.15
  +-- luxon@1.22.0
  +-- qs@6.9.1
  `-- uuid@3.4.0
canadaohcanada commented 4 years ago

Closing, this issue was solved by changing installed node version to 10.x.