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

apprtc websocket server down? #602

Open
fippo opened this Issue Jan 7, 2019 · 9 comments

Comments

Projects
None yet
4 participants
@fippo
Copy link
Contributor

fippo commented Jan 7, 2019

currently getting websocket timeouts, the red box says

WebSocket open error: WebSocket error
WebSocket register error: WebSocket error

after a while (~30s - 60s). @ggarber can see the same.

@MirkoBonadei @KaptenJansson can you please take a look? @juberti said there were cert errors recently.

@fippo

This comment has been minimized.

Copy link
Contributor Author

fippo commented Jan 7, 2019

and its back up. You might still want to investigate why.

@NeelamParmar

This comment has been minimized.

Copy link

NeelamParmar commented Jan 9, 2019

Hello,

I am facing same issue .

It shows "Firefox can’t establish a connection to the server at wss://apprtc-ws.webrtc.org/ws."
The wss server is down.

Could you please let us know is there any update on this ? Or is there any alternative which could be used for wss server ?

Could we create our own wss server ?

Thanks

@fippo

This comment has been minimized.

Copy link
Contributor Author

fippo commented Jan 9, 2019

@NeelamParmar if you run apprtc in production you should absolutely run your own signaling server. apprtc uses https://github.com/webrtc/apprtc/tree/master/src/collider

@NeelamParmar

This comment has been minimized.

Copy link

NeelamParmar commented Jan 9, 2019

Ok, thank you .

I will check it out .

@NeelamParmar

This comment has been minimized.

Copy link

NeelamParmar commented Jan 9, 2019

Collider is created using Go, can we create signaling server using node.js ?

@fippo

This comment has been minimized.

Copy link
Contributor Author

fippo commented Jan 9, 2019

there are a bunch of nodejs signaling servers, but they use a different protocol than apprtc.

@NeelamParmar

This comment has been minimized.

Copy link

NeelamParmar commented Jan 9, 2019

ohh ok.
It means we need to use only collider with Apprtc ? Others won't work with it as protocols are different ?

@brianpeiris

This comment has been minimized.

Copy link

brianpeiris commented Jan 24, 2019

Just wanted to report that the websocket server is down again. Timeout connecting to wss://apprtc-ws.webrtc.org/ws

@elixiroflife4u

This comment has been minimized.

Copy link

elixiroflife4u commented Jan 24, 2019

I am not hitting websocket timeouts persay, but it seems something really strange is going on with the webserver. The loopback calls in the Android Apprtc demo app are failing to connect since the offer gets sent to some abyss.
Edit: it seems to be working again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment