HTTPS SSL gotcha about peerjs-server

[SameerRathod]

I am also getting error but it is slightly different
It is saying me

Could not get an ID from the server. If you passed in a path to your self-hosted PeerServer, you'll also need to pass in that same path when creating a new Peer.

here is my configuration
var peer = new Peer(id,{host: '111.118.237.23', port: 9009,secure:true});

I am using a custom node server

var fs =require('fs');

var PeerServer = require('peer').PeerServer;
var server = new PeerServer({host:'111.118.237.23',port: 9009,
ssl: {
key: fs.readFileSync('/etc/ssl/certs/server.key'),
certificate: fs.readFileSync('/etc/ssl/certs/server.crt')
}

});

and self signed certificate
please help me in my scenario I cant use this product unsecured without ssl

[michelle]

Are you getting something like Error: DEPTH_ZERO_SELF_SIGNED_CERT? How is it failing?

[inian]

I solved this problem by opening the URL which the app makes a request to in a new tab, then confirm the security exception thrown by Chrome (since the certificate is self-signed, Chrome wont recognise it).
After adding the exception, the app worked fine.

[redannick]

@michelle I was not getting any errors from the server, and chrome wasn't giving me any errors either. I did try what @inian suggests too, but couldn't get the browser to detect the certificate as it wasn't an http request

[inian]

Yes, try enabling XMLHTTPRequests in the Chrome dev tools console and then you would be able to see the requests being made.

[luongnv89]

@sameer293 Did you manage this problem?

[SameerRathod]

@luongnv89 not yet.

[clarencechen]

@redannick @michelle @sameer293 @luongnv89 This problem is still happening in 2017 :(

[luongnv89]

@clarencechen I follow the tutorial in this: https://www.npmjs.com/package/peer, and it works for me.

This is how I did it:

var app = express()
var ExpressPeerServer = require('peer').ExpressPeerServer
var peerjs_options = {
    debug: true
}
var ssl_options ={
    key:fs.readFileSync('./certificate/myserver.key'),
    ca:fs.readFileSync('./certificate/GandiStandardSSLCA2.pem'),
    cert:fs.readFileSync('./certificate/certificate.crt'),
    honorCipherOrder: true,
    ciphers: 'ECDHE-RSA-AES128-SHA256:AES128-GCM-SHA256:HIGH:!RC4:!MD5:!aNULL:!EDH'
}
var server = https.createServer(ssl_options,app)
var peerServer = ExpressPeerServer(server, peerjs_options)

... set your app ... 

app.use('/myapp', peerServer)
server.listen(443)

Hope this help

[clarencechen]

Are there any files or strings I should obtain?
Thanks so much in advance

[sreekj]

@SameerRathod
Sameer, were you able to get over this issue ?

[afrokick]

Use lets encrypt to obtain cert and key, then use it for reverse proxy or pass in options

node ./src/index.js --sslCertPath /path/to/cert.pem --sslKeyPath /path/to/key.key

[redannick]

@afrokick does this help with local https development?

[afrokick]

@afrokick does this help with local https development?

Sorry, i don't know. I test it on local http and it works perfectly.

[redannick]

I only mention it as I believe this was what I was doing in the first place. I was testing something that required https so expected a self cert to work. I suppose you could spoof a domain in your hosts file perhaps to use a let's encrypt certificate locally or put it on a temporary domain and this was my original workaround, but really, shouldn't a self cert work in the first place?

[AlexErrant]

I suppose you could spoof a domain in your hosts file... shouldn't a self cert work in the first place?

I do this in my project, and document how to "get started" here. The steps aren't specific to PeerJS, but you should be able to understand how mkcert works and generate your own selfsigned key/cert and update your hosts file for peerjs-server from that doc.