Hello,
I'm getting a small error message on my central console. I think it's just latency (I'm pretty sure it is). When I run an update on my computer, for example (generally those connected via Wi-Fi), the update starts but displays a timeout on the console.
The full error message is:
HTTPConnectionPool(host='XXXX', port=8088): Read timed out. (read timeout=5)
Is it possible to increase the threshold somewhere?
Thanks in advance.
HTTPConnectionPool read timed out
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
Hello,
I'm having the same problem, even when updating the client installed on the WAPT server.
My server and clients are all running Windows 10 64-bit.
With this error, I can't see the tasks in progress when I launch a package and installation update from the WAPT console.
I've checked port 8088 of the server on localhost and its IP address; it responds correctly to telnet, so I don't have a firewall or other blocking issue.
Thanks,
David
I'm having the same problem, even when updating the client installed on the WAPT server.
My server and clients are all running Windows 10 64-bit.
With this error, I can't see the tasks in progress when I launch a package and installation update from the WAPT console.
I've checked port 8088 of the server on localhost and its IP address; it responds correctly to telnet, so I don't have a firewall or other blocking issue.
Thanks,
David
-
Daniel Traversa
- Messages: 16
- Registration: February 21, 2017 - 2:26 PM
Exactly the same problem.
The server and clients are on different VLANs, that's probably the cause.
Can this delay be configured?
The server and clients are on different VLANs, that's probably the cause.
Can this delay be configured?
-
Daniel Traversa
- Messages: 16
- Registration: February 21, 2017 - 2:26 PM
Is there a solution to this problem?
Thank you.
Thank you.
-
Daniel Traversa
- Messages: 16
- Registration: February 21, 2017 - 2:26 PM
I reinstalled on a Windows server and I don't have the problem...
I completely reinstalled on a new server with Debian 8 and I have the problem again.
On Windows 7 and Windows 10 clients.
I completely reinstalled on a new server with Debian 8 and I have the problem again.
On Windows 7 and Windows 10 clients.
