Hello,
I'm trying to modify a package group on another PC which contains waptsetup.exe and has the same private key as my WAPT server, but I'm getting an error: [error message here].
Do you know what causes it?
Signature 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 :
Based on the error message, it seems the package isn't signed with a recognized key or is incorrectly signed.
I didn't quite understand everything, but:
You mentioned waptsetup.exe on another machine. I think I understand that you installed waptsetup.exe on another machine to access the console (waptagent is sufficient; all machines have the console).
Try reinstalling waptagent.exe instead. It contains the keys you need to verify the package.
Be careful not to create multiple keys, as you risk confusion; reuse your existing keys.
I didn't quite understand everything, but:
You mentioned waptsetup.exe on another machine. I think I understand that you installed waptsetup.exe on another machine to access the console (waptagent is sufficient; all machines have the console).
Try reinstalling waptagent.exe instead. It contains the keys you need to verify the package.
Be careful not to create multiple keys, as you risk confusion; reuse your existing keys.
sfonteneau wrote: ↑May 4, 2022 - 2:33 PM Based on the error message, it seems the package is either not signed with a recognized key or is incorrectly signed.
I didn't quite understand everything, but:
You mentioned waptsetup.exe on another machine. I think I understand that you installed waptsetup.exe on another machine to access the console (waptagent is sufficient; all machines have the console).
Try reinstalling waptagent.exe instead. It contains the keys you need to verify the package.
Be careful not to create multiple keys, as you risk confusion; reuse your existing keys.
I used the console via waptagent.exe, but the same error occurs whenever I try to remove a package from a package group. I think I've missed a step; do I need to do something on the server so it recognizes the administrator's machine key?
Installed WAPT version = 2.2.1
Server OS = Windows Server 2019
Administration/package creation machine OS = Windows 10
Server OS = Windows Server 2019
Administration/package creation machine OS = Windows 10
Hello Martiny,
In the SSL folder on my machine that I want to make an administrator account, I only have the certificate for my server machine's key
Installed WAPT version = 2.2.1
Server OS = Windows Server 2019
Administration/package creation machine OS = Windows 10
Server OS = Windows Server 2019
Administration/package creation machine OS = Windows 10
