Firefox can't establish a websocket connection while Chrome can

Question

I'm developing a webapp and I'm including websocket connectivity. I've installed a websocket server with node.js (5.0.0) with websocket (https://www.npmjs.com/package/websocket).

In Chrome it works perfectly but in Firefox this message appears in console:

Firefox no puede establecer una conexión con el servidor en wss://www.my-dev-server.com:1337/.

(Firefox can't establish a connection with server at...)

This is the server code (basically as in examples):

var WebSocketServer = require('websocket').server;

var https = require('https');
var fs = require('fs');

var options = {
  key: fs.readFileSync('/keyfile.key'),
  cert: fs.readFileSync('/pemfile.pem')
};
var port = 1337; 

// Create HTTPS service.
var server = https.createServer(options, function(request, response) {
    console.log((new Date()) + ' Received request for ' + request.url);
    response.writeHead(404);
    response.end();
});     

server.listen(port, function() {
    console.log((new Date()) + ' Server is listening on port ' + port);
});

// create the server
wsServer = new WebSocketServer({
    httpServer: server,
    autoAcceptConnections: false
});

function originIsAllowed( origin ) {
    // TODO: complete
    return true;
}

var clients = [];

// WebSocket server
wsServer.on('request', function(request) {

    if( !originIsAllowed( request.origin ) ) {
        request.reject();
        console.log((new Date()) + ' Connection from origin ' + request.origin + 'rejected.');
        return;
    }
    console.log((new Date()) + ' Connection accepted from ' + request.origin + '.');

    var connection = request.accept(null, request.origin);
    clients.push(connection);

    connection.on('message', function( message ) {
        if (message.type === 'utf8') {
            console.log('Received Message: ' + message.utf8Data);
        }
        else if( message.type === 'binary' ) {

        }
    });

    connection.on( 'error', function( error ) {
    });

    connection.on('close', function( reasonCode, description ) {
        console.log((new Date()) + " Peer " + connection.remoteAddress + " disconnected.");
    });
});

I use a self-signed certificate for development purposes, the same that is used by the web server.

This is my client code:

var connection = new WebSocket('wss://www.my-dev-server.com:1337');

connection.onopen = function () { };

connection.onerror = function (error) { };

connection.onmessage = function (message) {
    /* some code here */
};

francadaval · Accepted Answer · 2015-11-08T12:29:49.213

7

I, finally, found a solution.

The problem was that for https connections, in port 443, Firefox had already stored an exception for unknown certificate while it needed another exception for wss (port 1337 in this case).

I've added a certificate exception, in advanced preferences, for this port and now works fine.

edited Nov 08 '15 at 12:29

answered Nov 08 '15 at 12:18

francadaval

2,451
3
26
36

3

any programmatical way to do this in node.js – mayank Dec 09 '16 at 09:27
1

I am facing this issue in firefox in my uat phase , chrome and other browser working fine – mayank Dec 09 '16 at 09:31
No, it's about browser configuration. You have to use a trusted certificate or config the browser to allow the self-signed certificate for your websocket URL. – francadaval Dec 09 '16 at 10:10
okay. I have handled it using nginx proxy_pass it worked for me :) – mayank Dec 09 '16 at 11:54
@mayank how did you do this with nginx proxy_pass? – Esqarrouth May 29 '20 at 20:26
@francadaval does that mean each firefox browsers have to do a manual operation to allow self-signed certificate? – Esqarrouth May 29 '20 at 20:27

Firefox can't establish a websocket connection while Chrome can

1 Answers1

Linked