Tranquil IT Forum

Information:
Linux server version: Debian GNU/Linux 11 (bullseye)
WAPT Agent version: 2.4.0.14080

Hello,

We are having a problem after creating our WAPT server and then implementing the packages. We created the units containing the required packages. Unfortunately, for some time now, it seems that all the units are no longer working, nor are the commands from the WAPT console.

Here is a screenshot of my unit in version 27:


And one of the computers in my network that still has unit version 26:


Despite attempting audits from the WAPT console and even after trying manually from the workstations (using the command "wapt-get update/upgrade"), version 27 is not downloading at all on approximately 50 computers in the network. Approximately 20% of them have no packages and no packages ready to be installed, while the others either have the "units" package with an error in version 26, or it's OK but still in version 26.

Thank you in advance.

Some suggestions:

• I see that the package has undergone modifications (x64) (Windows). There may be other capabilities preventing machines from seeing the package
• Are there any secondary repositories in your infrastructure? If so, are the secondary repositories up to date?
• In the WAPT inventory of the machines in question, is the computer_ad_dn entry correct, does it have the correct value?
• Is the admin key that signed the OU package present in the machine's certificate tab?

sfonteneau wrote: ↑Nov 8, 2023 - 2:06 PM Some suggestions:

• I see that the package has undergone modifications (x64) (Windows). There may be other capabilities preventing machines from seeing the package
• Are there any secondary repositories in your infrastructure? If so, are the secondary repositories up to date?
• In the WAPT inventory of the machines in question, is the computer_ad_dn entry correct, does it have the correct value?
• Is the admin key that signed the OU package present in the machine's certificate tab?

Good morning,

Sorry for the late reply. I tried several solutions, and the certificate issue turned out to be the right one. When I deployed my agent, I used my former colleague's certificate, and mine didn't exist. I assume that's why my attempts weren't working. So I recreated the agent with my certificate, and since then everything has been working perfectly.

Thank you again
Sincerely.

Perfect then, WAPT is working as expected. Thank you for your comment; the concept of a certificate is very important in WAPT and unfortunately often misunderstood.