Hello,
have you found a solution? I'm also experiencing this kind of problem on some computers, with no real hardware or software differences, about ten out of 120 computers.
Thank you.

It was a bad copy/paste on my part; the situation hasn't changed, there's still no response when I try to install it.
Do I have to reinstall the server from scratch and lose the history?

Thank you for your reply. Here are the results of the different commands I had already run:

C:\WINDOWS\system32>wapt-get update -f
Using config file: C:\Program Files (x86)\wapt\wapt-get.ini
Update package list from https://unc-srv-susi.cfu.local/wapt, https://unc-srv-susi.cfu ...

Hello,
I don't understand this deafening silence...
Is there no developer who might have an idea to help me track down this bug?
I've already uninstalled and reinstalled my console, recreated my keys, but nothing works.
I've never had any problems during previous upgrades...

From my research, it seems to be a problem with the private key, which isn't being accepted when I push updates. However, I checked the interface and everything looks OK, but I saw this alert in the console debug:

EWaptCertificateUntrustedIssuer: None of certificates ("wapt-private","wapt ...

Hello,
Still no response...
I also noticed errors when adding new hosts:
2019/09/09 11:57:21 [error] 1530#0: *159902 open() "/var/www/html/wapt-host/4C4C4544-0031-3310-8051-B4C04F324732.wapt" failed (2: No such file or directory), client: 192.203.100.44, server: xxxxxxxxxx ...

Yes, I'm using a self-signed certificate for the nginx server on the server side.
The certificate is identical to the one in C:\wapt\ssl\server\unc-srv-susi.cfu.local.crt.
The certificates are identical, but I'm getting these errors and nothing happens in the waptconsole when I update the clients.

Okay, I'm still answering myself... by adding to the discussion.
It seems to be an SSL certificate issue because when I verify the certificate or when I query the WAPT server using the `wapt-get` command, I get an error: clients cannot communicate with the...

Can no one give me feedback?
Thanks

A
quick update: I'm getting a strange message in debug mode when I run the installation on a client that seems a bit contradictory:

DEBUG:urllib3.connectionpool:https://unc-srv-susi.cfu.local:443 "GET /wapt-host/4C4C4544-0056-5A10-8031-CAC04F4D3432.wapt HTTP/1.1" 200 2851
DEBUG:root:ERROR for c ...