WAPT Server behind a reverse proxy

Questions about WAPT Server / Requests and help related to the WAPT server
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
Locked
User avatar
Franck_V
Messages: 1
Registration: August 30, 2018 - 5:27 PM

August 30, 2018 - 5:42 PM

Good morning,

We want our WAPT server to be reachable via our reverse proxy (Cluster of 3 Vulture nodes).
The agent's requests reach the server successfully, but they time out.

In the agent's debug logs we have:

Code: Select all

2018-08-30 17:17:36,184 DEBUG Resetting dropped connection: waptserver.mydomain.lan
In the NGINX logs:

Code: Select all

2018/08/30 16:55:08 [error] 731#731: *607395 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 10.0.0.1, server: _, request: "GET /socket.io/?login=%....
10.0.0.1 being the IP address of one of the three nodes of our reverse proxy

I tried sending an X-Forwarded-For header to NGINX, and I can see the client's IP address reaching the waptserver:

Code: Select all

User-Agent: python-requests/2.19.1
content-type: application/octet-stream
Cookie: io=759e37fd455e4d669d6a5f124733b5cd
X-Forwarded-For: 10.0.3.12
10.0.3.12 being the client workstation.

Do you have any idea?
High
cdeze
Messages: 31
Registration: Nov 29, 2016 - 09:39

September 4, 2018 - 4:07 PM

Have you tried this kind of configuration:
https://chrislea.com/2013/02/23/proxyin ... ith-nginx/
High
Locked

Return to "WAPT Server"


  • To go further with WAPT