You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: