Page 1 of 1
[SOLVED] 408 client error waptexit
Published: June 30, 2022 - 12:18
by plubz
Hello,
I've noticed that when my client machine is connected to a different network that doesn't have access to the server, WaptExit displays an error when shutting down the machine:
408 client error: for url:
http://127.0.0.1:8088/is_entreprise.
To shut down the machine, the end user is forced to click the OK button, which is quite inconvenient.
Do you know how to resolve this error?
Thank you for your help.
Wapt version: 2.2;
Wapt version: Discovery
; Server OS: Linux Debian 11
; Administration machine OS: Windows 10
Re: 408 client error waptexit
Published: June 30, 2022 - 3:22 PM
by dcardon
This smells like a bug. We'll look into it internally.
Regards,
Denis
Re: [SOLVED] 408 client error waptexit
Published: July 8, 2022 - 11:11
by Olivier Breton
I have the same issue.
Wapt version: 2.2;
Wapt version: Discovery
; Server OS: Linux Debian 10
; Administration machine OS: Windows 10
Re: [SOLVED] 408 client error waptexit
Published: July 8, 2022 - 7:43 PM
by dcardon
This should be fixed in the next version, 2.2.2.
Denis
Re: [SOLVED] 408 client error waptexit
Published: July 11, 2022 - 08:23
by Olivier Breton
You have a release date for version 2.2.2
Re: [SOLVED] 408 client error waptexit
Published: July 11, 2022 - 09:53
by dcardon
within two weeks max.
Re: [SOLVED] 408 client error waptexit
Published: July 11, 2022 - 11:38 AM
by Olivier Breton
OK thanks
Re: [SOLVED] 408 client error waptexit
Published: July 12, 2022 - 5:28 PM
by dcardon
Hi Olivier,
the WAPT-2.2.2-rc1 release candidate has just been released. Could you test it on a machine experiencing the problem to see if it resolves the issue for you? Simply install waptsetup.exe on the affected machine (no need to update everything).
Regards,
Denis
Re: [SOLVED] 408 client error waptexit
Published: September 13, 2022 - 11:34 AM
by sesaidi
Good morning,
I'm bumping this post because I'm experiencing the same issue after an update from 1.8.2 to 2.2.2.
No issues on the majority of workstations; only a handful report this error when working remotely:
https://ibb.co/jZMWd9G
- I tried to reinstall the agent.
- Verify that the wapt service was started (localhost:8088 correctly returns the client information).
- In
C:\Program Files (x86)\wapt\log\waptservice.log nothing different from the logs of a machine that does not encounter the problem.
What could cause this error?
Thank you in advance for your help.
WAPT Server version: 2.2.2
WAPT Agent version: 2.2.2.12388
WAPT Setup version: 2.2.2.12388
WAPT Deploy version: 2.2.2.12388