Websocket on localhost:30035 should be accessible using the daemon debug web server (available in moolticute settings) and external tools such as wscat.
Actual behavior
Moolticute communicates with the daemon fine but no other tool can seem to. When using wscat the websocket immediately hangs up. Using the moolticute debug server you just see errors being logged simply saying "CLOSED".
Expected behavior
Websocket on localhost:30035 should be accessible using the daemon debug web server (available in moolticute settings) and external tools such as wscat.
Actual behavior
Moolticute communicates with the daemon fine but no other tool can seem to. When using wscat the websocket immediately hangs up. Using the moolticute debug server you just see errors being logged simply saying "CLOSED".![image](https://github.com/mooltipass/moolticute/assets/88934620/be303c08-780c-4e1b-82c5-15678e856f91)
Step by step guide to reproduce the problem
Moolticute Version
v1.01.0
Operating System
Windows 10
Mooltipass Device
Mooltipass Mini BLE