Page 1 of 1

PC unreachable

Published: September 1, 2025 - 1:41 PM
by dsi_oll
Good morning,
Since installing the latest version, all the PCs in my network appear unreachable.
In the access.log file, I have this kind of message

Code: Select all

192.168.0.1 - NONE - [01/Sep/2025:13:36:47 +0200] "HEAD /wapt/Packages HTTP/1.1" 200 0 "-" "waptconsole/2.6.0.17392W"
192.168.0.1 - NONE - [01/Sep/2025:13:36:47 +0200] "GET /api/v3/get_ad_ou_split HTTP/1.1" 200 305 "-" "waptconsole/2.6.0.17392W"
192.168.0.1 - NONE - [01/Sep/2025:13:36:47 +0200] "POST /api/v3/hosts HTTP/1.1" 200 28965 "-" "waptconsole/2.6.0.17392W"
192.168.0.1 - NONE - [01/Sep/2025:13:36:47 +0200] "GET /api/v3/host_data?field=installed_packages&uuid=desktop-t57l0jn.ollioules.fr HTTP/1.1" 200 2993 "-" "waptconsole/2.6.0.17392W"
192.168.0.1 - NONE - [01/Sep/2025:13:36:47 +0200] "GET /licences.json HTTP/1.1" 200 2 "-" "waptconsole/2.6.0.17392W"
192.168.0.1 - NONE - [01/Sep/2025:13:36:47 +0200] "GET /api/v3/get_current_user_acls HTTP/1.1" 200 78 "-" "waptconsole/2.6.0.17392W"
192.168.0.1 - NONE - [01/Sep/2025:13:36:48 +0200] "GET /api/v3/reported_managed_hosts_count HTTP/1.1" 200 28 "-" "waptconsole/2.6.0.17392W"
192.168.0.1 - NONE - [01/Sep/2025:13:36:48 +0200] "HEAD /wapt/Packages HTTP/1.1" 200 0 "-" "waptconsole/2.6.0.17392W"
192.168.0.1 - NONE - [01/Sep/2025:13:36:49 +0200] "GET /api/v3/host_data?field=installed_packages&uuid=pc1240.ollioules.fr HTTP/1.1" 200 3533 "-" "waptconsole/2.6.0.17392W"
Thanks in advance.
Best regards,
Fabien

Latest version on Windows server

Re: PC unreachable

Published: September 1, 2025 - 2:03 PM
by blemoigne
Hello,
we would need the Waptservice logs for the problematic agents.
Best regards,
Bertrand

Re: PC unreachable

Published: September 4, 2025 - 8:40 AM
by dsi_oll
Here is an example:

Code: Select all

2025-09-04 08:37:12,861 [waptws SocketIOClient 2756] WARNING Exception ConnectionError('One or more namespaces failed to connect'), waiting 60s before retrying
2025-09-04 08:38:12,879 [wapttasks SocketIOClient 2756] INFO Socketio connection params have changed. Socketio needs reconnect
2025-09-04 08:38:12,879 [wapttasks SocketIOClient 2756] INFO Creating socketio client: https://waptsrv.contoso.com:443 client auth cert: ('C:\\Program Files (x86)\\wapt\\private\\oll-appli.contoso.com.crt', 'C:\\Program Files (x86)\\wapt\\private\\oll-appli.contoso.com.pem') proxies: None verify_cert: False
2025-09-04 08:38:12,879 [wapttasks SocketIOClient 2756] INFO Connecting Socketio to https://waptsrv.contoso.com:443
2025-09-04 08:38:14,132 [waptws Thread-3347 7208] WARNING WebSocket connection was closed, aborting
2025-09-04 08:38:14,132 [waptws SocketIOClient 2756] WARNING Exception ConnectionError('One or more namespaces failed to connect'), waiting 60s before retrying
2025-09-04 08:39:14,144 [wapttasks SocketIOClient 2756] INFO Socketio connection params have changed. Socketio needs reconnect
2025-09-04 08:39:14,144 [wapttasks SocketIOClient 2756] INFO Creating socketio client: https://waptsrv.contoso.com:443 client auth cert: ('C:\\Program Files (x86)\\wapt\\private\\oll-appli.contoso.com.crt', 'C:\\Program Files (x86)\\wapt\\private\\oll-appli.contoso.com.pem') proxies: None verify_cert: False
2025-09-04 08:39:14,144 [wapttasks SocketIOClient 2756] INFO Connecting Socketio to https://waptsrv.contoso.com:443
2025-09-04 08:39:15,265 [waptws Thread-3350 7428] WARNING WebSocket connection was closed, aborting
2025-09-04 08:39:15,265 [waptws Thread-3349 5868] WARNING WebSocket connection was closed, aborting
2025-09-04 08:39:15,265 [waptws SocketIOClient 2756] WARNING Exception ConnectionError('One or more namespaces failed to connect'), waiting 60s before retrying

Re: PC unreachable

Published: September 4, 2025 - 9:06 AM
by dcardon
Hello Fabien,

which version did you upgrade from? Version 2.4, 2.5, or 2.6.0.x?

Do you have filtering firewalls with wildcard certificates for SSL interception?

Are the agents correctly configured for HTTPS?

Regards,

Denis

Re: PC unreachable

Published: September 4, 2025 - 10:11 AM
by dsi_oll
Hello Denis and thank you for taking the time to read my problem.
dcardon wrote: Sep 4, 2025 - 9:06 AM Hello Fabien,

which version did you upgrade from? Version 2.4, 2.5, or 2.6.0.x? From 2.6.0.x.

Do you have filtering firewalls with wildcard certificates for SSL interception? No.

Are the agents correctly configured for HTTPS? How can I verify this?

Best regards,

Denis

Re: PC unreachable

Published: September 5, 2025 - 5:26 PM
by blemoigne
Good morning,
The WAPT server's HTTPS certificate should be checked:

Code: Select all

/opt/wapt/waptserver/ssl/cert.pem 
Is this a commercial certificate or one from your PKI? If so, does the cert.pem file contain the complete chain (certificate + any intermediate CAs + Root CA)?
Are the agents correctly verifying this certificate? (verify_cert parameter in the wapt-get.ini file)?
Are the wapt_server and repo_url properties of the wapt-get.ini file correctly set to https?

Best regards,
Bertrand

Re: PC unreachable

Published: September 8, 2025 - 9:43 AM
by dsi_oll
Indeed, I think that's where the problem lies.
I'm using a Windows server, and the SSL certificate is located in the nginx folder. Was this folder automatically generated by WAPT?
Can I renew it?

Is the certificate that appears on this line in the server configuration the same one that should be in the verify cert path?

Code: Select all

clients_signing_key = c:\wapt\conf\ca-WAPTSRV.XXX.fr.pem
clients_signing_certificate = c:\wapt\conf\ca-WAPTSRV.XXX.fr.crt
Thanks in advance