Tranquil IT Forum

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

Could you please specify the error message received when launching waptserver.service?

If necessary, run the command:

So 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