Tranquil IT Forum

Good morning,

I have a problem following the update of a WAPT server from version 1.3.13 to version 1.7.4.
Everything is working fine: package deployment, adding new hosts, etc...Except for uploading or deleting packages


When uploading packages, I get the following error message:

HTTPError: 504 Server Error: Gateway Time-out for url: http://dist.montpellier.cemagref.fr/api ... d_packages

After the transfer, this message appears after about thirty seconds (during which the console is unresponsive) regardless of the upload method:
-via waptconsole to import a local package
-via waptconsole to import a package from the tranquil.it repository

-via the command prompt with wapt-get build-upload or upload-package The following message appears simultaneously in the nginx error.log file on the server:
[error] 1890#1890: *2186 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 172.16.10.78, server: dist.montpellier.cemagref.fr, request: "POST /api/v3/upload_packages HTTP/1.1", upstream: "http://127.0.0.1:8080/api/v3/upload_packages", host: "dist.montpellier.cemagref.fr"


The following window appears after deleting a package from waptconsole: and at the same time in the nginx error.log:
[error] 1892#1892: *2195 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 172.16.10.78, server: dist.montpellier.cemagref.fr, request: "POST /api/v3/packages_delete HTTP/1.0", upstream: "http://127.0.0.1:8080/api/v3/packages_delete", host: "dist.montpellier.cemagref.fr"



IMPORTANT INFORMATION: Despite the error messages, the packages are being uploaded or deleted correctly, so it's probably not a permissions issue. However, it's still very annoying because the console freezes for 30 seconds each time.

I should point out that the server runs on Debian Stretch (9.9) and the console runs on Windows 10.

Does nobody have any ideas?

Is there a permissions issue with the /var/www/wapt/?

No, I've checked, the permissions are fine, and the files are uploaded correctly anyway.

What I don't understand is why the transfer goes smoothly, but I get an error message after a 30-second freeze.

I don't know what the upload function tries to do after the transfer is complete...

He is attempting to create a scan-package

You can try:

Thanks for the order; indeed, there was a (large) package that was taking far too long to scan. I deleted it since I no longer need it.
Everything is working perfectly now! Thank you so much for your help!

Hello,
I have the same problem after installing Wapt 1.7.4.6165 on a Windows Server 2012.
To give you some background, I had a Wapt 1.5.21 system on another Windows Server 2012 that worked perfectly until it crashed. I had to rebuild another Server 2012 on different hardware, but with the new version of Wapt.
The installation goes smoothly until I try to connect using the console.
I get the error " Error on Wapt HTTP 1.1 Server
504 Gateway Timeout".


I should also mention that I tried reinstalling version 1.5.21 and I also had a connection problem with the Wapt console (same error). So, I might as well use the latest release.
Thank you in advance for your solutions, as I use it extensively to deploy applications in my lab.

Patrick