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
[SOLVED] 408 client error waptexit
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: 1929
- Registration: June 18, 2014 - 09:58
- Location: Saint Sébastien sur Loire
- Contact :
This smells like a bug. We'll look into it internally.
Regards,
Denis
Regards,
Denis
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
-
Breton olive tree
- Messages: 3
- Registration: July 8, 2022 - 11:09
I have the same issue.
Wapt version: 2.2;
Wapt version: Discovery
; Server OS: Linux Debian 10
; Administration machine OS: Windows 10
Wapt version: 2.2;
Wapt version: Discovery
; Server OS: Linux Debian 10
; Administration machine OS: Windows 10
-
dcardon
- WAPT Expert
- Messages: 1929
- Registration: June 18, 2014 - 09:58
- Location: Saint Sébastien sur Loire
- Contact :
This should be fixed in the next version, 2.2.2.
Denis
Denis
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
-
Breton olive tree
- Messages: 3
- Registration: July 8, 2022 - 11:09
You have a release date for version 2.2.2
-
dcardon
- WAPT Expert
- Messages: 1929
- Registration: June 18, 2014 - 09:58
- Location: Saint Sébastien sur Loire
- Contact :
within two weeks max.
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
-
dcardon
- WAPT Expert
- Messages: 1929
- Registration: June 18, 2014 - 09:58
- Location: Saint Sébastien sur Loire
- Contact :
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
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
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
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.
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
