New installation: Server access error: HTTP/1.1 504 Gateway Time-Out

Questions about WAPT Server / Requests and help related to the WAPT server
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
Locked
Cantrel
Messages: 14
Registration: Sep 29, 2020 - 1:49 p.m.

September 29, 2020 - 1:57 PM

Hello,

We would like to test WAPT as we are looking for software to manage our IT infrastructure and Microsoft updates.
We received the installation instructions and a key from Ms. Badier.

This afternoon, I started installing a dedicated Hyper-V VM running Windows Server 2019 Standard for testing purposes.
On the Windows machine, I simply assigned a static IP address and joined the domain. I disabled the firewall for testing.

The WAPT installation appears to proceed correctly, with no error messages. However, upon launching the console, we receive the following message:
Server access error: HTTP/1.1 504 Gateway Time-Out.

We attempted to restart the services, but the problem persists.
I should mention that the installation was done using the default settings in the C drive, etc.

Could you please assist us?

Thank you.
Last edited by Cantrel on 30 Sep 2020 - 10:31, edited 1 time.
Cantrel
Messages: 14
Registration: Sep 29, 2020 - 1:49 p.m.

September 29, 2020 - 2:05 PM

Based on what I found on your forum, I'm missing the WAPTServer service.

I just ran this:
`c:\wapt\waptpython.exe c:\wapt\waptserver\winsetup.py -ldebug install_waptserver -cc:\wapt\conf\waptserver.ini`

as suggested in another post. We'll see.
Cantrel
Messages: 14
Registration: Sep 29, 2020 - 1:49 p.m.

September 29, 2020 - 2:08 PM

No better, I only have two services visible:
WAPTNginx
and WAPTService.

Awaiting your help,

thank you.
User avatar
dcardon
WAPT Expert
Messages: 1932
Registration: June 18, 2014 - 09:58
Location: Saint Sébastien sur Loire
Contact :

September 30, 2020 - 10:04 AM

Hello Cantrel,
did you perform the installation using the local administrator account or a domain account with local admin rights? There's a bug that can occur during the application of access control lists (ACLs) with iCACLs when a local account isn't used (just for the initial installation).
You can reinstall using the local admin account on the existing installation.
Regards,
Denis
Denis Cardon - Tranquil IT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
Cantrel
Messages: 14
Registration: Sep 29, 2020 - 1:49 p.m.

September 30, 2020 - 10:27

Hello,

Yes, I reinstalled it yesterday before joining the domain, using the local admin account and the server in a workgroup.
No problems with the installation.

Joining the server back to the domain afterwards was OK.

Thank you for your help.
Locked