Hello,
I built a package from an executable .exe and when I want to import the package in the private deposit, this error occurs:
- HTTPError: 502 Server Error: Bad Gateway.
This error happens from CLI or GUI.
The package size is 2.3 GB.
My OS: Windows Server 2012 R2.
Maybe the connection to the server closes because the transfer is too long. Anyone how to set this?
Import a big package into private repo.
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
-
Frédéric Bonnier
- Messages: 24
- Registration: June 23, 2014 - 10:10
- Location: Nantes
- Contact :
Hello,
The current method for uploading a package from the console has a timeout that is too short for large packages or slow networks. This is one of the things that will be changed in future versions.
For now, if you have a WAPT server on Windows:
copy your new package to the directory C:\WAPT\waptserver\repository\wapt and run the command:
#wapt-get update-packages C:\WAPT\waptserver\repository\wapt
If you have a WAPT server on Linux:
copy your package to /var/www/wapt on your WAPT server using WinSCP.
Then run the command on the WAPT server:
#python /opt/wapt/wapt-scanpackages.py /var/www/wapt
Frédéric
The current method for uploading a package from the console has a timeout that is too short for large packages or slow networks. This is one of the things that will be changed in future versions.
For now, if you have a WAPT server on Windows:
copy your new package to the directory C:\WAPT\waptserver\repository\wapt and run the command:
#wapt-get update-packages C:\WAPT\waptserver\repository\wapt
If you have a WAPT server on Linux:
copy your package to /var/www/wapt on your WAPT server using WinSCP.
Then run the command on the WAPT server:
#python /opt/wapt/wapt-scanpackages.py /var/www/wapt
Frédéric
Frédéric Bonnier - Tranquil IT Systems.
Display yourself on the WAPT user map by completing the questionnaire.
Discover our service offerings at Tranquil IT Systems and join us on Twitter.
Display yourself on the WAPT user map by completing the questionnaire.
Discover our service offerings at Tranquil IT Systems and join us on Twitter.
Apparently, the same error exists in version 1.5.
I just tested your commands and it works.
I get a message:
Processed packages: SolidWorks.wapt etc...
It was added correctly to my repository; all that's left is to test the deployment.
However, with version 1.5, is there now a variable to modify this timeout?
Here is the console log:
Uploading c:\waptdev\iut-solidworks_22.2.0.40-1_all.wapt: 7058648134 / 7058648134
Done Uploading c:\waptdev\iut-solidworks_22.2.0.40-1_all.wapt
FATAL ERROR: HTTPError: 504 Server Error: Gateway Time-out for url: https://wapt.iut.lan/api/v3/upload_packages
Exit code: 3
(I should mention that I previously had to modify the nginx.conf file by changing client_max_body_size to 10GB
from client_max_body_size to 10000m; to get the gateway timeout error.)
Regards
I just tested your commands and it works.
I get a message:
Processed packages: SolidWorks.wapt etc...
It was added correctly to my repository; all that's left is to test the deployment.
However, with version 1.5, is there now a variable to modify this timeout?
Here is the console log:
Uploading c:\waptdev\iut-solidworks_22.2.0.40-1_all.wapt: 7058648134 / 7058648134
Done Uploading c:\waptdev\iut-solidworks_22.2.0.40-1_all.wapt
FATAL ERROR: HTTPError: 504 Server Error: Gateway Time-out for url: https://wapt.iut.lan/api/v3/upload_packages
Exit code: 3
(I should mention that I previously had to modify the nginx.conf file by changing client_max_body_size to 10GB
from client_max_body_size to 10000m; to get the gateway timeout error.)
Regards
