Page 1 of 1

[RESOLVED] Packages not installing (and other problems?)

Published: February 15, 2023 - 5:35 PM
by fcomte
Good morning,

Following the topic viewtopic.php?t=3344and having received no response, I embarked on reinstalling an additional WAPT 2.3 server on Debian 11 (following the official documentation) with the idea, in the worst case scenario, of starting from scratch.
One small drawback: I didn't have a completely clean PC available, so I had to reuse one that had previously hosted the console from my old server. As a result, despite uninstalling the console in the best way I could think of (via unins000.exe and choosing to keep nothing), it still found some of the old console's configuration. So I had to modify the console's configuration after reinstalling it, and it seemed to work, as I now have a functional console, without a host and without packages in the repository. I managed to generate an agent and install it manually on the PC where the console is located.
The problem is, after installation, following the official documentation, I'm experiencing strange behavior:
  • I imported a package from the Tranquil IT repository
  • I applied it to a machine (the machine where the console is installed)
  • When I click on my host and then click on "Checking for updates" it seems to work, at least there's no error message.
  • When I click on "Start installations", I get this message (I've expanded the dropdown menu to see the choices):
2023-02-15 17:18:45 - Host Upgrade.png
2023-02-15 17:18:45 - Host Upgrade.png (6 KB) Viewed 5286 times
This window seems to have changed compared to version 2.2.3, and I can't check or uncheck "Do not install packages whose applications are running." Furthermore, when I click OK, I don't get an error message, but the package doesn't install.
If it helps, in the "Tasks" tab, I see this:
2023-02-15 17_33_18 - Stains.png
2023-02-15 17_33_18 - Staches.png (22.89 KB) Viewed 5286 times
I hope you find a solution because I am indeed without a working WAPT server and have no idea how to find another one quickly...

Re: Packages not installing (and other problems?)

Published: February 16, 2023 - 1:50 PM
by fcomte
Hello,

I just did a clean install, including on the console PC (fresh install of Windows 10). And now I've got something that seems to be working.

At least, it seems to indicate that the problem stems from the console update. I feel like I followed the procedure correctly, but I must be missing something... Or, how do I completely uninstall the console from a PC so I can reinstall it properly?

Re: Packages not installing (and other problems?)

Published: February 20, 2023 - 2:43 PM
by blemoigne
Good morning,
There must be an inconsistency between the certificates used to sign your actions and packages (see personal certificate in console preferences) and those in the C:\Program Files (x86)\wapt\ssl directory of your agents.
Here's what could have caused this inconsistency during console installation:
waptsetup.png
waptsetup.png (14.22 KB) Viewed 5213 times
Bertrand

Re: Packages not installing (and other problems?)

Published: February 20, 2023 - 3:00 PM
by fcomte
Hello,
thank you very much for your reply.
So, I should select this option when reinstalling the console?

Re: Packages not installing (and other problems?)

Published: February 21, 2023 - 9:40 AM
by blemoigne
Hello,
no it's the opposite, you need to keep your configuration and therefore leave it unchecked.

Re: Packages not installing (and other problems?)

Published: February 21, 2023 - 10:37 AM
by fcomte
Ah, okay, thank you. I thought that was what I had done.
I understand that it might have had some effect on the need to reconfigure the console. However, I don't understand how that explains the final problem, namely the packages not installing.

Re: Packages not installing (and other problems?)

Published: February 24, 2023 - 2:40 PM
by dcardon
Hello Florent,

as mentioned in the documentation, WAPT security is based on asymmetric cryptographic keys (i.e., public key/private key). If the certificate, i.e., the public key, is not present on the machine, the WAPT agent will not accept the installation of packages that have been signed with a private key. In other words, the signing private key must match the certificate on the machine.

I'm marking this topic as resolved.

Regards,

Denis