Tranquil IT Forum

- Server version: Windows Server 2019 Standard integrated into a domain
- Fresh virtualized install on an ESXi server
- WAPT Community version v1.8.2.7334

Hello everyone,
I worked with WAPT two years ago using a client's setup, and it worked really well, but everything was managed internally, so I never really got to do everything from start to finish.

Today, wanting to push the testing further and see if it's possible to integrate it with other clients, I created a VM in my Home Lab and set up a clean 2019 Standard server for this purpose.

But here's the thing: I have the same problem as here: viewtopic.php?t=1698
Basically, when I go to the services after installation, WAPTServer is missing, so I ran the command line provided, but it didn't help.
After rebooting the server, the three WAPT services are running correctly (NGINX, Service, and Server).

But nothing works; I'm still getting a 504 Gateway Timeout error. I admit I don't understand what I did wrong, because the server is completely clean and nothing could be blocking it.

Even the HTTPS web page never loads. I've tried disabling the firewall, but that didn't help either, so I'm a bit stuck. If anyone has any ideas, I'd be very grateful...

Thanks!
DinDon

It's been almost a month since I posted the message, and not a single reply.

I know very well that everyone here is a volunteer, or nearly so, but has no one encountered my problem and solved it?

I'm not going to solve your problem, but since you have an ESXi, try installing WAPT on a Debian system instead; it shouldn't take very long.

There may be a server conflicting ports used by the Wapt services (on the server, nginx listens on port 443 and the waptserver service on port 8080 of the loopback)