Setup Server-Server SSL communication using socket.io in node.js

Question

I'm trying to setup a server to server link using socket.io over ssl connection. This is my example:

/**
 * Server
 */


var app = require('express')();
var config = require('./config');
var https = require('https');
var http = require('http');
var fs = require('fs');
var server = https.createServer({key: fs.readFileSync(config.ssl.key), cert: fs.readFileSync(config.ssl.cert), passphrase: config.ssl.passphrase}, app);
//var server = http.createServer(app);
var io = require('socket.io').listen(server);

server.listen(config.port);

app.get('/', function (req, res) {
    res.send('Server');
  //res.sendfile(__dirname + '/index.html');
});

io.sockets.on('connection', function (socket) {
  socket.emit('news', { hello: 'world' });
  socket.on('my other event', function (data) {
    console.log(data);
  });
});



/**
 * Client
 */


var io = require('socket.io-client');
//var socket = io.connect('http://localhost', {port: 8088});
var socket = io.connect('https://localhost', {secure: true, port: 8088});
  socket.on('connect', function(){
    socket.on('event', function(data){});
    socket.on('disconnect', function(){});
  });

The code works fine when ran without SSL. I suspect it could be my self-signed certificate not being accepted, but I do not know how to make the client accept it.

Can I accept a self-signed SSL certificate, or is there another approach I can take?

After some more digging, I found that adding: require('https').globalAgent.options.rejectUnauthorized = false; before "var socket" in the client fixes the problem — Tomasz Rakowski
– Tomasz Rakowski, Commented Feb 8, 2014 at 20:21

Community · Accepted Answer · 2017-05-23 12:32:26Z

15

I've had to do things a little differently on the client to get this to work, by manually telling socket.io to use that Agent as well (and the secure: true is implied by https:). Here it is:

// Client
var io = require('socket.io-client');
var https = require('https');
https.globalAgent.options.rejectUnauthorized = false;
var socket = io.connect('https://localhost:3210/', { agent: https.globalAgent });
socket.on('connect', function(){ console.log('connected'); });

This is using socket.io v1.0.2.

Alternatively, I've had success with the following as well, as pointed to here: Socket.io + SSL + self-signed CA certificate gives error when connecting

process.env.NODE_TLS_REJECT_UNAUTHORIZED = '0';
var io = require('socket.io-client');
var socket = io.connect('https://localhost:3210/');
socket.on('connect', function(){ console.log('connected'); });

edited May 23, 2017 at 12:32

CommunityBot

11 silver badge

answered Jun 16, 2014 at 0:51

stevo

4685 silver badges10 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

smb Over a year ago

Worked perfect! I don't use self signed certs, but I want to be able to ignore my certification issues when doing local unit testing against my dev box. This did the trick! Thanks

Eric Dela Cruz Over a year ago

After a whole day searching and trying, your first solution worked for me. The second one with didn't work. Thanks!

Tomasz Rakowski · Accepted Answer · 2014-02-08 20:24:27Z

10

After some more searching, adding this in the client makes it work:

require('https').globalAgent.options.rejectUnauthorized = false;

/**
 * Client
 */


var io = require('socket.io-client');
//var socket = io.connect('http://localhost', {port: 8088});

require('https').globalAgent.options.rejectUnauthorized = false; 

var socket = io.connect('https://localhost', {secure: true, port: 8088});
  socket.on('connect', function(){
    socket.on('event', function(data){});
    socket.on('disconnect', function(){});
  });

answered Feb 8, 2014 at 20:24

Tomasz Rakowski

1,0624 gold badges13 silver badges28 bronze badges

1 Comment

hg. Over a year ago

For new versions of node.js you will also have to add process.env.NODE_TLS_REJECT_UNAUTHORIZED = 0;

Sebastiaan Luca · Accepted Answer · 2016-04-29 09:34:15Z

6

The previous answers didn't do it for me. require('https').globalAgent is always undefined.

Did some seaching and found the rejectUnauthorized parameter in the docs (https://nodejs.org/api/tls.html). Not sure if it's related to SocketIO, but it somehow seems to work with self-signed certificates:

var socket = io.connect('//yourhost:8000', {secure: true, rejectUnauthorized: false})

secure: true might be optional, but I like to enforce it anyhow.

answered Apr 29, 2016 at 9:34

Sebastiaan Luca

5031 gold badge9 silver badges11 bronze badges

Comments

Zhiyong · Accepted Answer · 2018-06-13 05:22:03Z

0

While all the above solutions focus on rejectUnauthorized=false, I'd like to suggest an alternative.

const https = require('https');
const rootCas = require('ssl-root-cas').create();
rootCas.addFile('cert/ca.crt');
https.globalAgent.options.ca = rootCas; // optional

const io = require("socket.io-client");
var socket = io.connect("https://...", { agent: https.globalAgent });

answered Jun 13, 2018 at 5:22

Zhiyong

7367 silver badges15 bronze badges

Collectives™ on Stack Overflow

Setup Server-Server SSL communication using socket.io in node.js

4 Answers 4

2 Comments

1 Comment

Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

4 Answers 4

2 Comments

1 Comment

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related