Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WebRTC signaling servers cannot be reached #19

Open
almereyda opened this issue Jul 4, 2024 · 0 comments
Open

WebRTC signaling servers cannot be reached #19

almereyda opened this issue Jul 4, 2024 · 0 comments

Comments

@almereyda
Copy link

almereyda commented Jul 4, 2024

Describe the bug

Intruige uses the embedded URLs for the signaling servers, of which many have disappeared or do not have a CSP configuration which would allow usage.

This results in failing connections between peers.

To Reproduce

  1. Open a board and its developer tools
  2. Open it in a private browser windows
  3. See errors appear in the console and in the network tab

Expected behavior

There are no errors and the clients are synced.

Additional context

It's best to run one's own signalling server. The demo instance is known to be weak and not for productive use. There are two known options, the JS one and another in Rust linked from yjs/y-webrtc#55

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant