Hello,
I'm having trouble uploading large packages to my WAPT 1.5.23 server on a Debian distribution. I keep getting the error "ConnectionError:(-1,'Unexpected EOF')". I imagine this is due to a restriction on package size or the number of files?
Thanks in advance.
[RESOLVED] Restriction on package size or number of files
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
- dcardon
- WAPT Expert
- Messages: 1932
- Registration: June 18, 2014 - 09:58
- Location: Saint Sébastien sur Loire
- Contact :
Hello imp83,
There have been memory issues during uploads in the past, but this should be resolved in version 1.5.1.23. How much RAM do you have on the server and the client machine? Could you specify the amount of RAM that is causing the problem, i.e., at what point you encounter an issue?.
At first glance, the first thing I would look at would be the antivirus, firewalls with DPI or proxies that think they are too smart.
Sincerely,
Denis
There are no particular restrictions. We have clients with packages larger than 15GB. When you mention restrictions on the number of files, are you referring to packages with a few hundred files, or tens of thousands? Could you publish your problematic package?
There have been memory issues during uploads in the past, but this should be resolved in version 1.5.1.23. How much RAM do you have on the server and the client machine? Could you specify the amount of RAM that is causing the problem, i.e., at what point you encounter an issue?.
At first glance, the first thing I would look at would be the antivirus, firewalls with DPI or proxies that think they are too smart.
Sincerely,
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
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
It's quite strange because when I try to edit the previous version of the package without making any changes and then upload it, I get an error:
HTTPError 413 Client Error: Request Entity Too Large for url: https://server/api/v3/upload_packages
On both the server and client sides, I have 4GB of RAM.
HTTPError 413 Client Error: Request Entity Too Large for url: https://server/api/v3/upload_packages
On both the server and client sides, I have 4GB of RAM.
- dcardon
- WAPT Expert
- Messages: 1932
- Registration: June 18, 2014 - 09:58
- Location: Saint Sébastien sur Loire
- Contact :
Good morning,
Upon closer inspection, the WAPT server itself doesn't limit it, but there is a security measure at the Nginx level. If you want to upload larger packages, you need to modify the `client_max_body_size` parameter in the `/etc/nginx/sites-enabled/wapt.conf` file.
Sincerely,
Denis
I asked in my email what the problematic packet size was... Could it possibly be 4GB? Thank you.Imp83 wrote: ↑Apr 20, 2018 - 11:27 It's quite strange because when I try to edit the previous version of the package without making any changes and then upload it, I get an error:
HTTPError 413 Client Error: Request Entity Too Large for url: https://server/api/v3/upload_packages
On the server and client side, I have 4GB of RAM.
Upon closer inspection, the WAPT server itself doesn't limit it, but there is a security measure at the Nginx level. If you want to upload larger packages, you need to modify the `client_max_body_size` parameter in the `/etc/nginx/sites-enabled/wapt.conf` file.
Sincerely,
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
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
