NodeJS >= 16 Incompatible With AMT TLS; Document This!

[rothn]

It's probably worth adding a note that people need to use nodejs <= 16 in order to connect to AMT when TLS is enabled. Otherwise, I would get errors. It took me awhile to figure this out.

TCP disconnected with error from 192.168.50.148:16993: ERR_SSL_UNSAFE_LEGACY_RENEGOTIATION_DISABLED, /webrelay.ashx/.websocket?p=1&host=192.168.50.148&port=16993&tls=1&tls1only=0
TCP disconnected from 192.168.50.148:16993.
Opening web socket connection to 192.168.50.148:16993.
TCP disconnected with error from 192.168.50.148:16993: ERR_SSL_NO_PROTOCOLS_AVAILABLE, /webrelay.ashx/.websocket?p=1&host=192.168.50.148&port=16993&tls=1&tls1only=1
TCP disconnected from 192.168.50.148:16993.
Opening web socket connection to 192.168.50.148:16993.
... (repeated)

[si458]

this was already fixed in meshcentral when we upgraded to node 18 (now testing with node 24)
meshcommander is not really active anymore but i do think this was already fixed also?
e56b9c0
have you tried the latest 0.9.7 version of meshcommander? https://meshcentral.com/meshcommander/MeshCommander-0.9.7.msi

[supersej]

To me MeshCommander 0.9.7 works fine with TLS
But MeshCommanderFirmware 0.9.5 can't connect and I therefor have no succes in installing the MeshCommander firmware on my system.

[si458]

@supersej I have new source code which means I might be able to build the firmware! Please give me a few days then pole me and I'll send what I find/compile etc!

[supersej]

Hi again @si458

any luck with the firmware build? 😊

[Simon1511]

Any news on this?