wolfSSL - Embedded SSL Library — -326 record layer version error

Re: -326 record layer version error

null@example.com (da) — Thu, 06 Nov 2025 16:58:10 +0000

it's not really helpful, since the issue would have already happened and at that point i would destroy the ssl object and make a new one to retry the connection, printing new logs would not help since the new connection would work
is there any way to clean way print the internal state of the object so that i maybe get more details?

Re: -326 record layer version error

null@example.com (anthony) — Wed, 05 Nov 2025 16:23:38 +0000

Hi DA.

Not exactly sure what kind of information you are looking to find out once its triggered. If you build in debug mode, once you see the return code in your application, you get turn on debug logging by calling wolfSSL_Debugging_ON().

Let me know if that suggestion is helpful.

Warm regards, Anthony

-326 record layer version error

null@example.com (da) — Wed, 05 Nov 2025 14:43:30 +0000

i have multiple machines with multiple binaries with multiple connections
sometimes (very rarely) i get the -326 error, meaning record layer version error
the problem is that i cannot just put the binaries in debug mode since there are too many connections, and i also do need the binaries to run smoothly
i would like to add some debugging code that is triggered only after this error is triggered
also, just to be clear this is not a mismatch of available encryption types between my binaries and the servers i am connecting to, since obviously the connections are retried and always work on the second try

does anyone have advice on how to approach this? and what specifically to log? because the ssl object does not seem to have public members that i can access