Hello,
while testing WAPT in a lab environment, I tried deploying Firefox on a Windows 10 workstation.
The workstation appears correctly in the inventory, no problem there, but after retrieving the Firefox package from the internet and adding it to the machine, I get the following error message:
Error building or uploading package ==> error on server: Ewaptforbidden (host matching package does not trust signer certificate...).
Can you help me?
Many thanks,
El Chapulin.
packet deployment error
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 :
Hi Anthony,
there must be a certificate issue. The package needs to be signed with a different certificate than the one installed on the machine.
Does your certificate appear correctly in the "Certificate" tab on the machine?
Is it the same as the one in your console?
there must be a certificate issue. The package needs to be signed with a different certificate than the one installed on the machine.
Does your certificate appear correctly in the "Certificate" tab on the machine?
Is it the same as the one in your console?
-
elchapulin
- Messages: 11
- Registration: June 9, 2023 - 2:47 PM
Hello,
thank you for the feedback.
Yes, the certificate does appear in the client's certificates tab and it's the same one as on my machine...
thank you for the feedback.
Yes, the certificate does appear in the client's certificates tab and it's the same one as on my machine...
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
Same expiry date on the certificate?
-
elchapulin
- Messages: 11
- Registration: June 9, 2023 - 2:47 PM
Okay, it's working perfectly on a test VM today...
No explanation needed, I'll continue testing!
Thanks!
No explanation needed, I'll continue testing!
Thanks!
-
elchapulin
- Messages: 11
- Registration: June 9, 2023 - 2:47 PM
Okay, so there must be a certificate issue because it only works on the VM (which was created during the first testing phase).
What's the procedure for deploying the correct certificate to the client machines, given that I've recreated a certificate on the server?
Thank you very much for your help.
El Chapulin
What's the procedure for deploying the correct certificate to the client machines, given that I've recreated a certificate on the server?
Thank you very much for your help.
El Chapulin
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
The procedure is as follows.
The certificate you use in the console must be present in the C:\Program Files (x86)\wapt\ssl folder of the machines you control.
Also delete all wapt packages signed with a different key
Also delete from your computer any certificates you are not using located in C:\Program Files (x86)\wapt\ssl
The certificate you use in the console must be present in the C:\Program Files (x86)\wapt\ssl folder of the machines you control.
Also delete all wapt packages signed with a different key
Also delete from your computer any certificates you are not using located in C:\Program Files (x86)\wapt\ssl
The error is here, then. There's no need to recreate the certificate in your case
