Closed martykazmaier closed 6 months ago
I switched the secure websocket lib - could likely be that something doesn't work.
(Xibalba secure websocket works however)
I've not settled yet for a websocket library I need to test at least another one. But good to know what to test for.
Works for me. You've to select 'Secure Websocket'.
However I need still test other websocket/ssh libraries…
I got that error when closing the connection. It may have only been once though.
From: Mike Krüger @.> Sent: Monday, May 13, 2024 12:40 AM To: mkrueger/icy_tools @.> Cc: martykazmaier @.>; Author @.> Subject: Re: [mkrueger/icy_tools] error from secure websocket connection (shsbbs.net:8080). (Issue #8)
Closed #8https://github.com/mkrueger/icy_tools/issues/8 as completed.
— Reply to this email directly, view it on GitHubhttps://github.com/mkrueger/icy_tools/issues/8#event-12782035032, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A4JLVXXDMCFUB2SVVSQWTDTZCBN7LAVCNFSM6AAAAABHRTQGCOVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJSG44DEMBTGUYDGMQ. You are receiving this because you authored the thread.Message ID: @.***>
I'm still getting it if I let the system follow through the logoff ansi and hanging up itself. Not just once. Everytime on my system at least.
Target closed Connection aborted: IO error: peer closed connection without sending TLS close_n otify: https://docs.rs/rustls/latest/rustls/manual/_03_howto/index.html#unexpect ed-eof