Tranquil IT Forum

Hello,

I'm currently experiencing a problem when my users connect remotely via our VPN.

When I try to install packages via the console, the following message appears: "The WAPT service is unreachable."

From the client, there are no problems.
The update installation works correctly when I run the action from the agent.

Additional information:
- Port 8088 is open on the PC, and package deployment works when I'm not connected to the VPN.
- The network information "IP addresses" on the WAPT console is updated correctly when the PC is connected to the VPN. However, the "Listening IP" field is empty.

Thank you in advance for your help.

Seb.

For remote updates to be triggered on clients from the console to work, the server must be able to "see" port 8088, which is open on one of the client's IP addresses, and the requests must reach the client with the server's original source IP address (without rewriting the source IP address).

When a client machine is connected via VPN, several problems can occur:
- the subnet it's on might be NATed, making its individual IP address invisible;
- firewall rules between the server's subnet and the VPN subnet might block requests
; - the server's IP address might itself be masked (SNAT), causing clients to reject requests.

The "Listening IP" field is updated by the server after each time the client sends its status. The server tests immediately after the status update (the inventory sent by the client contains the IPs of the network interfaces and the listening ports of the wapt service (8088 by default) as well as the http/https protocol(s))