Peer connection failed but no log #243
Comments
|
Hey guidtz, if spreed-webrtc server doesn't log an issue, it's always a good idea to consult your browser's dev console. Pretty sure it will contain valuable information for us to debug the issue :) |
|
Hi, I have got a lot of errors My mistake or something wrong ? Thanks |
|
Hi, it seems that you have no STUN or TURN server configured. If no direct peer connection is possible, then a STUN and in some cases a TURN server is required to relay peer connections between those networks. I see two different networks in your candidate logs: 192.168.1.10 and 192.168.122.1 - if there is no routing or a firewall between these two, the peerconnection will fail after all candidates have timed out. If you add a TURN server to the Spreed webrtc configuration both peers will also offer relay candidates which then might succeed. See https://github.com/coturn/rfc5766-turn-server/ for a TURN server implementation if you want to setup your own on a server which is reachable from both parties (usually somewhere in the Internet). Cheers |
|
Ok I add a turn server in the server with debian package and add this in my server.conf but I have same problems. 192.168.1.10 and 192.168.122.1 are local ip of my computer |
|
Err yeah, well this is not exactly correct. The TURN server must be reachable directly by both peers (from both networks). Configuring it as 127.0.0.1 will not work - it must be in some other network, usually world routeable/external to make sense. You wrote above 2 desktops in different networks. Both of these networks need to be able to reach the same TURN server. When setting up the TURN server make also sure to use shared secrent authentication with it (turnSecret in server.conf) and use the same setting in the TURN configuration. |
|
In server.conf in /etc/turnserver.conf Or do you have example of conf file ? Sorry for my lack of education in webrtc and turnserver it's the first time I make this type of server but if it can work with owncloud it will be a good thing and after i'll make a documentation for replicating this install. Cheers |
|
That basically looks good. It is recommended to run the turn server on port 443 to get best firewall trespassing. Also add turn:public_ip:3478?transport=tcp as well to also support those which cannot use UDP. server.conf: in turnserver.conf Something like this is recommended. Second public IP and TLS is recommended to get best firewall trespassing support. |
|
very very very good ... it's work on non ssl for testing after I make it works on ssl port. so if we have apache and turn server how can we use the 443 port for both ? thanks a lot |
|
well, use a dedicated IP address for the TURN server and another one for Apache. Note that the usage of port 443 for TURN is not directly connected to SSL. TURN can do all protocols on the same port. It is merely the best port to cross firewalls as it is usually open/unfiltered. |
|
ok i'll learn this for production time. I'll go to test this. I close this issue thnaks for you're help |
Hello,
I installed spreed-webrtc to use with owncloud. But before to connect it to owncloud I want to test it. So I can run a spreed-webrtc server connect from 2 desktop on 2 different network, I can start a webconf but after a while (1mn) I have an error message : "Peer connection failed. Check your settings" but no logs for found where is the problem.
How can I debug this ?
The text was updated successfully, but these errors were encountered: