apprtc websocket server down?

[fippo]

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]

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

[NeelamParmar]

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]

@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]

Ok, thank you .

I will check it out .

[NeelamParmar]

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

[fippo]

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

[NeelamParmar]

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

[brianpeiris]

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

[elixiroflife4u]

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.

[KaptenJansson]

What happens is some client goes rogue or maliciously creates thousands of bogus TLS connections to the signalling server and it runs out of sockets. Once those timeout it works again. Load balancing between the two instances was broken due to a VM name change but that has been rectified. Not sure if that will help in this situation though.

[ArnavVashisthCodingAccountnew]

apprtc has been shutdown, according to their GitHub repository. Farewell , AppRTC

[fippo]

this has been overtaken by events indeed

[ArnavVashisthCodingAccountnew]

It has also shocked me

…

On Wed, Feb 23, 2022, 1:02 PM Philipp Hancke ***@***.***> wrote: this has been overtaken by events indeed — Reply to this email directly, view it on GitHub <#602 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ARUDRLDUQEHXN3M355OAUS3U4SERXANCNFSM4GOQVN7A> . You are receiving this because you commented.Message ID: ***@***.***>

[paragpatel]

If you are missing https://appr.tc/ , give a try to https://hub.docker.com/r/pegome/apprtc It has support for SSL and inbuilt TURN server.