STUN and TURN Server












0















I have developed a webrtc based video chat using peerjs. The solution is working fine but some users are facing problem to establish the call. I guess it is due to NAT and firewall issues.



I have user peerjs as :



var peer = new Peer({host: myserver.com], port: 9000, debug: true});


I have changed the code to [passed google stun] as seen here : =



Still the same issue. Some user can not connect to peer id. Am I doing something wrong?










share|improve this question

























  • What you have done @selbie

    – Ashika
    Nov 25 '18 at 10:13











  • I indented your line of javascript such it appears as a code block. It makes the question much more readable.

    – selbie
    Nov 25 '18 at 19:56











  • Also, welcome to the world of P2P and WebRTC, where rarely anything "just works". Issues like, "why can't I reliably connect" aren't going to be solved by someone inspecting one line of javascript. It could be a NAT issue. Could be an issue with another peer. Either way, you may have to debug very hard with tools such as Wireshark and Fiddler to understand the flow of your network traffic.

    – selbie
    Nov 25 '18 at 19:59











  • Yes, I'm new to this. For NAT issues, everyone is saying to implement/add the STUN and TURN server. But I dunno how to add this. Could you please tell me how to resolve this issue. @selbie

    – Ashika
    Nov 26 '18 at 5:05











  • Using port 9000 may be your problem, as it may not be accessible due to firewall rules. I presume you have your own peerjs server not at 'myserver.com' but some other address?

    – Mikkel
    Dec 30 '18 at 4:53
















0















I have developed a webrtc based video chat using peerjs. The solution is working fine but some users are facing problem to establish the call. I guess it is due to NAT and firewall issues.



I have user peerjs as :



var peer = new Peer({host: myserver.com], port: 9000, debug: true});


I have changed the code to [passed google stun] as seen here : =



Still the same issue. Some user can not connect to peer id. Am I doing something wrong?










share|improve this question

























  • What you have done @selbie

    – Ashika
    Nov 25 '18 at 10:13











  • I indented your line of javascript such it appears as a code block. It makes the question much more readable.

    – selbie
    Nov 25 '18 at 19:56











  • Also, welcome to the world of P2P and WebRTC, where rarely anything "just works". Issues like, "why can't I reliably connect" aren't going to be solved by someone inspecting one line of javascript. It could be a NAT issue. Could be an issue with another peer. Either way, you may have to debug very hard with tools such as Wireshark and Fiddler to understand the flow of your network traffic.

    – selbie
    Nov 25 '18 at 19:59











  • Yes, I'm new to this. For NAT issues, everyone is saying to implement/add the STUN and TURN server. But I dunno how to add this. Could you please tell me how to resolve this issue. @selbie

    – Ashika
    Nov 26 '18 at 5:05











  • Using port 9000 may be your problem, as it may not be accessible due to firewall rules. I presume you have your own peerjs server not at 'myserver.com' but some other address?

    – Mikkel
    Dec 30 '18 at 4:53














0












0








0








I have developed a webrtc based video chat using peerjs. The solution is working fine but some users are facing problem to establish the call. I guess it is due to NAT and firewall issues.



I have user peerjs as :



var peer = new Peer({host: myserver.com], port: 9000, debug: true});


I have changed the code to [passed google stun] as seen here : =



Still the same issue. Some user can not connect to peer id. Am I doing something wrong?










share|improve this question
















I have developed a webrtc based video chat using peerjs. The solution is working fine but some users are facing problem to establish the call. I guess it is due to NAT and firewall issues.



I have user peerjs as :



var peer = new Peer({host: myserver.com], port: 9000, debug: true});


I have changed the code to [passed google stun] as seen here : =



Still the same issue. Some user can not connect to peer id. Am I doing something wrong?







webrtc stun turn peerjs






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 25 '18 at 5:49









selbie

55.3k1061121




55.3k1061121










asked Nov 24 '18 at 8:30









AshikaAshika

186




186













  • What you have done @selbie

    – Ashika
    Nov 25 '18 at 10:13











  • I indented your line of javascript such it appears as a code block. It makes the question much more readable.

    – selbie
    Nov 25 '18 at 19:56











  • Also, welcome to the world of P2P and WebRTC, where rarely anything "just works". Issues like, "why can't I reliably connect" aren't going to be solved by someone inspecting one line of javascript. It could be a NAT issue. Could be an issue with another peer. Either way, you may have to debug very hard with tools such as Wireshark and Fiddler to understand the flow of your network traffic.

    – selbie
    Nov 25 '18 at 19:59











  • Yes, I'm new to this. For NAT issues, everyone is saying to implement/add the STUN and TURN server. But I dunno how to add this. Could you please tell me how to resolve this issue. @selbie

    – Ashika
    Nov 26 '18 at 5:05











  • Using port 9000 may be your problem, as it may not be accessible due to firewall rules. I presume you have your own peerjs server not at 'myserver.com' but some other address?

    – Mikkel
    Dec 30 '18 at 4:53



















  • What you have done @selbie

    – Ashika
    Nov 25 '18 at 10:13











  • I indented your line of javascript such it appears as a code block. It makes the question much more readable.

    – selbie
    Nov 25 '18 at 19:56











  • Also, welcome to the world of P2P and WebRTC, where rarely anything "just works". Issues like, "why can't I reliably connect" aren't going to be solved by someone inspecting one line of javascript. It could be a NAT issue. Could be an issue with another peer. Either way, you may have to debug very hard with tools such as Wireshark and Fiddler to understand the flow of your network traffic.

    – selbie
    Nov 25 '18 at 19:59











  • Yes, I'm new to this. For NAT issues, everyone is saying to implement/add the STUN and TURN server. But I dunno how to add this. Could you please tell me how to resolve this issue. @selbie

    – Ashika
    Nov 26 '18 at 5:05











  • Using port 9000 may be your problem, as it may not be accessible due to firewall rules. I presume you have your own peerjs server not at 'myserver.com' but some other address?

    – Mikkel
    Dec 30 '18 at 4:53

















What you have done @selbie

– Ashika
Nov 25 '18 at 10:13





What you have done @selbie

– Ashika
Nov 25 '18 at 10:13













I indented your line of javascript such it appears as a code block. It makes the question much more readable.

– selbie
Nov 25 '18 at 19:56





I indented your line of javascript such it appears as a code block. It makes the question much more readable.

– selbie
Nov 25 '18 at 19:56













Also, welcome to the world of P2P and WebRTC, where rarely anything "just works". Issues like, "why can't I reliably connect" aren't going to be solved by someone inspecting one line of javascript. It could be a NAT issue. Could be an issue with another peer. Either way, you may have to debug very hard with tools such as Wireshark and Fiddler to understand the flow of your network traffic.

– selbie
Nov 25 '18 at 19:59





Also, welcome to the world of P2P and WebRTC, where rarely anything "just works". Issues like, "why can't I reliably connect" aren't going to be solved by someone inspecting one line of javascript. It could be a NAT issue. Could be an issue with another peer. Either way, you may have to debug very hard with tools such as Wireshark and Fiddler to understand the flow of your network traffic.

– selbie
Nov 25 '18 at 19:59













Yes, I'm new to this. For NAT issues, everyone is saying to implement/add the STUN and TURN server. But I dunno how to add this. Could you please tell me how to resolve this issue. @selbie

– Ashika
Nov 26 '18 at 5:05





Yes, I'm new to this. For NAT issues, everyone is saying to implement/add the STUN and TURN server. But I dunno how to add this. Could you please tell me how to resolve this issue. @selbie

– Ashika
Nov 26 '18 at 5:05













Using port 9000 may be your problem, as it may not be accessible due to firewall rules. I presume you have your own peerjs server not at 'myserver.com' but some other address?

– Mikkel
Dec 30 '18 at 4:53





Using port 9000 may be your problem, as it may not be accessible due to firewall rules. I presume you have your own peerjs server not at 'myserver.com' but some other address?

– Mikkel
Dec 30 '18 at 4:53












0






active

oldest

votes











Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53456493%2fstun-and-turn-server%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes
















draft saved

draft discarded




















































Thanks for contributing an answer to Stack Overflow!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53456493%2fstun-and-turn-server%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Wiesbaden

Marschland

Dieringhausen