Tranquil IT Forum

Hello,

On a Linux Ubuntu 22.04 server, I recently updated WAPT from version 2.4 to version 2.6.

Although I followed the update procedure exactly, including the post-configuration steps, all clients now appear as disconnected.

On a new computer, after disabling the firewall and manually installing the WAPT agent version 2.6, the agent appears correctly in the console, but it still shows as "DISCONNECTED".

Could you please help me resolve this issue?

Thank you in advance for your assistance.

Best regards,



- Installed WAPT version: 2.6
- Server OS: Linux
- Administration/package creation machine OS: Windows 10

Hello lowix,

lowix wrote: ↑Nov 28, 2024 - 4:30 PM On a Linux Ubuntu 22.04 server, I recently updated WAPT from version 2.4 to version 2.6.

Although I followed the update procedure to the letter, including the post-configuration steps, all clients now appear as disconnected.

On a new computer, after disabling the firewall and manually installing the WAPT agent version 2.6, the agent appears correctly in the console, but it still shows as "DISCONNECTED".

Could you help me resolve this issue?

It's going to be difficult to solve the problem with so little information... And if you want someone to help you solve your problem, it's more like a support ticket than a help forum...

Which upgrade documentation did you follow exactly? The 2.5 to 2.6 upgrade or the 2.4 to 2.6 upgrade [1]? Is there any SSL interception, reverse proxies, etc.? Are there any server-side and client-side logs?

Sincerely,

Denis


[1] https://www.wapt.fr/en/doc/wapt-server- ... 2-4-to-2-6

Hello Mr. Cardon,

Thank you for your reply!

I realize that my first message lacked detail. I will therefore provide some clarification.

First, let me introduce myself: I work for a university and I have deployed WAPT in three different universities over the past 10 years. These projects have always been successful, with full support from my IT colleagues and users. I would also like to sincerely thank you for the quality of your solution, and I will be sure to visit your booth at the next JRES.

Currently, I manage a small network of about 100 workstations in a lab. The infrastructure is quite simple: a WAPT server (VM) running Linux, accessible only by machines on its private VLAN, without any special security measures such as proxies or SSL interception. The agent is deployed via GPO (I have already started deploying version 2.6 of the agent).

I started with version 2.4, which installed and configured without any problems, and everything worked perfectly for about a year.

Recently, I decided to upgrade to version 2.6, and that's where the difficulties began.
I followed the documentation: https://www.wapt.fr/en/doc/wapt-server- ... 2-4-to-2-6.

I didn't encounter any particular difficulties during the upgrade, and I don't think I missed any steps, but it's still possible I might have overlooked something important.

Perhaps I should have upgraded to version 2.5 first before moving to 2.6?

In any case, all workstations now appear as "DISCONNECTED".

I also tested installing an administration console on a freshly installed Windows 10 VM, but the problem persists.

I am available to provide more information or logs if that would help you better understand and resolve this issue.

Thank you very much!

Hello lowix,

lowix wrote: ↑Dec 2, 2024 - 12:12 PM Thank you for your reply!

I realize that my first message lacked detail. I will therefore provide some clarification.

First, let me introduce myself: I work for a university and I have deployed WAPT in three different universities over the past 10 years. These projects have always been successful, with full support from my IT colleagues and users. I would also like to sincerely thank you for the quality of your solution, and I will be sure to visit your booth at the next JRES.

I'd love to, I'll be at the booth. It's always nicer to put a face to a username

Currently, I manage a small network of about 100 workstations in a lab. The infrastructure is quite simple: a WAPT server (VM) running Linux, accessible only by machines on its private VLAN, without any special security measures like proxies or SSL interception. The agent is deployed via GPO (I've actually started deploying version 2.6 of the agent).

I began with version 2.4, which installed and configured without any problems, and everything worked perfectly for about a year.

Recently, I decided to upgrade to version 2.6, and that's where the difficulties began.
I followed the documentation: https://www.wapt.fr/en/doc/wapt-server- ... 2-4-to-2-6

Okay, very well, there are a couple of things that changed in 2.5, so it's important to pay close attention to all the points mentioned in this section. The biggest change is the requirement to use HTTPS.

I didn't encounter any particular difficulties during the update and I don't think I missed any steps, but it's always possible I might have overlooked something important.

Perhaps I should have upgraded to version 2.5 first before moving on to 2.6?

No, not at all, we just abandoned the direct upgrade from 1.8 to 2.6, but otherwise for all versions in 2.x you can upgrade directly.

In any case, all workstations now appear as "DISCONNECTED".

I also tested installing an administration console on a freshly installed Windows 10 VM, but the problem persists.

When you run a wapt-get update / upgrade / install / search command locally, does the machine communicate properly with the server?

The DISCONNECTED message indicates that the WebSocket, which allows the agent to receive instructions from the server, is not being established. The install/upgrade process uses HTTPS, not WebSocket.

Are the agents correctly configured with an HTTPS server URL? Is the certificate self-signed, internal PKI, commercial, or Let's Encrypt?

Are there other things hosted on the same server? Did you restart the postconf?

Sincerely,

Denis

Hello Denis,

Thank you for your detailed feedback.

Yes, the agents are correctly configured with an HTTPS server URL, and a Wapt-Get update on a client machine seems to work: I realize that during the initial installation of version 2.4, I didn't configure an HTTPS certificate. This could explain the communication problem.

I will take care of installing an HTTPS certificate and I will keep you informed of the results.

Thank you again for your help!

Yours sincerely,

Hello Denis,

Thank you so much for your invaluable help regarding the client disconnection issue after updating to WAPT version 2.6.

Thanks to your advice, I was able to identify that the lack of a specific SSL certificate was the cause of the problem.

After installing the certificate provided by my university's IT department, everything is working perfectly again!

Thank you so much!!!

Good evening Lowix,

thank you for the feedback.

See you soon at the JRES!

Denis