Hello,
I'm new to using WAPT.
I just installed my WAPT Community server on CentOS 7.
I configured my console on my Windows 10 machine and generated my wpatagent.exe file for my client machines.
I successfully created my first 7-Zip deployment package by following the video on the page https://www.wapt.fr/fr/doc/wapt-create- ... index.html.
I managed to deploy my 7-Zip package on my administration machine (the one with the console)
, but I can't do it on my first test machine where I only installed wpatagent.exe.
When I add my 7-Zip package to deploy it on my test machine, the "Save and Apply" and "Save" buttons remain grayed out.
When I try to add a dependency via right-click, I get the message "The user certificate c:\private\privatekey.crt is not authorized on the selection."
While right-clicking and selecting "Add Dependency" works on my machine with the console, I get a window asking for my private key password...
What have I missed to make it work on my client machines?
Regards
[SOLVED] - First steps with wapt, I can't deploy my package
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
-
dcardon
- WAPT Expert
- Messages: 1932
- Registration: June 18, 2014 - 09:58
- Location: Saint Sébastien sur Loire
- Contact :
As the error message states, your private key does not match the certificate (or lack thereof) deployed on the client machine. You likely installed waptsetup.exe instead of generating an agent and deploying waptagent.exe.
Denis Cardon - Tranquil IT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
Hello Denis,
Thank you for your reply.
Indeed, the certificate was missing from the directory structure installed by the WaptAgent installer.
I manually copied the certificate to c:\program files x86\wapt\ssl.
I thought the certificate was automatically included in the installer when it was compiled on the server.
In the form, I had specified c:\private\privatekey.crt as the path to the certificate.
Perhaps I should have left the default path, c:\program files x86\wapt\ssl?
In any case, once the privatekey.crt file was pasted into c:\program files x86\wapt\ssl on the client machine, I can deploy my packages from the admin console.
Thank you for your reply.
Indeed, the certificate was missing from the directory structure installed by the WaptAgent installer.
I manually copied the certificate to c:\program files x86\wapt\ssl.
I thought the certificate was automatically included in the installer when it was compiled on the server.
In the form, I had specified c:\private\privatekey.crt as the path to the certificate.
Perhaps I should have left the default path, c:\program files x86\wapt\ssl?
In any case, once the privatekey.crt file was pasted into c:\program files x86\wapt\ssl on the client machine, I can deploy my packages from the admin console.
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
Since the latest version of WAPT, the WAPT console no longer starts automatically as administrator; it can now start as a regular user.
And as a regular user, the console cannot copy anything to wapt\ssl, which would explain why the certificate was not present on your machine.
The procedure should specify that the Waptagent should be installed on the machine that just generated it.
And as a regular user, the console cannot copy anything to wapt\ssl, which would explain why the certificate was not present on your machine.
The procedure should specify that the Waptagent should be installed on the machine that just generated it.
