After several tests, I'm left with a wapt1.5 server that's not very usable... here's my problem:
- wapt1.5-3.jpg (99.26 KB) Viewed 5868 times
Thank you all (good webcasting too)
[SOLVED] waptconsole update error
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
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
Hi!
After several tests, I'm left with a wapt1.5 server that's not very usable... here's my problem: I'm stuck... the Running status no longer changes and each Check Update creates an error (irreversible)
Thank you all (good webcasting too)
After several tests, I'm left with a wapt1.5 server that's not very usable... here's my problem: I'm stuck... the Running status no longer changes and each Check Update creates an error (irreversible)
Thank you all (good webcasting too)
When there's an error, there are two possibilities:
- The WAPT client can't validate the signature of the request sent by the console: is the certificate deployed on the client the same as the one used to sign in the console?
- The WAPT client has disconnected from the server (and possibly reconnected with a different WebSocket session ID) since the grid was displayed.
You can get more information by checking "View debug information" in the "Display / Display Preferences" menu.
To clarify how it works:
- When the action is initiated on the client, the WAPT server sets the status to RUNNING while waiting for a response from the client
. - When the response comes back via the WebSocket channel, the status is updated in the database.
- The WAPT client can't validate the signature of the request sent by the console: is the certificate deployed on the client the same as the one used to sign in the console?
- The WAPT client has disconnected from the server (and possibly reconnected with a different WebSocket session ID) since the grid was displayed.
You can get more information by checking "View debug information" in the "Display / Display Preferences" menu.
To clarify how it works:
- When the action is initiated on the client, the WAPT server sets the status to RUNNING while waiting for a response from the client
. - When the response comes back via the WebSocket channel, the status is updated in the database.
Tranquil IT
In both cases...
It's important to verify that the certificate on the client is correct. <répertoire de wapt>\ssl is the same as the one you use to sign packets and actions in the console (defined by the personal_certificate_path in %LOCALAPPDATA%\waptconsole\waptconsole.ini)
It's important to verify that the certificate on the client is correct. <répertoire de wapt>\ssl is the same as the one you use to sign packets and actions in the console (defined by the personal_certificate_path in %LOCALAPPDATA%\waptconsole\waptconsole.ini)
Tranquil IT
