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 :-/
Migration 1.8 -> 2.2: certificate signing problem
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
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
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?
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?
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.
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.
System and Network Administrator at Domitia Habitat
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.
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.
System and Network Administrator at Domitia Habitat
