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

Share your tips or issues concerning the WAPT Console or WAPT Agent here
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
Locked
User avatar
fcomte
Messages: 18
Registration: February 1, 2023 - 11:15

February 15, 2023 - 5:35 PM

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 5279 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 5279 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...
- Installed WAPT version: 2.4.0.14080 Discovery
- Server OS: Debian GNU/Linux 11 (bullseye)
- Administration/package creation machine OS: Windows 10
User avatar
fcomte
Messages: 18
Registration: February 1, 2023 - 11:15

February 16, 2023 - 1:50 PM

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?
- Installed WAPT version: 2.4.0.14080 Discovery
- Server OS: Debian GNU/Linux 11 (bullseye)
- Administration/package creation machine OS: Windows 10
User avatar
blemoigne
Messages: 178
Registration: July 17, 2020 - 11:29

February 20, 2023 - 2:43 PM

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 5206 times
Bertrand
User avatar
fcomte
Messages: 18
Registration: February 1, 2023 - 11:15

February 20, 2023 - 3:00 PM

Hello,
thank you very much for your reply.
So, I should select this option when reinstalling the console?
- Installed WAPT version: 2.4.0.14080 Discovery
- Server OS: Debian GNU/Linux 11 (bullseye)
- Administration/package creation machine OS: Windows 10
User avatar
blemoigne
Messages: 178
Registration: July 17, 2020 - 11:29

February 21, 2023 - 9:40 AM

Hello,
no it's the opposite, you need to keep your configuration and therefore leave it unchecked.
User avatar
fcomte
Messages: 18
Registration: February 1, 2023 - 11:15

February 21, 2023 - 10:37

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.
- Installed WAPT version: 2.4.0.14080 Discovery
- Server OS: Debian GNU/Linux 11 (bullseye)
- Administration/package creation machine OS: Windows 10
User avatar
dcardon
WAPT Expert
Messages: 1932
Registration: June 18, 2014 - 09:58
Location: Saint Sébastien sur Loire
Contact :

February 24, 2023 - 2:40 PM

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
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
Locked