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.
Client "unreachable" over VPN
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
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))
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))
Tranquil IT
