Hello,
I'm unable to install packages on the machines where the WAPT agent has been deployed.
In the admin console, I can add packages to the machines, but when I apply the updates, the packages show errors. I also have a package that shows an error and corresponds to my UUID.
Both packages are therefore stuck in a pending state.
Communication between the client and the server is OK.
Do you have a solution?
Thank you.
[SOLVED] Unable to install packages
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
The solution is to have the same keys on both machines.
I have two computers with the admin console.
Each has a different key, which is why I couldn't install the packages on another machine with a different key.
So I retrieved the key from one of the machines and installed it on the other.
I also created a new agent with the new key.
I have two computers with the admin console.
Each has a different key, which is why I couldn't install the packages on another machine with a different key.
So I retrieved the key from one of the machines and installed it on the other.
I also created a new agent with the new key.
-
dcardon
- WAPT Expert
- Messages: 1932
- Registration: June 18, 2014 - 09:58
- Location: Saint Sébastien sur Loire
- Contact :
Hello Maxime,
I recommend you take a look at https://www.wapt.fr/fr/doc/wapt-concept ... -principle
Sincerely,
Denis
Indeed. The private signing key must match the certificate deployed on the workstation.Maxime wrote: ↑June 7, 2019 - 2:53 PM The solution is to have the same keys on both machines.
I have two computers with the admin console.
Each has a different key, which is why I couldn't install the packages on another machine with a different key.
So I retrieved the key from one of the machines to install it on the other.
I also created a new agent with the new key.
I recommend you take a look at https://www.wapt.fr/fr/doc/wapt-concept ... -principle
Sincerely,
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
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
