Hello,
we installed the WAPT server on a Windows machine and started deploying agents, both manually and via Group Policy.
In the administration console, we see our workstations contacting the server, but they are all showing as "Unreachable".
Having previously installed an older version in a test environment, I don't recall encountering this problem or needing to manually open a port, etc. (I've checked these settings on both the server and clients, and I don't think the issue lies there).
I should mention that localhost:8088 is working, and I can connect to the server from the workstations using the command line.
WAPT version: 1.3.12.15.
PS: I no longer see the waptupdate (or waptupgrade, I can't remember) package in the main repository. Is this normal?
Unreachable Positions
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
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
Hello
, have you tried one of the solutions listed in the documentation:
https://www.wapt.fr/fr/doc/Frequent-pro ... la-console?
Simon
, have you tried one of the solutions listed in the documentation:
https://www.wapt.fr/fr/doc/Frequent-pro ... la-console?
Simon
Hello,
after double-checking, it's the Windows firewall rule that hasn't updated: it's still using the old IP address of the previous server.
So I'm going to write a small script to remove the rules on our machines.
It's a shame that uninstalling the agent doesn't also remove this rule, but oh well, now we know, we can manage it.
after double-checking, it's the Windows firewall rule that hasn't updated: it's still using the old IP address of the previous server.
So I'm going to write a small script to remove the rules on our machines.
It's a shame that uninstalling the agent doesn't also remove this rule, but oh well, now we know, we can manage it.
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
Actually, when the service starts, the rule isn't recreated if it already exists:
https://github.com/tranquilit/WAPT/blob ... ce.py#L452
Indeed, the IP address might not be correct if you tested a WAPT server on the same machine with a different IP address.
If you delete the rule and restart the WAPT service, you shouldn't have any more problems.
For your information, the next version won't have this kind of issue because we're using the WebSocket system.
Simon
https://github.com/tranquilit/WAPT/blob ... ce.py#L452
Indeed, the IP address might not be correct if you tested a WAPT server on the same machine with a different IP address.
If you delete the rule and restart the WAPT service, you shouldn't have any more problems.
For your information, the next version won't have this kind of issue because we're using the WebSocket system.
Simon
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
Exactly.
WaptUpgrade will be useful to you the day you want to update Wapt.
WaptUpgrade will be useful to you the day you want to update Wapt.
