blaze icon indicating copy to clipboard operation
blaze copied to clipboard

Published 20 hours ago • verified publisher icon blenderskool

WebRTC not working across different networks

Open blenderskool opened this issue 6 years ago • 5 comments

WebRTC works when the clients are in same network, but fails (switches to WebSockets) when they are in different networks.

blenderskool avatar Jan 07 '19 13:01 blenderskool

This is most likely because there is no TURN server being used.

blenderskool avatar Sep 12 '20 15:09 blenderskool

This is most likely because there is no TURN server being used.

Yeah that's one possibility. Second is ICE fails a lot in firefox. Do you possibly use firefox?

RotonEvan avatar Oct 20 '20 03:10 RotonEvan

@RotonEvan No not using Firefox right now

blenderskool avatar Oct 20 '20 03:10 blenderskool

Can I use a TURN server within blaze? I have coturn up and running as my nextcloud talk module needs a TURN server for compatibility reasons.

elearningdienst avatar Nov 23 '21 20:11 elearningdienst

@elearningdienst Yes it is possible to use a coturn server with Blaze. You'll have to add your TURN server details to this file, and rebuild Blaze client app https://github.com/blenderskool/blaze/blob/61998dd02bd1d47d011f1ce6ace0a2c9747cbf63/client/src/utils/fileShare.js#L17

blenderskool avatar Feb 12 '22 09:02 blenderskool

Closing this as this is not a problem with Blaze. To ensure WebRTC works across all networks, a TURN server needs to be configured which can be done using coturn in case anyone is interested in self-hosting.

blenderskool avatar Jul 14 '23 14:07 blenderskool