Not able to use wss with an IP address

[peterphonic]

Not able to use wss with an IP address

[bsergean]

This might be a high level SSL stuff, where you actually need a real hostname and can't use an IP.

$ curl -I google.com/
HTTP/1.1 301 Moved Permanently
Location: http://www.google.com/
Content-Type: text/html; charset=UTF-8
Date: Fri, 10 Feb 2023 20:17:07 GMT
Expires: Sun, 12 Mar 2023 20:17:07 GMT
Cache-Control: public, max-age=2592000
Server: gws
Content-Length: 219
X-XSS-Protection: 0
X-Frame-Options: SAMEORIGIN
Connection: close

$ ping google.com 
PING google.com (142.251.214.142): 56 data bytes
64 bytes from 142.251.214.142: icmp_seq=0 ttl=118 time=6.540 ms
^C
--- google.com ping statistics ---
1 packets transmitted, 1 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 6.540/6.540/6.540/0.000 ms
DataMover$ curl -I https://142.251.214.142
curl: (60) SSL certificate problem: self signed certificate
More details here: https://curl.se/docs/sslcerts.html

curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.

[peterphonic]

Ahhh, thank you, I'll see what I can do in our test environment.

[peterphonic]

I coded a small javascript wss client (using same npm package than my wss server) and this wss client can connect to the same wss server (usingn ip address). Would it be possible that the javascript client and IXWebSocket client have a different implementation of OpenSSL interface?

[bsergean]

Yes the ixwebsocket client uses openssl in its own way.

[peterphonic]

So, I updated my hosts file. I added a fake url pointing to the wss server. Then, I created a new certificate with a SAN pointing to the fake URL et voilà, my c++ wss client can connect to my wss javascript server.

So, your assumption is correct, the IXWebSocket implementation of openssl cannot use an ip address, only domain.

Thank you!