David Sanner - I'm seeing an issue with signalk...
I'm seeing an issue with signalk-server-setup when configuring for SSL. It's creating 1024 bit certs which recent node version take issue with its short length. Maybe update to 2048 if anyone else is seeing this issue? I can open Issue on github if others are seeing this.
9 Replies
What kind of issues it repors?
I just enabled ssl to clean SK install running node v22 and no issues seen. Key lenght 1024 bit.
I couldn't get it to startup after running signalk-server-setup and having it setup the config & generate the cert.
(this is with and existing install) Logs show....
TypeError: Cannot read properties of undefined (reading 'private')
at /usr/local/lib/node_modules/signalk-server/lib/security.js:171:47
at /usr/local/lib/node_modules/signalk-server/node_modules/selfsigned/index.js:196:16
at RsaKeyPairGenJob.<anonymous> (/usr/local/lib/node_modules/signalk-server/node_modules/node-forge/lib/rsa.js:949:11)
at job.ondone (node:internal/crypto/keygen:95:5)
Then seeing this repeating a few times.:
TypeError: Cannot read properties of undefined (reading 'ws')
at Timeout._onTimeout (/usr/local/lib/node_modules/signalk-server/lib/deltastats.js:60:46)
at listOnTimeout (node:internal/timers:569:17)
at process.processTimers (node:internal/timers:512:7)
----
However after the setup I replaced the cert with my own 2048b cert (no other changes) and it starts up fine. Maybe just with my setup (node v18.19.0 / rpi, latest debian, fully patched)
Can you disable ssl and remove cert&key, reboot and enable it from GUI. Is it working then?
I'd be happy to try just don't see how to enable ssl via gui (Under gui server->settings I see "The server was started by systemd, run signalk-server-setup to change ports and ssl configuration")
Toggle switch can be found here.
Server -> Settings -> Server Settings -> Options -> ssl (toggle ON/OFF) -> Hit Save button and restart
Thanks... but I don't seem to have that setting (Signal K Server version 2.13.5)
Should be there, one below. Has been there for ages.
Odd, this must be something w/ my install. Running node v18.19.0. I cleared my settings.json and then my security.json, restarted, no change. Went ahead and tried 'npm install -g signalk-server' but no luck their either. I remember seeing it ... but it's been ages.
Mystery ... but looks like it's something w/ my install/setup. With the recent changes to Kip supporting relative url in the embeds I'm ok w/o running ssl so unless there are ideas of what I could do to test or check with my install we can file this in that "that's odd" bin. Thx.