Empty response when signalling and web on different servers

[korcanergun]

Hey,

When i use nodejs as web server and publish demos everything looks fine and working. But when i tried to move web files to another server im getting this error.

http://prntscr.com/8yjlca

i am setting socket url like connection.socketURL = 'http://webrtc.XXXXXX.XX:9001/';

Actually i tried but didn't find a solution for this. Can you check ?

Best Wishes, Korcan

[muaz-khan]

Make sure that port 9001 is permitted for both outgoing/incoming HTTP+HTTPs+TCP requests.

Replace this snippet v3.0/server.js#L80-L83:

app = app.listen(9001, process.env.IP || "0.0.0.0", function() {
    var addr = app.address();
    console.log("Server listening at", addr.address + ":" + addr.port);
});

PS. Don't use HTTP, because Chrome disabled getUserMedia capturing in the HTTP-based pages.

[korcanergun]

Hi, Port 9001 permitted to all requests. I converted HTTPS but right now im getting socket.io "Access-Control-Allow-Origin" problem. But i see in server file origin looks like ":"

Thanks for fast response. Do you have any idea about how to solve this problem ?

I searched google and i found "update socket io to 1.3.7 on serverside" . Still no differences. If i use your nodejs based http server everything looks fine. But when i move my HTML pages to web server (ps: using same domain. webrtc.xxxx.xx is my web and webrtc.xxxx.xx:9001 is signaling server) im getting access control error.

Also i added acces control origin header to response but still im getting this error based from socket.io

Thanks

[muaz-khan]

v3.0 is now having demo URL as well:

• https://rtcmulticonnection.herokuapp.com/

You can see how external servers (cross-domains) are using it:

• https://jsfiddle.net/zd9Lsdfk/

PS. Same code is deployed to heroku. Nothing is changed; and it is working.

[korcanergun]

For future problems im explaning my problem. I am using socket.io 1.3.7 on client side and rtcmulticonnection uses 0.9.16 . For that reason i have a problem .

After i installed 0.9.16 on client side problem gone :) Thanks for this awesome library