You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 12, 2018. It is now read-only.
Trying to connect from a javascript client to the server but I can't seem to get it to do it.
The certificate is self signed. First the client browser sends a GET to the other http server (your simple web server Eidheim) which uses the self signed certificate to get the rest file. That works fine as long as the first time an exception is created in the browser to accept the self signed certificate.
The html file that is distributed that way does a connect in that fashion to the secure websocket server (The code provided in this repo):
websocket = new WebSocket(wsUri); where wsUri is :
var wsUri = "wss://localhost:7777";
the port was changed from 8080 to 7777 so not to conflict with the simple web server
I read here and there I may have a problem with the self signing certificate that wss just won't trust and won't give any warning about, and just error the connection.
If I point browser (any) to wss://localhost:7777 or wss://127.0.0.1:7777 or wss://[machine name]:7777 I get nowhere, so I can't get the message to pop up for me to add an exception.
Not sure how to get some traction with my self signing certificate. Using a self signing certificate should work for me as it should be an option for people who install my product and may not have a verified certificate to provide
The text was updated successfully, but these errors were encountered:
leogi22
changed the title
seld signed certificate
self signed certificate
Sep 8, 2016
It has been some time since I did this, but I think I managed to connect to my wss with a self signed certificate on Chrome, but I first had to accept the certificate through https with the same certificate. I do not remember if I had to use the same port or not before getting the wss up and running. It seems there is lacking support on web browsers to accept certificates on wss connections sadly.
Thought, I think there should be a way to accept self signed certificates in your OS? I'm not an expert on this however.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Trying to connect from a javascript client to the server but I can't seem to get it to do it.
The certificate is self signed. First the client browser sends a GET to the other http server (your simple web server Eidheim) which uses the self signed certificate to get the rest file. That works fine as long as the first time an exception is created in the browser to accept the self signed certificate.
The html file that is distributed that way does a connect in that fashion to the secure websocket server (The code provided in this repo):
websocket = new WebSocket(wsUri); where wsUri is :
var wsUri = "wss://localhost:7777";
the port was changed from 8080 to 7777 so not to conflict with the simple web server
I read here and there I may have a problem with the self signing certificate that wss just won't trust and won't give any warning about, and just error the connection.
If I point browser (any) to wss://localhost:7777 or wss://127.0.0.1:7777 or wss://[machine name]:7777 I get nowhere, so I can't get the message to pop up for me to add an exception.
Not sure how to get some traction with my self signing certificate. Using a self signing certificate should work for me as it should be an option for people who install my product and may not have a verified certificate to provide
The text was updated successfully, but these errors were encountered: