-
-
Notifications
You must be signed in to change notification settings - Fork 120
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
public signaling servers down? #43
Comments
The demo here isn't working https://docs.yjs.dev/getting-started/a-collaborative-editor Why the wontfix tag? |
I accidentally added it and I can't seem to remove it. But the demo is working on the website on the website, right? On stackblitz I get errors though. |
I get the same errors.. Probably some heroku foo 🥲 |
Also bitten by this. Time to set up independent servers it seems.. |
Hey! We also have a problem with that - it's not critical for us as we've used that only for some local development and we are in the middle of migrating to private signaling server. But I guess could be nice to resolve if feasible 😄 As for having a private signaling server, there is an example server in ./bin folder, which works fine and I think can be used out of the box. Thanks for your hard work on this library! |
Yes, booting the server on e.g. scalingo.com is very easy :) |
Sorry for the long wait. I couldn't decide on the next server after switching several times because they all went broke / failed regularly / changed focus. I went with fly.io. I'm sorry fly.io, because of my luck you will probably go down as well. |
Not sure if this is worth opening a new issue, but it seems y-webrtc-eu.fly.dev is down? |
Not bad luck, Fly.io was never very reliable to begin with. |
Hallo,
My app cannot connect to ['wss://signaling.yjs.dev', 'wss://y-webrtc-signaling-eu.herokuapp.com', 'wss://y-webrtc-signaling-us.herokuapp.com']
A few weeks back this wasn't the case.
Code used:
I would like to deploy my own signaling server but find the tuturial to be unclear. Could anyone help me with this?
The text was updated successfully, but these errors were encountered: