Ah, after that, it's much better! The upgraded machines are now showing as OK!

Thank you so much.
Have a good day.

Like this?
But that doesn't change anything... is there a specific procedure to follow?

- The version is PostgreSQL 9.4.19

- Here's what I retrieved from the logs:
Jul 3 00:04:05 EOS waptserver[1047]: 2022-07-03 00:04:05,930 [waptserver] CRITICAL Get_websocket_auth_token failed ProgrammingError("ERROR: Syntax error on or near 'ON'\nLINE 1: ...519b9b0-d697-11e7-8d03 ...

In Pg, the requested database extraction

Here is the result:

2022-07-06 10:26:36,855 [waptcore MainThread 912] DEBUG Thread 912 is connecting to wapt db
2022-07-06 10:26:41,647 [waptcore MainThread 912] DEBUG DB Start transaction
2022-07-06 10:26:41,656 [waptcore MainThread 912] DEBUG DB commit
2022-07-06 10:26:41,692 [waptservice ...

I deployed my agent 2.2 on a workstation by doing the manual install to test but the workstation still does not appear as OK (reachable).

I'm sorry, but I'm not sure I understand.
Do I need to downgrade my server version from 2.2 to 1.8.1, then update it to 1.8.2, and then upgrade it to 2.2?

Hello,

Wapt version: 2.2
Server: Debian 11
Clients: Windows 10

Hello,
I recently migrated from version 1.8.1 to 2.2.
The clients now appear disconnected but OK in status, and the WAPT client version has updated automatically on the clients.

I checked the time...

Strangely, it's empty.
I only have [global]

Hello,
I just upgraded my WAPT server from 1.8 to 2.2 (discovery), however, I'm encountering a problem.
The URL of the main repository is https://store.wapt.fr/wapt, and the URL of my local server is the same as before.
My server is running Debian 10.
I followed the procedure correctly. I tried to...