New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Self-signed certs #19
Comments
Resolved - Had to use ws instead of websockets. Then as ws wouldn't work I had to implement the fix from #15 (comment) Doesnt look like my msgs are making it to the server though, could this be another issue with using ws? When I follow the change you recommended in the previous thread, appending .ws to wsp it forces the connection closed without me calling a wsp.close(), when this occurs the connections closed event is 1006.
|
@narsariusv |
Working with |
Getting connection errors due to self-signed certs. Is their an option similar to ws that allows you to bypass the connection error?
The text was updated successfully, but these errors were encountered: