Hello,
I have the same problem on my control station. My latest changes:
- installed the waptupgrade package
- created an agent with the WUA option.
Since then, my computer displays error 408 when I restart/quit...
For your information, I reinstalled my console, but nothing changed...

Hello,

yes, it seems the FQDN is missing from my certificate because I'm using a wildcard certificate. I read the post from January 27, 2022, and it's the same error.
Since I have to use my wildcard, I'll deploy the agent via the IP address in my GPO... and it works...

We're making a little progress...
if I change my waptdeploy call to:
waptdeploy.exe --hash=02dfba835e17c928933a9bf929200cd50475fc8658322e1f4484b563bfe0738a --minversion=2.2.3.12465 --wait=15 --waptsetupurl=https://wapt.monsite.fr/wapt/waptagent.exe
I get the previous error (TLS failed)
if...

Apparently so...
I had set up the GPO and tested it on a machine, and it worked... when I installed the certificate (valid for our site), the GPO stopped running, so I tried to run the command manually, encountering the errors from the previous post. Going back to the old method...

Hello,
when I configure the server with an external certificate in Nginx and reload it (reload Nginx), the web page appears correctly with HTTPS,
so I was happy.
Now I get an error when I try to deploy using waptdeploy.exe and the hash and the waptagent... there's an error...

Thanks, it works!
and here is my code for the route:

# -*- coding: utf-8 -*-
from setuphelpers import *

def install():
# Declaring local variables

# Installing the software
print("Installing: Brave_installer-x64.exe")
install_exe_if_needed('brave_installer-x64.exe',
silentflags='--install ...

Hello,

I'm trying to uninstall the "Brave" package (created using Package Template), but unfortunately it requires an action, and I haven't found a silent option... Do you have any ideas?

Many thanks in advance,
Samuel

Hello,

just a quick update on my migration experience:

first observation, when everything works, it's fantastic! Much faster and much clearer.

However, I did encounter some issues during my migration because I changed the server name and also the domain name... so I had...

Yes, it was a key error (thanks for the advanced mode tip).
I had to recreate my key and re-sign my packages because in the meantime my server changed domain and name... plus migrated from wapt 1.3 to 1.5...
thanks

Okay,
I'm in debug mode and yes, it's definitely a key problem: My question is... should I look at it from the client side or the server side?

THANKS.