Tranquil IT Forum

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?

Hello

, have you tried one of the solutions listed in the documentation:
https://www.wapt.fr/fr/doc/Frequent-pro ... la-console?

Simon

I just checked the instructions and everything seems fine.

Even "Scan listening IPs" doesn't return any results.

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.

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

Indeed, everything seems to be working again. Thank you.

It's very interesting to know about future versions; it's good to see you continually improving the solution.

In the main repository, I no longer see the waptupgrade package, which updated the agent itself.

I'm wondering if this is a bug, if the package exists but isn't visible, or if it's abnormal.

If I understand correctly, as long as I don't recreate a custom agent, the waptupgrade package won't exist, since we don't need it?

Exactly.

WaptUpgrade will be useful to you the day you want to update Wapt.