[Libwebsockets] LWS v3.0.0 Windows x64 Client connect issue.
mookimoo73 at gmail.com
Mon May 14 14:22:21 CEST 2018
I have made some progress on this this morning and I see that when I
compile the Server and Client and using #ifdef LWS_WITH_SSL in the
code and excluding it from the Makefile the connection is made from
the Windows client and works as expected.
However, with the Linux client, which by coincidence, is on the same
machine as the server, and connecting in both WSS and WS modes I can
only assume that the failure of Windows to initiate a WSS connection
is either down to a Windows 2012 R2 ism or my stupidity. So with the
latter being the favourite I am working on the assumption that the
context's ssl_cert_filepath, ssl_private_key and ssl_ca_filepath are
not required on Windows as LWS will use the internal certificate store
to validate the server certificate presented to it, is this assumption
If this is correct then it would appear that this does not work as I
have both the Intermediate and Root certificates installed on the
Windows machine, if I am wrong then I would appreciate some input as
to where I might be going wrong.
On 11 May 2018 at 16:20, Mooki Moo <mookimoo73 at gmail.com> wrote:
> I have an issue using an x64 build of LWS on Windows 10 Pro. I have
> built OpenSSL (v1.1.0h) with it passing all of the tests prior to
> I configured LWS using the CMake (GUI) and built using Visual Studio
> 17 (CE) but when I try to connect to the WSS server (running on Arch
> Linux) I get a “client connect failed” via the
> LWS_CALLBACK_CLIENT_CONNECTION_ERROR for each of my protocols.
> When using either my own VS built LWS test client or the Appveyor
> built one on Windows I see a notice in the console that “SSL
> disabled”, but using the test client on Linux I see “Using SSL”. The
> code used for both clients is identical with the Windows client code a
> copy of the Linux one.
> It may be worth while pointing out that the LWS version on the server
> is v2.4.2-1 and the Windows is built using the new v3.0.0 so the only
> thing I can conclude is a version incompatibility, can anyone confirm
> or deny this please.
More information about the Libwebsockets