Hello,
Adobe has changed its licensing policy for Creative Cloud, so
I'm forced to uninstall the licensed CC 2018 apps and replace them with a 16GB setup using an anonymous license.
I've modified nginx to accept files larger than 4GB.
The package build and signature are correct. The upload completes but fails at the very end with the following error message:
Done uploading: xxxxx.wapt
FATAL ERROR: HTTError: 504 Server error: Gateway Time-out for url: https://mywaptserver.domain.lan/api/ ... d_packages.
On the server, the load average was over 2, so I think it was overloaded. Is there any way to extend the time required to complete the package upload on the server? (Obviously, a hardware upgrade is out of the question, as I have no budget for it.)
Thank you.
gateway timeout
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
The HTTP upload method is not really optimized for very large packets like this one... improvements should be considered on our end.
One possibility is to
- Build/sign the package without uploading it using the command (in cmd on your development machine):
Then upload the package (.wapt) via SSH using WinSCP3, for example, to the server's /var/www/wapt directory
then reindex the packages (update in the repository the index file "Packages") with the command (via ssh root on the Wapt server)
One possibility is to
- Build/sign the package without uploading it using the command (in cmd on your development machine):
Code: Select all
wapt-get -i build-package c:\waptdev\<monpaquet-wapt>then reindex the packages (update in the repository the index file "Packages") with the command (via ssh root on the Wapt server)
Code: Select all
wapt-scanpackages /var/www/wapt/ -linfo
Tranquil IT
Hello,
thank you very much for the quick reply. Indeed, it works well for uploads.
However, I made the mistake of trying to deploy the package to all 31 PCs in a room (I was pressed for time, as classes were being held this morning using the CC suite). It was a disaster; only 2 or 3 completed the download and installed the package successfully. The others encountered connection errors with the server (probably due to network congestion). I had to urgently perform the installations manually.
But I will test it tomorrow in another room with only 2 or 3 computers at a time. I will report the final result.
thank you very much for the quick reply. Indeed, it works well for uploads.
However, I made the mistake of trying to deploy the package to all 31 PCs in a room (I was pressed for time, as classes were being held this morning using the CC suite). It was a disaster; only 2 or 3 completed the download and installed the package successfully. The others encountered connection errors with the server (probably due to network congestion). I had to urgently perform the installations manually.
But I will test it tomorrow in another room with only 2 or 3 computers at a time. I will report the final result.
