-
Notifications
You must be signed in to change notification settings - Fork 284
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
wss / secure websockets don't work, cause server process exit #385
Comments
Sometimes a core dump occurs after wss initialisation:
However usually vibed just exits. |
Here's another error with the same cause from a -debug compile, get an assertion failure this time:
|
Captured a bunch of core dumps and analsyed with gdb but they show problems in many places... here's a few:
|
The WebSocket specific bug should be fixed now and the rest looks like it may all be #384. I'll continue to investigate there. |
vibed seems to just exit without any stack trace a lot when attempting this.
If you set up the ssl context correctly and serve content over SSL vibed will crash after the browser has attempted to initiate the wss connection.
The text was updated successfully, but these errors were encountered: