Review - Following update 1.7.4.6155, there are package management issues

[avondra]

Wapt version 1.7.4.6155
Server OS: CentOS 7.6
Admin OS: Windows 10

Hello,
Following my MD5 verification problem, I upgraded Wapt from 1.6.7 to the latest version 1.7.4. I no longer have the error, but package installations and updates no longer work. I don't get an error message, but there is no longer any interaction with clients.
Can you shed some light on this new malfunction? It's also very urgent because I need to deploy a softphone by tomorrow evening...
Thank you for your help.

[avondra]

Continuation,
Little info, a strange message in debug mode when I launch the installation on a client which seems a little 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:\private\wapt-private.pem: Unable to load key c:\private\wapt-private.pem
DEBUG:root:SUCCESS key c:\private\wapt-private.pem match certificate c:\private\wapt-private.crt
{"msg":"1 actions launched, 0 errors, 0 skipped, 0 server errors","success":true,"request_time":null,"result":[]}

[avondra]

Can no one give me feedback?
Thanks

[avondra]

Okay, I'm still answering myself... by adding to the discussion.
It seems to be an SSL certificate issue because when I check the certificate or when I query the Wapt server using the wapt-get command, I get an error: clients cannot communicate with the server, hence the inability to perform updates:
TypeError: argument of type 'NoneType' is not iterable.
It looks like a python bug, I'm in 2.7 is this a possible solution and do you have a workaround

C:\wapt>wapt-get.exe register
Using config file: C:\wapt\wapt-get.ini
Registering host against server: https://unc-srv-susi.cfu.local
System Power Controls
FATAL ERROR: SSLError: HTTPSConnectionPool(host='unc-srv-susi.cfu.local', 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')],)",),))

C:\wapt>wapt-get enable-check-certificate
Using config file: C:\wapt\wapt-get.ini
Server certificate: C:\wapt\ssl\server\unc-srv-susi.cfu.local.crt
FATAL ERROR: TypeError: argument of type 'NoneType' is not iterable

[htouvet]

Are you using a self-signed certificate for the nginx server on the server side?

If so, is this certificate identical to the one in C:\wapt\ssl\server\unc-srv-susi.cfu.local.crt?

If this certificate is signed by a CA, does the server-side PEM file contain the entire certificate chain (intermediate and root CAs)?

[avondra]

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.

[avondra]

Hello,
Still no response...
I've 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, request: "GET /wapt-host/4C4C4544-0031-3310-8051-B4C04F324732.wapt HTTP/1.1", host: "xxxxxxxxxx"

I have to create this file manually, which isn't normal; since the version upgrade, there have been problems They're piling up...
Help!!

[avondra]

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

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

What can I do, since the installation via WAPT Self-Service works on the client?

Thank you for your help.

[avondra]

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 with the various WAPT version upgrades, and I still consider it an essential tool.
Do I have to resign myself to reinstalling my server from scratch and losing all my installation history?

[sfonteneau]

Good morning

The easiest way to help us is by running a few commands (you've already done some of them), can you send us the result?

Code: Select all

wapt-get update -f 

Code: Select all

wapt-get register 

The contents of your agent's wapt-get.ini file
The console's waptconsole.ini (%localappdata%\waptconsole\waptconsole.ini)

Can you also run this (starts the debug mode agent):

Code: Select all

"c:\Program Files (x86)\wapt\runwaptservice.bat" -ldebug

Then perform actions using the console and send us back the result from the agent in debug mode?

The files:

• C:\Program Files (x86)\wapt\ssl\*.crt
• C:\Program Files (x86)\wapt\ssl\server\*.crt
• C:\Program Files (x86)\wapt\private\*.crt

For the server, this file:

Code: Select all

/opt/wapt/waptserver/ssl/cert.pem

Also the crt file indicated in the waptconsole.ini file (%localappdata%\waptconsole\waptconsole.ini)

Also check the time:

• From the post that has the wapconsole
• From agent Wapt
• And from the Wapt server

On Windows computers you can check the time like this:

Code: Select all

waptpython
import datetime
datetime.datetime.utcnow()

Yes, because time zone differences, daylight saving time, etc., it's complicated...

Simon