Tranquil IT Forum

Hello,
I'm experiencing unreachable workstations on the server again.
I launched debug mode to test and got the result below.
I checked the personal certificates in Tools > Preferences. I verified the associated key and everything is OK. I copied this key to Program Files (x86)\wapt\ssl to be sure it's in the .crt file, but it didn't help... If you have any ideas on how to resolve this issue, I would appreciate it.
Best regards

2023-03-10 08:13:15,970 [urllib3.connectionpool WaptTaskManager 7220] DEBUG Starting new HTTPS connection (1): 10.39.12.9:443
2023-03-10 08:13:18,900 [urllib3.connectionpool SocketIOClient 13292] DEBUG Starting new HTTPS connection (1): 10.39.12.9:443
2023-03-10 08:13:18,931 [waptws SocketIOClient 13292] WARNING Exception SSLError(MaxRetryError("HTTPSConnectionPool(host='10.39.12.9', port=443): Max retries exceeded with url: /get_websocket_auth_token (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self signed certificate (_ssl.c:1131)')))"), waiting 60s before retrying
2023-03-10 08:13:26,008 [waptcore WaptTaskManager 7220] DEBUG DB Start transaction
2023-03-10 08:13:29,513 [waptcore WaptTaskManager 7220] DEBUG Transaction took too much time: 3.504660129547119

Hello Jean-Philippe,

what version of WAPT are you using? What is the server OS? What is the client OS?

The machine is unable to validate the server's HTTPS certificate. You need to either correct the certificate issue (is the CA missing locally on the machine?), pin the server certificate to the machine, switch to HTTP without TLS, or ignore the certificate altogether.

Regards,

Denis

Hello,

since I haven't received a response, I assume the HTTPS certificate issue has been resolved... I'm marking this topic as resolved.

Regards,

Denis

Hello,
no, I'm still in the testing phase.
I don't understand why the workstations have different SHA256 hashes. Some start with 636xxxxxx, others with c5b75xxxxxxxx. Shouldn't the hash be the same for all workstations?
Furthermore, I just noticed that workstations with different hashes were correctly identified by the console interface. So my problem probably isn't related to the certificate.
The client workstation I'm using for the console interface is running Windows 10, and the server is running Windows Server 2019.
WAPT console version 2.3.0.13470.
Regards

Hello Jean-Philippe,

the client certificate fingerprint issue is different from the server's HTTPS certificate issue. Please start a new thread. Regarding the fingerprints, please specify where you obtained them. I'm locking this topic.

Regards,

Denis