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 }}
Repository navigation
SSL - Internal error trying to connect to a secure websocket #555
When trying to connect to a secure websocket I get the following output:
Connection error: Unable to connect to server.dev on port 443, error: error in handshake : SSL - Internal error (eg, unexpected failure in lower-level module)
I revisited this while working through the open TLS reports. Current client/server tests pass with Mbed TLS 3 and 4 and OpenSSL 1.1/3.6. We have also fixed PSA-state lifetime (#613), terminal read/error handling (#650), and handshake busy-spinning (#655).
SSL - Internal error does not identify which operation failed, and server.dev in the snippet does not provide a usable reproduction. Could you try current master and provide the IXWebSocket/TLS backend versions, the complete current error, and a minimal server configuration or reproducible endpoint? Your use of caFile for the trust bundle is the correct configuration field.
Keeping this open pending a current reproduction rather than assuming the other TLS fixes explain this particular failure.
Closing this old report because we do not have a usable reproduction or enough information to identify a remaining library defect. The current TLS paths have received several fixes and pass the backend tests described above. This does not establish that the original failure was fixed. Please reopen with a minimal reproduction on current master, backend/version details, and the complete error if it still occurs.
Activity
bsergean commentedon Nov 17, 2026
I revisited this while working through the open TLS reports. Current client/server tests pass with Mbed TLS 3 and 4 and OpenSSL 1.1/3.6. We have also fixed PSA-state lifetime (#613), terminal read/error handling (#650), and handshake busy-spinning (#655).
SSL - Internal errordoes not identify which operation failed, andserver.devin the snippet does not provide a usable reproduction. Could you try current master and provide the IXWebSocket/TLS backend versions, the complete current error, and a minimal server configuration or reproducible endpoint? Your use ofcaFilefor the trust bundle is the correct configuration field.Keeping this open pending a current reproduction rather than assuming the other TLS fixes explain this particular failure.
bsergean commentedon Nov 17, 2026
Closing this old report because we do not have a usable reproduction or enough information to identify a remaining library defect. The current TLS paths have received several fixes and pass the backend tests described above. This does not establish that the original failure was fixed. Please reopen with a minimal reproduction on current master, backend/version details, and the complete error if it still occurs.