Bad Gateway Error using Socket.io Node.js over SSL

Question

I previously had a Socket.io script running fine over http, but upgrading to https has broken it. I have installed the cert on the server but no luck. The code for the server setup is:

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

var options = {
    key:    fs.readFileSync('/etc/nginx/ssl/default/54082/server.key'),
    cert:   fs.readFileSync('/etc/nginx/ssl/default/54082/server.crt')
};
var app = https.createServer(options);

var io = require('socket.io').listen(app);

However in the web browser the page fails to connect to it and the console shows a the server responded with a status of 502 (Bad Gateway) response.

Any ideas on if the script set up is wrong? Or perhaps something in the Nginx setup?

Many thanks

Edit: The front end code I'm using to connect:

<script type="text/javascript" src="https://socket.example.com/socket.io/socket.io.js"></script>
<script>
var io = io('https://socket.example.com', { secure: true });
</script>

Edit:: Nginx config:

# FORGE CONFIG (DOT NOT REMOVE!)
include forge-conf/socket.example.co.uk/before/*;

server {
    listen 443 ssl;
    server_name socket.example.co.uk;
    root /home/forge/socket.example.co.uk;

    # FORGE CONFIG (DOT NOT REMOVE!)
    include forge-conf/socket.example.co.uk/server/*;

    location / {    
        proxy_pass https://socket.example.co.uk:3000;
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection 'upgrade';
        proxy_set_header Host $host;
        proxy_cache_bypass $http_upgrade;
    }

}

# FORGE CONFIG (DOT NOT REMOVE!)
include forge-conf/socket.example.co.uk/after/*;

Are you passing {secure: true} while connecting to server ? stackoverflow.com/questions/6599470/node-js-socket-io-with-ssl — Mukesh Sharma
– Mukesh Sharma, Commented Feb 29, 2016 at 11:44
it is not necessary to proxy to node.js through nginx. the port is open, so connecting with io.connect('<domain>:<port>',{secure:true}); from the client is all you need to do to get up and running. it is not possible to proxy through nginx (and not necessary since node binds to all interfaces, and the domain is routed to your ip:port anyway due to DNS config). i literally upgraded my socket io to https yesterday without problems. — r3wt
– r3wt, Commented Feb 29, 2016 at 13:54
@r3wt So you're saying the domain should be something different? What should it be? I am using the code var io = io('https://socket.example.com/socketio/socketio.js', { secure: true }); — samiles
– samiles, Commented Mar 2, 2016 at 11:48
@r3wt :( No need for names. I'm trying my best and you don't have to help me. I'll post the front end code now... — samiles
– samiles, Commented Mar 2, 2016 at 16:23
the people who called me on my lack of effort are the ones who made me a better developer. instead of pardoning yourself for your incompetence, you should recognize this as a gift so that you can see the areas where you are deficient and need to improve in. — r3wt
– r3wt, Commented Mar 2, 2016 at 16:26

r3wt · Accepted Answer · 2016-03-02 16:36:27Z

5

+25

make sure that your domain points to your server.
make sure that an nginx server block is running for your domain with ssl enabled.
remove any location blocks from your nginx config attempting to proxy to the port you are running your socket.io server on.
make sure your ssl certificate is valid.
connect with io.connect() instead of the way you are doing. leave out the protocol portion of the url (https://).
use sudo killall -9 node from the commandline to kill any zombie processes that might be lingering and bound to your port. this sometimes happens with socket.io when it fails to shutdown properly.

example from my own code:

var socket = io.connect('dev.somedomain.com:3000',{secure:true});

server example from my own domain:

var fs = require('fs'),
    https = require('https'),
    config = JSON.parse(fs.readFileSync('./config.json','utf-8')),
    serverOpts = {
        key: fs.readFileSync(config.server.key),
        cert: fs.readFileSync(config.server.cert)
    },
    server = https.createServer(serverOpts,function(req,res){}),
    io = require('socket.io').listen(server);

io.on('connection', function(socket){
   console.log('houston, we have lift off');
});

server.listen(config.port, function(){
    log('listening on *:%d',config.port);
});

obviously i'm reading the path to my certificate and key file from a config.json file but you should get the idea right?

answered Mar 2, 2016 at 16:36

r3wt

4,7622 gold badges37 silver badges57 bronze badges

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

1 Comment

samiles Over a year ago

Not had any luck with any of this. Thanks anyway for your help. Maybe there's something else in my setup somewhere breaking something... I'm just giving up now...

Anil Kumar · Accepted Answer · 2016-03-09 09:19:51Z

4

The 502 (Bad Gateway) indicates that the nginx service tried to contact the proxy server but failed. The line in the nginx config

 proxy_pass https://socket.example.co.uk:3000;

seems to be the issue. Could not see from your nodejs code that the port 3000 is being used.

answered Mar 9, 2016 at 9:19

Anil Kumar

1246 bronze badges

Comments

Ipoel · Accepted Answer · 2017-09-12 17:11:28Z

-4

I've same issue but with apache2, I solve it by add this line to my vhost config

SSLProxyEngine on SSLProxyVerify none SSLProxyCheckPeerCN off SSLProxyCheckPeerName off SSLProxyCheckPeerExpire off

answered Sep 12, 2017 at 17:11

Ipoel

11 bronze badge

Collectives™ on Stack Overflow

Bad Gateway Error using Socket.io Node.js over SSL

3 Answers 3

1 Comment

Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

3 Answers 3

1 Comment

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related