Debian: 12
nginx: 1.24
Wapt server: 2.5.2.15207
Hello,
We just upgraded from Wapt 2.4 to 2.5.
The workstations reconnected correctly after the Wapt server upgrade, but they remain "reachable" even when powered off. This didn't happen in version 2.4 with the same server configuration.
Any ideas on how to resolve this issue?
Thank you for your help.
Best regards.
[RESOLVED] Devices marked as reachable in the console even though they are turned off
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 :
We think we've found the problem; have you enabled certificate authentication in the postconf?
Hello and thank you for your quick reply, Simon.
Using HTTPS authentication via postconf solves this problem, but it blocks my external workstations that use the reverse proxy.
My situation is complex; I use two domains for my WAPT server, one internal for my desktops and one external for my laptops, therefore requiring two different certificates (a self-signed WAPT certificate internally and a public certificate externally).
Switching the reverse proxy to a simple "mod-stream" disables the SSL delegation that allowed me to switch between certificates.
I'll start another thread if needed regarding the reverse proxy once I've analyzed everything. Kevin provided us with a configuration; thank you to him.
This specific issue is resolved; thanks again.
Using HTTPS authentication via postconf solves this problem, but it blocks my external workstations that use the reverse proxy.
My situation is complex; I use two domains for my WAPT server, one internal for my desktops and one external for my laptops, therefore requiring two different certificates (a self-signed WAPT certificate internally and a public certificate externally).
Switching the reverse proxy to a simple "mod-stream" disables the SSL delegation that allowed me to switch between certificates.
I'll start another thread if needed regarding the reverse proxy once I've analyzed everything. Kevin provided us with a configuration; thank you to him.
This specific issue is resolved; thanks again.
