Hello, I'm writing to explain the problem I'm having. After restarting the WAPT server, I'm getting a 502 Nginx Bad Gateway error
when I try to start the waptserver.service. I receive a "failed with result 'exit-code'".
This is the second time I've encountered this problem, and the first time I had to perform a complete reinstall. I should mention that no changes were made to the server configuration, and the restart was performed because I couldn't connect to the administration console. The same "bad gateway" error occurred. If anyone has any suggestions, I'd be very grateful, because after reviewing all the logs in var/log, I'm completely stuck on the source of the problem.
Thank you in advance for any replies.
- WAPT version installed: WAPT-1.6.2.8
- Server OS: Debian 9.6
- Administration/package creation machine OS: Windows 10
[SOLVED] waptserver.service: Failed with result 'exit-code'.
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
Could you please specify the error message received when launching waptserver.service?
If necessary, run the command:
If necessary, run the command:
Code: Select all
journalctl -xeSo I just found the problem. I regained access; it was a socket from another machine communicating on the same DNS server. As a result, I was getting ARP attack alerts on ESET. I hadn't made the connection because the ARP attack address was that of my network gateway. Anyway, that problem is solved, thank you all the same. But I'm facing another type of issue since the reboot: many of my hosts are disconnecting even though the machines are being requested and the ESET trust zones are configured correctly
