lws_service call stuck after upgrading wolfSSL version

[phelpsdc10]

Setup Info:
LWS version 4.3.1
WolfSSL verion upgraded from 4.6.0 to 5.7.6
Curl upgraded to 8.17.0

Before upgrade: Linux 32-bit, Windows 32-bit, Windows 64-bit, and Unison wolfssl consuming products have had no issues.
After upgrade: Windows products are not able to finish hello process, as they get "stuck" in lws_service. (IE no return from lws_service, haven't finished stepping through polling etc. yet, additional testing needs to be done with 3rd party device to see if the problem may be self-connection)

Problem:
This is a single-threaded implementation where the same application is connecting to itself (client/server).
The client sends hello and then moves to want to read. The server processes the read, sends server hello, and moves to want to read. It never gets back to the client read. Attempted to do lws_cancel_service on LWS_CALLBACK_SERVER_WRITEABLE but does not appear to be getting there on a step-through.

Steps Taken:
Initially observed that the wolfssl bio_read was sending back SOCKET_ERROR_E on a WSAEWOULDBLOCK for the client which I thought might trigger a failure. I changed this to also send back a -323 on a WSAEWOULDBLOCK instead of SOCKET_ERROR_E but there was no change. All timers were doubled for testing, but this also had no effect. No other changes have been made.

Request:
Was hoping some guidance or enlightenment regarding this iisue could be given.

`02/26/2026 10:10:09 [2026/02/26 10:10:09:8759] N: __lws_lc_tag: ++ [wsi|0|pipe] (1)

02/26/2026 10:10:09 [2026/02/26 10:10:09:8759] N: __lws_lc_tag: ++ [vh|0|system||-1] (1)

02/26/2026 10:10:09 [2026/02/26 10:10:09:8759] N: __lws_lc_tag: ++ [wsisrv|0|adopted] (1)

02/26/2026 10:10:09 [2026/02/26 10:10:09:8759] N: __lws_lc_tag: ++ [vh|1|default||1443] (2)

02/26/2026 10:10:09 [2026/02/26 10:10:09:8759] N: Vhost 'default' using TLS mode

02/26/2026 10:10:09 [2026/02/26 10:10:09:9022] N: SSL ECDH curve 'prime256v1'

02/26/2026 10:10:09 [2026/02/26 10:10:09:9054] N: [vh|1|default||1443]: lws_socket_bind: source ads 0.0.0.0

02/26/2026 10:10:09 [2026/02/26 10:10:09:9054] N: __lws_lc_tag: ++ [wsi|1|listen|default||1443] (2)

02/26/2026 10:10:09 BACNET_SC_INFO_MSG : The Websocket Server Task is attempting Hub Connection during startup.

02/26/2026 10:10:09 BACNET_SC_INFO_MSG : code 12 value 0

02/26/2026 10:10:09 [2026/02/26 10:10:09:9075] N: __lws_lc_tag: ++ [wsicli|0|WS/h1/default/10.21.212.24] (1)

02/26/2026 10:10:09 [2026/02/26 10:10:09:9075] W: lws_plat_set_socket_options_ip: not implemented on windows platform

02/26/2026 10:10:09 [2026/02/26 10:10:09:9085] N: lws_gate_accepts: on = 0

02/26/2026 10:10:09 wolfSSL Entering wolfSSL_new

02/26/2026 10:10:09 wolfSSL Entering ReinitSSL

02/26/2026 10:10:09 wolfSSL Entering SetSSL_CTX

02/26/2026 10:10:09 wolfSSL Entering wolfSSL_set_options

02/26/2026 10:10:09 WOLFSSL_OP_CIPHER_SERVER_PREFERENCE

02/26/2026 10:10:09 SSL_OP_NO_COMPRESSION: compression not compiled in

02/26/2026 10:10:09 wolfSSL Entering wolfSSL_NewSession

02/26/2026 10:10:09 InitSSL done. return 0 (success)

02/26/2026 10:10:09 wolfSSL_new InitSSL success

02/26/2026 10:10:09 wolfSSL Leaving wolfSSL_new InitSSL =, return 0

02/26/2026 10:10:09 wolfSSL Entering wolfSSL_BIO_s_socket

02/26/2026 10:10:09 wolfSSL Entering wolfSSL_BIO_new

02/26/2026 10:10:09 wolfSSL Entering wolfSSL_BIO_new_socket

02/26/2026 10:10:09 wolfSSL Entering wolfSSL_set_bio

02/26/2026 10:10:09 wolfSSL Entering wolfSSL_BIO_set_flags

02/26/2026 10:10:09 wolfSSL Entering wolfSSL_BIO_set_flags

02/26/2026 10:10:09 wolfSSL Entering wolfSSL_dtls_set_using_nonblock

02/26/2026 10:10:09 wolfSSL_dtls_set_using_nonblock() is DEPRECATED for non-DTLS use.

02/26/2026 10:10:09 wolfSSL Entering wolfSSL_set_ex_data

02/26/2026 10:10:09 wolfSSL Entering wolfSSL_CRYPTO_set_ex_data

02/26/2026 10:10:09 wolfSSL Entering wolfSSL_ERR_clear_error

02/26/2026 10:10:09 Error queue turned off, can not clear nodes

02/26/2026 10:10:09 TLS 1.2 or lower

02/26/2026 10:10:09 wolfSSL Entering wolfSSL_connect

02/26/2026 10:10:09 wolfSSL Entering ReinitSSL

02/26/2026 10:10:09 wolfSSL Entering RetrySendAlert

02/26/2026 10:10:09 wolfSSL Entering SendTls13ClientHello

02/26/2026 10:10:09 Adding signature algorithms extension

02/26/2026 10:10:09 Adding supported versions extension

02/26/2026 10:10:09 wolfSSL Entering EccMakeKey

02/26/2026 10:10:09 wolfSSL Leaving EccMakeKey, return 0

02/26/2026 10:10:09 growing output buffer

02/26/2026 10:10:09 PSK Key Exchange Modes extension to write

02/26/2026 10:10:09 Key Share extension to write

02/26/2026 10:10:09 Supported Versions extension to write

02/26/2026 10:10:09 Signature Algorithms extension to write

02/26/2026 10:10:09 Point Formats extension to write

02/26/2026 10:10:09 Supported Groups extension to write

02/26/2026 10:10:09 Encrypt-Then-Mac extension to write

02/26/2026 10:10:09 SNI extension to write

02/26/2026 10:10:09 EMS extension to write

02/26/2026 10:10:09 wolfSSL Entering SslBioSend

02/26/2026 10:10:09 wolfSSL Entering wolfSSL_BIO_write

02/26/2026 10:10:09 Shrinking output buffer

02/26/2026 10:10:09 wolfSSL Leaving SendTls13ClientHello, return 0

02/26/2026 10:10:09 connect state: CLIENT_HELLO_SENT

02/26/2026 10:10:09 Server state up to needed state.

02/26/2026 10:10:09 Progressing server state...

02/26/2026 10:10:09 ProcessReply...

02/26/2026 10:10:09 wolfSSL Entering RetrySendAlert

02/26/2026 10:10:09 wolfSSL Entering SslBioReceive

02/26/2026 10:10:09 wolfSSL Entering SslBioReceive

02/26/2026 10:10:09 wolfSSL Entering wolfSSL_BIO_read

02/26/2026 10:10:09 Would block

02/26/2026 10:10:09 wolfSSL error occurred, error = -323

02/26/2026 10:10:09 wolfSSL Entering wolfSSL_get_error

02/26/2026 10:10:09 wolfSSL Leaving wolfSSL_get_error, return -323

02/26/2026 10:10:09 wolfSSL Entering wolfSSL_session_reused

02/26/2026 10:10:09 wolfSSL Leaving wolfSSL_session_reused, return 0

02/26/2026 10:10:09 [2026/02/26 10:10:09:9457] N: __lws_lc_tag: ++ [wsisrv|1|adopted] (2)

02/26/2026 10:10:09 [2026/02/26 10:10:09:9467] N: lws_gate_accepts: on = 0

02/26/2026 10:10:09 wolfSSL Entering wolfSSL_ERR_clear_error

02/26/2026 10:10:09 Error queue turned off, can not clear nodes

02/26/2026 10:10:09 wolfSSL Entering wolfSSL_new

02/26/2026 10:10:09 wolfSSL Entering ReinitSSL

02/26/2026 10:10:09 wolfSSL Entering SetSSL_CTX

02/26/2026 10:10:09 wolfSSL Entering wolfSSL_set_options

02/26/2026 10:10:09 WOLFSSL_OP_NO_SSLv2 : wolfSSL does not support SSLv2

02/26/2026 10:10:09 SSL_OP_NO_SSLv3

02/26/2026 10:10:09 WOLFSSL_OP_CIPHER_SERVER_PREFERENCE

02/26/2026 10:10:09 SSL_OP_NO_COMPRESSION: compression not compiled in

02/26/2026 10:10:09 wolfSSL Entering wolfSSL_NewSession

02/26/2026 10:10:09 InitSSL done. return 0 (success)

02/26/2026 10:10:09 wolfSSL_new InitSSL success

02/26/2026 10:10:09 wolfSSL Leaving wolfSSL_new InitSSL =, return 0

02/26/2026 10:10:09 wolfSSL Entering wolfSSL_set_ex_data

02/26/2026 10:10:09 wolfSSL Entering wolfSSL_CRYPTO_set_ex_data

02/26/2026 10:10:09 wolfSSL Entering wolfSSL_set_fd

02/26/2026 10:10:09 wolfSSL Entering wolfSSL_set_read_fd

02/26/2026 10:10:09 wolfSSL Leaving wolfSSL_set_read_fd, return 1

02/26/2026 10:10:09 wolfSSL Entering wolfSSL_set_write_fd

02/26/2026 10:10:09 wolfSSL Leaving wolfSSL_set_write_fd, return 1

02/26/2026 10:10:09 wolfSSL Entering wolfSSL_dtls_set_using_nonblock

02/26/2026 10:10:09 wolfSSL_dtls_set_using_nonblock() is DEPRECATED for non-DTLS use.

02/26/2026 10:10:09 wolfSSL Entering wolfSSL_ERR_clear_error

02/26/2026 10:10:09 Error queue turned off, can not clear nodes

02/26/2026 10:10:09 wolfSSL Entering wolfSSL_accept

02/26/2026 10:10:09 wolfSSL Entering ReinitSSL

02/26/2026 10:10:09 wolfSSL Entering RetrySendAlert

02/26/2026 10:10:09 wolfSSL Entering RetrySendAlert

02/26/2026 10:10:09 Entered embed receive.

02/26/2026 10:10:09 growing input buffer

02/26/2026 10:10:09 Entered embed receive.

02/26/2026 10:10:09 received record layer msg

02/26/2026 10:10:09 got HANDSHAKE

02/26/2026 10:10:09 wolfSSL Entering wolfSSL_get_options

02/26/2026 10:10:09 wolfSSL Entering DoTls13HandShakeMsg

02/26/2026 10:10:09 wolfSSL Entering EarlySanityCheckMsgReceived

02/26/2026 10:10:09 wolfSSL Leaving EarlySanityCheckMsgReceived, return 0

02/26/2026 10:10:09 wolfSSL Entering DoTls13HandShakeMsgType

02/26/2026 10:10:09 processing client hello

02/26/2026 10:10:09 wolfSSL Entering DoTls13ClientHello

02/26/2026 10:10:09 Supported Versions extension received

02/26/2026 10:10:09 Adding signature algorithms extension

02/26/2026 10:10:09 PSK Key Exchange Modes extension received

02/26/2026 10:10:09 Key Share extension received

02/26/2026 10:10:09 Skipping Supported Versions - already processed

02/26/2026 10:10:09 Signature Algorithms extension received

02/26/2026 10:10:09 Point Formats extension received

02/26/2026 10:10:09 Supported Groups extension received

02/26/2026 10:10:09 Encrypt-Then-Mac extension received

02/26/2026 10:10:09 SNI extension received

02/26/2026 10:10:09 Extended Master Secret extension received

02/26/2026 10:10:09 wolfSSL Entering CheckPreSharedKeys

02/26/2026 10:10:09 wolfSSL Entering ALPN_Select

02/26/2026 10:10:09 wolfSSL Entering MatchSuite

02/26/2026 10:10:09 wolfSSL Entering VerifyServerSuite

02/26/2026 10:10:09 Requires AEAD

02/26/2026 10:10:09 wolfSSL Entering wolfSSL_curve_is_disabled

02/26/2026 10:10:09 wolfSSL_curve_is_disabled checking for 23

02/26/2026 10:10:09 wolfSSL Leaving wolfSSL_curve_is_disabled, return 0

02/26/2026 10:10:09 Verified suite validity

02/26/2026 10:10:09 wolfSSL Entering EccMakeKey

02/26/2026 10:10:09 wolfSSL Leaving EccMakeKey, return 0

02/26/2026 10:10:09 Derive Early Secret

02/26/2026 10:10:09 wolfSSL Leaving DoTls13ClientHello, return 0

02/26/2026 10:10:09 wolfSSL Leaving DoTls13HandShakeMsgType(), return 0

02/26/2026 10:10:09 wolfSSL Leaving DoTls13HandShakeMsg, return 0

02/26/2026 10:10:09 Shrinking input buffer

02/26/2026 10:10:09 accept state ACCEPT_CLIENT_HELLO_DONE

02/26/2026 10:10:09 wolfSSL Entering wolfSSL_accept_TLSv13

02/26/2026 10:10:09 wolfSSL Entering ReinitSSL

02/26/2026 10:10:09 wolfSSL Entering RetrySendAlert

02/26/2026 10:10:09 accept state ACCEPT_HELLO_RETRY_REQUEST_DONE

02/26/2026 10:10:09 accept state ACCEPT_FIRST_REPLY_DONE

02/26/2026 10:10:09 accept state ACCEPT_SECOND_REPLY_DONE

02/26/2026 10:10:09 wolfSSL Entering SendTls13ServerHello

02/26/2026 10:10:09 growing output buffer

02/26/2026 10:10:09 Key Share extension to write

02/26/2026 10:10:09 Supported Versions extension to write

02/26/2026 10:10:09 Shrinking output buffer

02/26/2026 10:10:09 wolfSSL Leaving SendTls13ServerHello, return 0

02/26/2026 10:10:09 accept state SERVER_HELLO_SENT

02/26/2026 10:10:09 accept state ACCEPT_THIRD_REPLY_DONE

02/26/2026 10:10:09 wolfSSL Entering EccSharedSecret

02/26/2026 10:10:09 wolfSSL Leaving EccSharedSecret, return 0

02/26/2026 10:10:09 wolfSSL Entering SendTls13EncryptedExtensions

02/26/2026 10:10:09 Supported Groups extension free

02/26/2026 10:10:09 Derive Handshake Secret

02/26/2026 10:10:09 Derive Client Handshake Secret

02/26/2026 10:10:09 Derive Server Handshake Secret

02/26/2026 10:10:09 Derive Client Key

02/26/2026 10:10:09 Derive Server Key

02/26/2026 10:10:09 Derive Client IV

02/26/2026 10:10:09 Derive Server IV

02/26/2026 10:10:09 growing output buffer

02/26/2026 10:10:09 wolfSSL Entering BuildTls13Message

02/26/2026 10:10:09 wolfSSL Entering EncryptTls13

02/26/2026 10:10:09 wolfSSL Leaving BuildTls13Message, return 0

02/26/2026 10:10:09 Shrinking output buffer

02/26/2026 10:10:09 wolfSSL Leaving SendTls13EncryptedExtensions, return 0

02/26/2026 10:10:09 accept state SERVER_EXTENSIONS_SENT

02/26/2026 10:10:09 wolfSSL Entering SendTls13CertificateRequest

02/26/2026 10:10:09 Signature Algorithms extension to free

02/26/2026 10:10:09 growing output buffer

02/26/2026 10:10:09 Signature Algorithms extension to write

02/26/2026 10:10:09 wolfSSL Entering BuildTls13Message

02/26/2026 10:10:09 wolfSSL Entering EncryptTls13

02/26/2026 10:10:09 wolfSSL Leaving BuildTls13Message, return 0

02/26/2026 10:10:09 Shrinking output buffer

02/26/2026 10:10:09 wolfSSL Leaving SendTls13CertificateRequest, return 0

02/26/2026 10:10:09 accept state CERT_REQ_SENT

02/26/2026 10:10:10 wolfSSL Entering SendTls13Certificate

02/26/2026 10:10:10 growing output buffer

02/26/2026 10:10:10 wolfSSL Entering BuildTls13Message

02/26/2026 10:10:10 wolfSSL Entering EncryptTls13

02/26/2026 10:10:10 wolfSSL Leaving BuildTls13Message, return 0

02/26/2026 10:10:10 Shrinking output buffer

02/26/2026 10:10:10 wolfSSL Leaving SendTls13Certificate, return 0

02/26/2026 10:10:10 accept state CERT_SENT

02/26/2026 10:10:10 wolfSSL Entering SendTls13CertificateVerify

02/26/2026 10:10:10 growing output buffer

02/26/2026 10:10:10 Trying ECC private key, RSA didn't work

02/26/2026 10:10:10 Using ECC private key

02/26/2026 10:10:10 wolfSSL Entering EccSign

02/26/2026 10:10:10 wolfSSL Leaving EccSign, return 0

02/26/2026 10:10:10 wolfSSL Entering BuildTls13Message

02/26/2026 10:10:10 wolfSSL Entering EncryptTls13

02/26/2026 10:10:10 wolfSSL Leaving BuildTls13Message, return 0

02/26/2026 10:10:10 Shrinking output buffer

02/26/2026 10:10:10 wolfSSL Leaving SendTls13CertificateVerify, return 0

02/26/2026 10:10:10 accept state CERT_VERIFY_SENT

02/26/2026 10:10:10 wolfSSL Entering SendTls13Finished

02/26/2026 10:10:10 growing output buffer

02/26/2026 10:10:10 Derive Finished Secret

02/26/2026 10:10:10 Derive Finished Secret

02/26/2026 10:10:10 wolfSSL Entering BuildTls13Message

02/26/2026 10:10:10 wolfSSL Entering EncryptTls13

02/26/2026 10:10:10 wolfSSL Leaving BuildTls13Message, return 0

02/26/2026 10:10:10 Derive Master Secret

02/26/2026 10:10:10 Derive Client Traffic Secret

02/26/2026 10:10:10 Derive Server Traffic Secret

02/26/2026 10:10:10 Derive Client Key

02/26/2026 10:10:10 Derive Server Key

02/26/2026 10:10:10 Derive Client IV

02/26/2026 10:10:10 Derive Server IV

02/26/2026 10:10:10 Shrinking output buffer

02/26/2026 10:10:10 wolfSSL Leaving SendTls13Finished, return 0

02/26/2026 10:10:10 accept state ACCEPT_FINISHED_SENT

02/26/2026 10:10:10 accept state TICKET_SENT

02/26/2026 10:10:10 wolfSSL Entering RetrySendAlert

02/26/2026 10:10:10 Entered embed receive.

02/26/2026 10:10:10 WSA embed receive A non-blocking socket operation could not be completed immediately.
: 10035

02/26/2026 10:10:10 wolfSSL error occurred, error = -323

02/26/2026 10:10:10 wolfSSL Entering wolfSSL_get_error

02/26/2026 10:10:10 wolfSSL Leaving wolfSSL_get_error, return -323

02/26/2026 10:11:54 BACNET_SC_INFO_MSG : The BACnet/SC Datalink Task has requested the Websocket Server Task to shut down.`

[lws-team]

-323 is "WANT_READ" in wolf-speak... that's not an error it's an indication that we should try again later... you should find out where in lws it receives this -323 and we can look at the code / how it's handling a WANT_READ.

[phelpsdc10]

Andy, Thanks for the prompt response. I have been delayed looking at 2 similar issues with wolfssl 5.7.6 which we have somewhat pinned down and wanted to ensure this issue did not share a root cause with them. (Connections not working on corporate network or laptops but working fine on private networks: possibly due to crowdstrike falcon/zscaler etc.) I did another build increasing client side timers from defaults to ~100 and stepped through. The path that is taken is: lws_ssl_client_connect1 -> lws_client_connect -> lws_tls_client_connect In lws_tls_client_connect I get a return value of -2 (LWS_SSL_CAPABLE_MORE_SERVICE_READ -> lws_client_create_tls which returns CCTLS_RETURN_RETRY -> lws_http_client_socket_service -> Nothing appears to happen and exits the function at completion -> rops_handle_POLLIN which returns LWS_HPI_RET_HANDLED -> lws_service_fd_tsl where breakpoints were hit at pollfd->revents = 0 and pt->inside_lws_service = 0 -> client_connect_4_established -> client_connect_3_connect Looking through documentation and using AI I don't see anything wrong up to this point but at this point it stepped into managed symbols I didn't currently have and I ran into one of our timeout exceptions. It was end of day so I will continue today with the server side. Is there anything that you see that appears incorrect in the step through so far, any better information I could provide or callstacks up to this point? Where would be a useful additional place to put a breakpoint after this? Or should I just continue with the server connect and embed read? Thanks greatly for your help, David

…

On Thu, Feb 26, 2026 at 1:10 PM Andy Green ***@***.***> wrote: *lws-team* left a comment (warmcat/libwebsockets#3550) <#3550 (comment)> -323 is "WANT_READ" in wolf-speak... that's not an error it's an indication that we should try again later... you should find out where in lws it receives this -323 and we can look at the code / how it's handling a WANT_READ. — Reply to this email directly, view it on GitHub <#3550 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADBCNDK3OS4NEM4XBB5VEX34N5AJRAVCNFSM6AAAAACWA47V4CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTSNRYGY2DGMZRGI> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[lws-team]

Does this help? I am wondering if the handshake both completed (n == 1) and happens to want to read more, in which case we have to prioritize the fact it completed.

diff --git a/lib/tls/openssl/openssl-client.c b/lib/tls/openssl/openssl-client.c
index d0b7e5f1..d8c21f26 100644
--- a/lib/tls/openssl/openssl-client.c
+++ b/lib/tls/openssl/openssl-client.c
@@ -565,12 +565,6 @@ lws_tls_client_connect(struct lws *wsi, char *errbuf, size_t elen)
        }
 #endif
 
-       if (m == SSL_ERROR_WANT_READ || SSL_want_read(wsi->tls.ssl))
-               return LWS_SSL_CAPABLE_MORE_SERVICE_READ;
-
-       if (m == SSL_ERROR_WANT_WRITE || SSL_want_write(wsi->tls.ssl))
-               return LWS_SSL_CAPABLE_MORE_SERVICE_WRITE;
-
        if (n == 1 || m == SSL_ERROR_SYSCALL) {
 #if defined(LWS_HAVE_SSL_set_alpn_protos) && \
     defined(LWS_HAVE_SSL_get0_alpn_selected)
@@ -594,6 +588,12 @@ lws_tls_client_connect(struct lws *wsi, char *errbuf, size_t elen)
                return LWS_SSL_CAPABLE_DONE;
        }
 
+       if (m == SSL_ERROR_WANT_READ || SSL_want_read(wsi->tls.ssl))
+               return LWS_SSL_CAPABLE_MORE_SERVICE_READ;
+
+       if (m == SSL_ERROR_WANT_WRITE || SSL_want_write(wsi->tls.ssl))
+               return LWS_SSL_CAPABLE_MORE_SERVICE_WRITE;
+
        if (!n) /* we don't know what he wants, but he says to retry */
                return LWS_SSL_CAPABLE_MORE_SERVICE;
 

[phelpsdc10]

Thanks for the diff. m = SSL_ERROR_WANT_READ n = -1 return = LWS_SSL_CAPABLE_MORE_SERVICE_READ

…

On Thu, Mar 5, 2026 at 9:10 AM Andy Green ***@***.***> wrote: *lws-team* left a comment (warmcat/libwebsockets#3550) <#3550 (comment)> Does this help? I am wondering if the handshake both completed (n == 1) and happens to want to read more, in which case we have to prioritize the fact it completed. diff --git a/lib/tls/openssl/openssl-client.c b/lib/tls/openssl/openssl-client.c index d0b7e5f1..d8c21f26 100644 --- a/lib/tls/openssl/openssl-client.c +++ b/lib/tls/openssl/openssl-client.c @@ -565,12 +565,6 @@ lws_tls_client_connect(struct lws *wsi, char *errbuf, size_t elen) } #endif - if (m == SSL_ERROR_WANT_READ || SSL_want_read(wsi->tls.ssl)) - return LWS_SSL_CAPABLE_MORE_SERVICE_READ; - - if (m == SSL_ERROR_WANT_WRITE || SSL_want_write(wsi->tls.ssl)) - return LWS_SSL_CAPABLE_MORE_SERVICE_WRITE; - if (n == 1 || m == SSL_ERROR_SYSCALL) { #if defined(LWS_HAVE_SSL_set_alpn_protos) && \ defined(LWS_HAVE_SSL_get0_alpn_selected) @@ -594,6 +588,12 @@ lws_tls_client_connect(struct lws *wsi, char *errbuf, size_t elen) return LWS_SSL_CAPABLE_DONE; } + if (m == SSL_ERROR_WANT_READ || SSL_want_read(wsi->tls.ssl)) + return LWS_SSL_CAPABLE_MORE_SERVICE_READ; + + if (m == SSL_ERROR_WANT_WRITE || SSL_want_write(wsi->tls.ssl)) + return LWS_SSL_CAPABLE_MORE_SERVICE_WRITE; + if (!n) /* we don't know what he wants, but he says to retry */ return LWS_SSL_CAPABLE_MORE_SERVICE; — Reply to this email directly, view it on GitHub <#3550 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADBCNDPJ46ECD3PJTNT27AD4PGKEVAVCNFSM6AAAAACWA47V4CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DAMBVG42TMOJVG4> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[lws-team]

I see... then does this help instead (fixes our not actually setting up to wait for READ event)

diff --git a/lib/tls/tls-client.c b/lib/tls/tls-client.c
index 41dd1c74..cd78751f 100644
--- a/lib/tls/tls-client.c
+++ b/lib/tls/tls-client.c
@@ -45,8 +45,11 @@ lws_ssl_client_connect1(struct lws *wsi, char *errbuf, size_t len)
        case LWS_SSL_CAPABLE_MORE_SERVICE_WRITE:
                lws_callback_on_writable(wsi);
                /* fallthru */
-       case LWS_SSL_CAPABLE_MORE_SERVICE:
        case LWS_SSL_CAPABLE_MORE_SERVICE_READ:
+               if (lws_change_pollfd(wsi, 0, LWS_POLLIN))
+                       return -1;
+               /* fallthru */
+       case LWS_SSL_CAPABLE_MORE_SERVICE:
                lwsi_set_state(wsi, LRS_WAITING_SSL);
                break;
        }
@@ -80,6 +83,8 @@ lws_ssl_client_connect2(struct lws *wsi, char *errbuf, size_t len)
                        lws_callback_on_writable(wsi);
                        /* fallthru */
                case LWS_SSL_CAPABLE_MORE_SERVICE_READ:
+                       if (lws_change_pollfd(wsi, 0, LWS_POLLIN))
+                               return -1;
                        lwsi_set_state(wsi, LRS_WAITING_SSL);
                        /* fallthru */
                case LWS_SSL_CAPABLE_MORE_SERVICE: