Closed jaimestuardo closed 3 years ago
The prototype uses self-signed certificates, so you should just bypass the warning.
Click on "advanced" -> "Proceed to x.x.x.x (unsafe)" should suffice.
How to do that when connecting using socket.io client.
Actually, the problem is that. I only used Chrome to check that the same problem occurs.
Regarda Jaime
You probably need some additional parameter to bypass SSL certificate check. Does this help? https://github.com/socketio/socket.io/issues/1187
Alternatively just use a real domain name with real certificates (e.g. use certbot to get one from LetsEncrypt).
But didn't you have that problem when creating this tutorial?
Never mind. I have finally exported a self signed certificate that was created by Visual Studio to be used in IISEXPRESS when debugging sites. I exported public and private keys and referenced them when instantiating the socket.io server. Now it works.
When using OpenSSL as in your tutorial it does not work.
Regards Jaime
I did what you taught but there is a problem with the certificate authority. This is the same error that appeared in the youtube video when trying to connect using Google Chrome.
How can I solve this?
Regards Jaime