[BETA] WAPT 1.5 - Console connection error

[hasop]

Hello,

I tested the installation of versions 1.5.1.5 and 1.5.1.11 on a Windows Server 2008 machine. I get the same result:
When I try to connect to the console from my Windows 7 Pro client, I get the message:
Error connecting with SSL
error:14090086:SSL routines:ssl3_get_server_certificate:certificate verify failed

[sfonteneau]

Can you click on the small wrench icon?

Can you check if the "Verify HTTPS certificate" box is checked?

If version 1.3 was previously installed on the machine, there's still a bug; simply click the "Verify" button and the problem will be resolved.

If the box is checked, you can uncheck it and click "Verify" to confirm functionality without verifying the HTTPS certificate.

We will be releasing the documentation related to HTTPS verification shortly.

[hasop]

Perfect!

The HTTPS box wasn't checked, but a "Check" allowed the console to launch correctly. Indeed, there had been a 1.3.13 installation previously. I had uninstalled the agent and deleted the data directory.

However, I don't see my client machine in the list (only the server), even though "Update software inventory" doesn't return an error and the service is running.

[hasop]

Is there anything else I need to do to make the client visible in the console?

[hasop]

Here is what I have:
C:\Windows\system32>wapt-get register My PC
FATAL ERROR: SSLError: HTTPSConnectionPool(host='XXXXXX', port=
443): Max retries exceeded with url: /add_host (Caused by SSLError(SSLError("bad
handshake: Error([('SSL routines', 'tls_process_server_certificate', 'certificate
verify failed')],)",),))

[sfonteneau]

It appears you have enabled HTTPS certificate verification on the WAPT agent side...

https://www.wapt.fr/wapt-1.5/Configurat ... icate.html

[hasop]

I don't remember activating that function, but indeed, setting it to 0 makes it work better.

Thank you.

[sfonteneau]

Some versions of Wapt 1.5 enable this setting by default!

But the official release is coming soon!