Socket.io Error 400

#1

Hello,

after an upgrade to 1.0.10 see plenty of 'Disconnected …" messages and new comment added to a ticket do not show up unless a page reload is forced.

No errors in TruDesk console.

Chrome Console:
Failed to load resource: the server responded with a status of 400 (Bad Request)
index.js:83 WebSocket connection to ‘ws://10.0.0.21/socket.io/?EIO=3&transport=websocket&sid=TGbK6xVdF-73FWJEAAAD’ failed: Error during WebSocket handshake: Unexpected response code: 400
r.doOpen @ index.js:83
socket.io/?EIO=3&transport=polling&t=MfgbFte&sid=TGbK6xVdF-73FWJEAAAD:1 Failed to load resource: the server responded with a status of 400 (Bad Request)
index.js:83 WebSocket connection to ‘ws://10.0.0.21/socket.io/?EIO=3&transport=websocket&sid=cwkaEBJk8_aE1CPhAAAB’ failed: Error during WebSocket handshake: Unexpected response code: 400

So it seems socket.io is somehow broken. The TruDesk Debian installation runs in VMware Workstation and I access it from the VMware host (Windows 2019).

What would you recommend to fix the socket.io issue ?

Many thanks,

Pummelchen

#2

Do a yarn run build

#3

Yep, done that with the Node 12.1.0 upgrade, still the same errors in Chrome console. Hmm …

#4

Ok, found it, its the old problem that node under Linux cannot use port 80 or ports in the lower range without little tricks. Using high port works just fine. Forgot about that :slight_smile: