Wrong websocket path

[rawtaz]

The websocket path is /socket.io in the source code but /whiteboard in the documentation.

The result of this is that the client fails to connect to the service, when configured according to the documentation/example.

I suggest changing the code so that it is using /whiteboard, as that makes more sense than /socket.io (in particular since there may be other services using websockets on the host in question, and it's therefore better to name the endpoints for what they are instead of by technology).

I also mentioned this earlier here ten days ago, perhaps that information is useful to those having problems getting it running.

[juliusknorr]

The documentation describes a scenario where the server is proxied behind the /whiteboard prefix which should work fine as the socket URL then becomes /whiteboard/socket.io. We have this working fine in multiple installations, so I'd be curious if you maybe missed adding the /whiteboard path to the configured server URL, e.g. https://cloud.example.com/whiteboard in the admin settings.

[KunaPrime]

i'm facing exact same issue, running nginx proxy, and i was able to solve it with this, but i assume this is not desirable solution at all

[brakhane]

i'm facing exact same issue, running nginx proxy, and i was able to solve it with this, but i assume this is not desirable solution at all

If you add a trailing slash to proxy_pass, eg. change proxy_pass http://localhost:3002; to proxy_pass http://localhost:3002/;, it should work even when using /whiteboard/ as a location.