Hello,

WAPT version 2.5.5.15591 Enterprise edition.
The server is running Debian 12, while the client machines are running Windows 10 Pro and 11.

Recently, during package installation (this problem occurs with several packages), I'm getting the following error:

Traceback (most recent call last ...

Hello,

After analysis, here's what we observed:
The WAPT agent was deployed via GPO, with the `--force` option added to the WAPT deploy options.
This option was forcing a restart when the PC couldn't contact Active Directory.
After removing the option, the restarts stopped, and the problem persists...

Hello Simon,

In our tests, we also tried with the WAPT agent installed, but without any packages.
The PC still restarted.

Regards,

Hello,

I'm starting this thread because we're facing a problem that, for the moment, seems inexplicable.
We have a WAPT server running version 2.5.5.15591, and the agents are the same version.

When the machines lose contact with the domain (for example, when working remotely without a VPN), they restart...

Hello,

Finally, after investigation, the problem stemmed from the Reverse Proxy. The documentation specified that the agents no longer supported TLS Reverse Proxy and that simple SNI streams were required; however, this impacted not only the agents but also...

Hello,

The password has been changed via the postconf script, but unfortunately, the problem remains the same :/.

Regards,

Hello,

WAPT Server version: 2.5.5.15556
WAPT Agent version: 2.3.0.13516
WAPT Setup version: 2.5.5.15556
WAPT Deploy version: 2.5.5.15556
Database status: OK

Following an update from version 2.3 to version 2.5, I can no longer connect to the WAPT console.
It has been updated to...