[BETA] WAPT 1.5
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
Hello,
We use Wapt 1.5.1.8 in production at our clients' (Debian server)
Hubert.
We use Wapt 1.5.1.8 in production at our clients' (Debian server)
Hubert.
Tranquil IT
I have a feeling it's the WebSocket that's not working... in the WaptService logs on the client I have this:
Error in socket io connection ConnectionError (unexpected status code (401 Unauthorized)).
The permissions on the server in /var/www/wapt are correct.
I'm a bit stumped
Error in socket io connection ConnectionError (unexpected status code (401 Unauthorized)).
The permissions on the server in /var/www/wapt are correct.
I'm a bit stumped
Hello,
The message "(unexpected status code (401 Unauthorized))" means that the WebSocket connection is not authorized because either the computer is not registered on the server or the public key stored in the server's database does not match the computer's private key.
Indeed, in version 1.5, the computer creates a private/public key pair (using its FQDN as the object) and sends the X.509 certificate with the public key to the server during the initial registration (when installing the waptagent.exe client).
This key pair is then used to authenticate inventories sent by the client and to authenticate WebSocket connections.
If the key pair is generated after the waptservice has started, the computer will appear disconnected until the waptservice restarts.
If the computer is incorrectly registered or not registered at all, you can try "wapt-get register -ldebug" on the client with administrator privileges and restart the service ("net stop"). "waptservice" "net start waptservice"
If the key doesn't match, you can try removing the client from the inventory (this will remove the certificate/public key of the client in question from the database) and re-registering the client.
If it still doesn't work, it's a bug...
----
Regarding the second point, the message
"/var/www/wapt-host/45EC4D56-BA0D-3CFF-6F8C-8C1E31C46A3A.wapt" failed (2: No such file or directory)"
is normal as long as you haven't created a configuration for the machine in the console.
The machine tries to retrieve its target configuration with each update.
In wapt 1.3, machine packages were named with the machine's FQDN.
In wapt 1.5, machine packages are named by default with the machine's UUID.
A script allows you to recreate machine packages in bulk if necessary. (/opt/wapt/waptserver/scripts/migrate-hosts.py )
The message "(unexpected status code (401 Unauthorized))" means that the WebSocket connection is not authorized because either the computer is not registered on the server or the public key stored in the server's database does not match the computer's private key.
Indeed, in version 1.5, the computer creates a private/public key pair (using its FQDN as the object) and sends the X.509 certificate with the public key to the server during the initial registration (when installing the waptagent.exe client).
This key pair is then used to authenticate inventories sent by the client and to authenticate WebSocket connections.
If the key pair is generated after the waptservice has started, the computer will appear disconnected until the waptservice restarts.
If the computer is incorrectly registered or not registered at all, you can try "wapt-get register -ldebug" on the client with administrator privileges and restart the service ("net stop"). "waptservice" "net start waptservice"
If the key doesn't match, you can try removing the client from the inventory (this will remove the certificate/public key of the client in question from the database) and re-registering the client.
If it still doesn't work, it's a bug...
----
Regarding the second point, the message
"/var/www/wapt-host/45EC4D56-BA0D-3CFF-6F8C-8C1E31C46A3A.wapt" failed (2: No such file or directory)"
is normal as long as you haven't created a configuration for the machine in the console.
The machine tries to retrieve its target configuration with each update.
In wapt 1.3, machine packages were named with the machine's FQDN.
In wapt 1.5, machine packages are named by default with the machine's UUID.
A script allows you to recreate machine packages in bulk if necessary. (/opt/wapt/waptserver/scripts/migrate-hosts.py )
Tranquil IT
For the CentOS Wapt 1.5 repository, the packages are available here: https://wapt.tranquil.it/centos7/wapt-1.5/
They require PostgreSQL 9.4 and Nginx
: https://www.wapt.fr/fr/doc-1.5/Installa ... _wapt.html
They require PostgreSQL 9.4 and Nginx
: https://www.wapt.fr/fr/doc-1.5/Installa ... _wapt.html
Tranquil IT
