WAPT Server behind a reverse proxy
Published: 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:
In the NGINX logs:
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:
10.0.3.12 being the client workstation.
Do you have any idea?
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.lanCode: 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=%....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.12Do you have any idea?