Socket.io-client: Setting rejectUnauthorized to false is not ignoring certificate error

Created on 29 Mar 2016 · 4Comments · Source: socketio/socket.io-client

I've a self signed certificate setup with a different hostname on my server. I get a
WebSocket Error: Network Error 12038, The host name in the certificate is invalid or does not match
on IE.

I tried setting rejectUnauthorized to false but it still gives me the same error.

var wsconnect = socket('https://url', {
  transports: ['websocket'],
  rejectUnauthorized: false
});

Am I doing this right?

Source

aravindsrivats

👍2

Most helpful comment

does this only work on nodejs but not with the client on browser? I can't get it work from browser. Still pop out Error in connection establishment: net::ERR_CERT_AUTHORITY_INVALID in chrome

YenF on 31 Mar 2018

👍3

All 4 comments

@aravindsrivats using process.env.NODE_TLS_REJECT_UNAUTHORIZED = '0';

zeeshanjan82 on 29 Sep 2016

😕2 👎1

does it works?

roccomuso on 16 Jan 2018

does this only work on nodejs but not with the client on browser? I can't get it work from browser. Still pop out Error in connection establishment: net::ERR_CERT_AUTHORITY_INVALID in chrome

YenF on 31 Mar 2018

👍3

Did anyone ever figure this out? Having this problem now.