-
-
Notifications
You must be signed in to change notification settings - Fork 971
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
simple-peer won't connect when clients are not in the same network #929
Comments
sample OFFER: sample ANSWER: |
Your ice-server credentials seem to be the issue. I am using the turn server from open-relay. It works on different networks as well. This is not the issue with the simple-peer library. |
thanks |
This error occurs when clients are in different networks: in this method: |
Can you share the code with me? I can check with my credentials and test the issue? |
Sure this a simplified version, without any Server URL for initaiator: URL for other peer: Steps:
TURN Server urls are from free plan of "metered.ca" Thanks a lot |
link to the sample html file: |
You can give https://github.com/matallui/artico a try! The |
Thanks |
@omidshakeri gotcha! I believe neither this nor peerJS are actively maintained anymore. Hence why I started Artico in the first place, to try to expand on these projects. If you give Artico a try let me know. I’d love to get some feedback on how to improve. |
It will be OK if you add a available STUN server address in |
Thanks |
Hi @omidshakeri, I'm getting into your trouble! Can you give me your solution? Thanks for replay ! |
I switched to PeerJS and it works perfectly with the |
Oh, can you share me your repo ? |
simple-peer won't connect when clients are not in the same network
It works perfectly if both clients are in the same network (connected to the same modem/WiFi)
but even after setting iceServers, the connection is not working
one of many iceServers configs that I have tested:
config: { iceServers: [ { urls: 'stun:stun.l.google.com:19302' }, { urls: 'stun:stun1.l.google.com:19302' }, { urls: 'stun:stun2.l.google.com:19302' }, { urls: 'stun:stun3.l.google.com:19302' }, { urls: 'stun:stun4.l.google.com:19302' }, { url: 'turn:turn.bistri.com:80', credential: 'homeo', username: 'homeo', }, { url: 'turn:turn.anyfirewall.com:443?transport=tcp', credential: 'webrtc', username: 'webrtc', } ] },
am I doing anything wrong?
is there any other configurations that someone is using without problems, so can help me?
The text was updated successfully, but these errors were encountered: