Error re-signing my private repository packages after WAPT update

Questions about WAPT Packaging / Requests and help regarding Wapt packages.
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
laurentb
Messages: 1
Registration: June 14, 2022 - 8:32 PM

June 15, 2022 - 1:01 PM

Hello,

I attempted to update WAPT Community from version 1.8.2 to the latest version, 2.2 Discovery.

Everything seemed to go smoothly, and following the update steps in the documentation, I tried to re-sign the packages in my repository.

However, I'm getting an error: "EWaptBadSignature: check_package_signature failed".

The signing of my machine packages worked just before.

I also verified with WAPT that my private key and associated password are valid.

Since I'm using a virtual machine, and after several hours of searching for a solution, I restored my WAPT server to avoid disrupting the updates across my network. :(

My WAPT server is running Windows 10 Pro.

Do you have any idea what the problem might be?

Many thanks in advance.
High
User avatar
CasseThor
Messages: 22
Registration: December 1, 2017 - 9:25 PM

June 22, 2022 - 09:02

Hello,
I have the same problem.
Attachments
Capture.JPG
Capture.JPG (22.78 KB) Viewed 2329 times
High
Locked

Return to “WAPT Packages”


  • To go further with WAPT