Tranquil IT Forum

Hello,


I've tried quite a few things since this morning, but there's still no noticeable improvement. I suspect I have a certificate problem.

Here's what's been done to move the old server from our production VLAN to the new one in the DMZ:
- Updated Debian 10 to Debian 11
- Updated WAPT 1.8 to 2.2
- Installed Debian 11 on the new server
- Installed WAPT 2.2 on the new server
- Migrated data according to the documentation: https://www.wapt.fr/fr/doc/wapt-server-backup.html
- Upgraded the console; everything is working correctly
- Updated the agent
- Resigning packages via the console failed; I tried using the command line: https://www.wapt.fr/fr/doc/wapt-command ... ackage-cmd

Since then, the machines have lost the list of installed packages, and I still can't sign the packages. I have an error message visible in both screenshots.
On an administration machine where the console hasn't been updated to WAPT 2.2, I still have access to the packages.

I'm stumped... I still have my certificates and passwords from 2019/2020; it's as if they're not being recognized correctly.
Unless the certificates and waptserver.ini file from the old server, placed on the new server in the /opt/wapt/conf folder, are causing the problem?

It's beyond me :-/

When re-signing through the console, we check that the old package is correctly signed in its previous version, to avoid a man-in-the-middle attack.

Apparently the old certificate from the 7zip package is not recognized on the machine: the certificate (present in the WAPT folder of the package) is indeed present in "C:\Program Files (x86)\wapt\ssl" on the machine?

jlatieule wrote: ↑August 30, 2022 - 5:22 PM Since then, the machine packages have lost the list of installed packages

It's strange; it might be an inventory retrieval issue if the agent isn't up to date, but the packages shouldn't just disappear on their own like that

Thanks Simon,


I think there are two problems to fix simultaneously.

The agent isn't deployed yet, so I think the lack of station updates will resolve itself.

Regarding the certificates, the private and public keys are in c:/private.
Back at work, I'll check the contents of the package and the SSL folder. The public key is probably missing somewhere.

Hi Simon,


That was it. The public key wasn't in "C:\Program Files (x86)\wapt\ssl".
I rebuilt the agent with it and it worked perfectly.

There are still some packages where I'm getting Python errors, probably due to the version upgrade. I still have a few package modifications to make and then it will be migrated correctly.