javascript - Using Socket.IO from Node.js to connect to external server - Stack Overflow

admin管理员组

文章数量:1322697

Background: I have a node.js server running on my localhost (call this Server A); and an external server running node.js at :3000 (call this Server B). I do not control or have access to Server B (it is a dashboard site for an IoT device in my home), but I need to connect to is using socket.io and emit a specific message.

I can connect to it easily from a flat javascript file (client-side), but need it running server side (ultimate goal is to make it into something I can call with an HTTP request); and examples such as How to connect two node.js servers with websockets? suggest I should be able to use socket.io-client from node.js with nearly the same code to achieve the same results. But when I run the code from node.js, I cannot connect to the socket.

Below is the code that works successfully in flat javascript file. I know it works because I see 'socket connect' in the console, and I can also test for the the socket emit at the end.

var myemail = "[email protected]";
var device_id = '12345';
// Create SocketIO instance, connect
var socket = io.connect(':3000');

socket.on('connect', function(){
    try {
        console.log('socket connect');
        socket.emit('configure', {email:myemail, deviceid:device_id});
    } catch(e) {
        console.log(e);
    }
});
socket.emit("/" + device_id, "45678");

...and below is the code I cannot get to work when running from my node.js instance. I'd expect a message 'socket connect' in the mand line log and get nothing.

var express=require('express');
var http=require('http');
var app=express();
var server = http.createServer(app);
//Variables

var myemail = "[email protected]";
var device_id = '12345'; 

var io = require('socket.io-client');
var socket = io.connect(':3000');

//Connect listener
socket.on('connect', function(){
   try {
      console.log('socket connect');
      socket.emit('configure', {email:myemail, deviceid:device_id});
   } catch(e) {
     console.log(e);
   }
});
socket.emit("/" + device_id, "45678");

Any ideas?

UPDATE

Ran debug utility, results included as linked image below. Key thing I see is that engine.io tries to do an xhr poll, and gets a 503 response back from the server. (Obviously not a true 'temporary error' with the server as again, this all works from running client-side js in chrome).

debugging output image link

Background: I have a node.js server running on my localhost (call this Server A); and an external server running node.js at https://example:3000 (call this Server B). I do not control or have access to Server B (it is a dashboard site for an IoT device in my home), but I need to connect to is using socket.io and emit a specific message.

I can connect to it easily from a flat javascript file (client-side), but need it running server side (ultimate goal is to make it into something I can call with an HTTP request); and examples such as How to connect two node.js servers with websockets? suggest I should be able to use socket.io-client from node.js with nearly the same code to achieve the same results. But when I run the code from node.js, I cannot connect to the socket.

Below is the code that works successfully in flat javascript file. I know it works because I see 'socket connect' in the console, and I can also test for the the socket emit at the end.

var myemail = "[email protected]";
var device_id = '12345';
// Create SocketIO instance, connect
var socket = io.connect('https://example:3000');

socket.on('connect', function(){
    try {
        console.log('socket connect');
        socket.emit('configure', {email:myemail, deviceid:device_id});
    } catch(e) {
        console.log(e);
    }
});
socket.emit("/" + device_id, "45678");

...and below is the code I cannot get to work when running from my node.js instance. I'd expect a message 'socket connect' in the mand line log and get nothing.

var express=require('express');
var http=require('http');
var app=express();
var server = http.createServer(app);
//Variables

var myemail = "[email protected]";
var device_id = '12345'; 

var io = require('socket.io-client');
var socket = io.connect('https://example:3000');

//Connect listener
socket.on('connect', function(){
   try {
      console.log('socket connect');
      socket.emit('configure', {email:myemail, deviceid:device_id});
   } catch(e) {
     console.log(e);
   }
});
socket.emit("/" + device_id, "45678");

Any ideas?

UPDATE

Ran debug utility, results included as linked image below. Key thing I see is that engine.io tries to do an xhr poll, and gets a 503 response back from the server. (Obviously not a true 'temporary error' with the server as again, this all works from running client-side js in chrome).

debugging output image link

• javascript
• node.js
• socket.io
• iot

Share Improve this question Follow edited Aug 21, 2017 at 3:50 Lee asked Aug 20, 2017 at 2:47 LeeLee 8111 silver badge55 bronze badges 11

• Here's a guess. What happens if you want until inside the connect event in order to do your socket.emit("/" + device_id, "45678");. You are attempting that .emit() before the connect has finished. Perhaps this is somehow not causing a problem in the browser, but is on node.js? Timing could be different on the two platforms, perhaps. – jfriend00 Commented Aug 20, 2017 at 3:09
• Oh, and btw, socket.io-client works just fine in node.js to connect to other socket.io servers so that is not an issue. – jfriend00 Commented Aug 20, 2017 at 3:10
• FYI, socket.io has various debug modes that will give you very verbose logging on what's going on too. That might elucidate what is happening. – jfriend00 Commented Aug 20, 2017 at 3:14
• Thanks jfriend00 for the response. Tried adding the emit into the on.("connect") function, didn't work - anyway, it's the initial handshake emit already inside the on connect function that isnt working. ... Also tried using the IP of the server instead of the name. Regarding the debug modes, any thoughts on what i should be looking for? I can see it is not connected but not sure what to look for. – Lee Commented Aug 20, 2017 at 4:09
• Are you sure you have the right version of socket.io-client on your server to match what you're trying to connect to? socket.io can be picky about matching client and server versions. I don't know the debug info in socket.io to know what to look for. If you want to post all the debug output somewhere, I'll look at it. – jfriend00 Commented Aug 20, 2017 at 4:20

 |  Show 6 more ments

2 Answers 2

Sorted by: Reset to default 4

Solved this - issue was that the server I was connecting to required use of https, so I needed to add

{secure: true,    rejectUnauthorized: false}

after the url to connect to.

Full working example:

const myemail   = [email protected];
const device_id   = 12345;
io = require('socket.io-client');
var socket = io.connect('https://server:3000',{secure: true,    rejectUnauthorized: false});

function doStuff(){


//Listener
socket.on('connect', function(){
   try {
      console.log('socket connect');
      socket.emit('configure', {email:myemail, deviceid:device_id});

   } catch(e) {
     console.log(e);
   }
});

socket.emit("/" + device_id, "003021");


}


doStuff();

I think the line causing the issue is :

var socket = io.connect('https://example:3000');

I managed to make a working example using this code :

const myemail = "[email protected]";
const device_id = '12345'; 
var socket = require('socket.io-client')('https://example:3000');
socket.on('connect', function(){
 try{
   console.log('socket connect');
   socket.emit('configure', {email:myemail, deviceid:device_id});
 }catch(e){ console.log(e); }
});

本文标签： javascriptUsing SocketIO from Nodejs to connect to external serverStack Overflow