-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
EPROTO protocol error after updating nodejs #76
Comments
It seems telldus api only supports old and insecure TLSv1, and node v12 requires this. i have now fixed that in the code |
should be fixed in 1.0.6 |
I'm getting this: I'm using local configuration. Think it might be related? |
Yes! I messed up local api when fixing the https issue. have now fixed in newest version. |
Awesome! Thanks! Will test later today, I'll report back if there are any issues |
[Opening this as a new issue as I discovered I had commented it under another issue not really related... Hope that is okay!]
I had to update my Homebridge server on a RPi to Debian Buster.
And with that came the need to update:
Now, homebridge had to be updated also. so after completely uninstalled (as far as i can see):
...and finally all over again a complete new installation of
I thought it then was ready to rock. But unfortunately, even after re-doing the homebridge/homebride-telldus uninstall-install procedure twice, i was still stuck with the same problem:
`
`
Somewhere on the internet (cant find it again unfortunately) i read that the EPROTO 'unsupported protocol' error could be caused by that - while the minimal supported TLS version in previos versions of Node.js was TLSv1.0 - since v11.4.0, it is raised to TLSv1.2.
And if there is a certificate being used that is signed with TLSv1.0 this could be the root of the cause. Okay... so doing some more tests down that road, I tried to figure out how to start homebridge with the node flag
--tls-min-v1.0
forcing it to accept TLSv1.0 anyway.Now, node homebirdge seems to be launched from the homebridge shell script at
/usr/local/lib/node_modules/homebridge/bin
. But adding flags to env in a shebang under Linux seems not as easy. At least not under Debian.Fortunately, I also stumbled across this site http://sambal.org/2014/02/passing-options-node-shebang-line/
So, by hard coding
/usr/local/lib/node_modules/homebridge/bin/homebridge
to the following, it actually seems to work!!!!`
`
Of course, this was a dirty quick fix, not suitable for updates, but someone out there that are a true programmer might be able to look into the TLS-version problem? What part of homebridge-telldus needs to be updated to use protocol TLSv1.2 to be able to again access Telldus Live under under Node.js v11.4.0 and above?
The text was updated successfully, but these errors were encountered: