[RESOLVED] Following an upgrade from 2.4.0 to 2.5.5, all clients were disconnected

Questions about WAPT Server / Requests and help related to the WAPT server
Forum Rules
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
Locked
MaximeJ
Messages: 8
Registration: May 26, 2024 - 09:28

May 29, 2024 - 3:34 PM

- Installed WAPT version: 2.4.0 for clients, server and admin machine in 2.5.5
- Server OS: Debian 12.5
- Operating system of the administration/package creation machine: Windows 11

Hello, following a question asked yesterday (viewtopic.php?t=3908) and whose fix simply consisted of installing the latest version of WAPT, which we did today, no client can now communicate with the wapt server.

We exhibit similar behavior to these two other subjects:
viewtopic.php?t=3784
viewtopic.php?t=3785

Note that all customers appear in "disconnected", including the one on my administration workstation which I updated manually.


To begin with, running waptdeploy (which is also up to date) fails with the following error:
.\waptdeploy.exe --hash=d1267cb848231ed1c07f831e2883269ae8e2060aa51f4345e45d035a2b4b9440 --minversion=2.5.5.15602 --wait=15 --waptsetupurl=https://waptserveur.dom.local/api/v3/ge ... tagent.exe --setupargs="/LOG=C:\ProgramData\IT\Logs\WAPTAgentGPO.log"

{"hash":"d1267cb848231ed1c07f831e2883269ae8e2060aa51f4345e45d035a2b4b9440","minversion":"2.5.5.15602","wait":"15","waptsetupurl":"https://waptserver.dom.local/api/v3/get ... tputFormat"}
WAPT version: 2.4.0.14080
WAPT required version: 2.5.5.15602
Wapt agent path: C:\Users\ADM-PD~1\AppData\Local\Temp\waptagent.exe
Wget new waptagent from https://waptserver.dom.local/api/v3/get_waptagent_exe/
Trying to reach https://waptserver.dom.local/api/v3/get_waptagent_exe/...
Expecting hash sha256: d1267cb848231ed1c07f831e2883269ae8e2060aa51f4345e45d035a2bxxxx
Using proxy:
Error trying to get https://waptserver.dom.local/api/v3/get_waptagent_exe/ : Error downloading https://waptserver.dom.local/api/v3/get_waptagent_exe/: [EHttpSocket] THttpClientSocket.WGet: waptserver.dom.local:443/api/v3/get_waptagent_exe/ failed as 404 Not Found... sleeping
Delete sheduled task "fullwaptupgrade"
An unhandled exception occurred at $00603D02:
Exception: Error downloading https://waptserver.dom.local/api/v3/get_waptagent_exe/: [EHttpSocket] THttpClientSocket.WGet: waptserver.dom.local:443/api/v3/get_waptagent_exe/ failed as 404 Not Found
$00603D02
$00605402

On my administration workstation with the manually installed 2.5.5 client, I keep getting these messages in a loop in the service logs:
2024-05-29 15:53:14,013 [waptws SocketIOClient 3352] WARNING Exception ConnectionError('One or more namespaces failed to connect'), waiting 60s before retrying
2024-05-29 15:54:14,034 [wapttasks SocketIOClient 3352] INFO Socketio connection params have changed. Socketio needs reconnect
2024-05-29 15:54:14,034 [wapttasks SocketIOClient 3352] INFO Creating socketio client: https://waptserver.dom.local:443 client auth cert: ('C:\\Program Files (x86)\\wapt\\private\\w-adm-mju.si.local.crt', 'C:\\Program Files (x86)\\wapt\\private\\w-adm-mju.si.local.pem') proxies: None verify_cert: True
2024-05-29 15:54:14,034 [wapttasks SocketIOClient 3352] INFO Connecting Socketio to https://waptserver.dom.local:443
2024-05-29 15:54:15,798 [waptws SocketIOClient 3352] WARNING Exception ConnectionError('One or more namespaces failed to connect'), waiting 60s before retrying
I tried the following commands on another computer:

Code: Select all

wapt-get update
wapt-get install dgt-waptupgrade
which worked well, my client updated. However, I now see the same thing appearing in the logs as on my admin machine:
[wapttasks SocketIOClient 10092] INFO Creating socketio client: https://waptserver.dom.local:443 client auth cert: ('C:\\Program Files (x86)\\wapt\\private\\w-doh-mju.si.local.crt', 'C:\\Program Files (x86)\\wapt\\private\\w-doh-mju.si.local.pem') proxies: None verify_cert: True
[wapttasks SocketIOClient 10092] INFO Connecting Socketio to https://waptserver.dom.local:443
[waptws SocketIOClient 10092] WARNING Exception ConnectionError('One or more namespaces failed to connect'), waiting 60s before retrying

I have reviewed the other questions asked on the forum, and we have tried the solutions provided, including 'making sure that the postconf was executed correctly,' but without success so far.
Do you have any idea where this problem might be coming from?

THANKS,
Maxim
MaximeJ
Messages: 8
Registration: May 26, 2024 - 09:28

May 29, 2024 - 5:38 PM

The issue can be marked as resolved.
Our problem stemmed "simply" (I say simply, but thank you to the support team) ;) ) of an old remnant in the waptserver.ini server configuration file:

Code: Select all

use_ssl_client_auth = False
This line, which was still present, had to be removed as it conflicted with the new security features of version 2.5. Once removed and the postconf script restarted, all our clients reconnected within a minute.

THANKS.
User avatar
dcardon
WAPT Expert
Messages: 1929
Registration: June 18, 2014 - 09:58
Location: Saint Sébastien sur Loire
Contact :

May 30, 2024 - 09:17

Hello Maxime,
thank you for the feedback :-)
Denis
Denis Cardon - Tranquil IT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
Locked