[Bug]: A-force -> Not being able to upload file using binary format and multi part form data about appsmith HOT 8 OPEN

Do we have an update on this issue? Been a while since last activity

from appsmith.

Hi! @Peterkrol12 In order to allow upload of larger files we would need to change a few settings to allow the web-server to send larger files. Could you elaborate on your deployment setup?

from appsmith.

Hi @sondermanish - We have a few appsmith instances running using the EC2 AMI

from appsmith.

Thanks! @Peterkrol12
Since the file size upload limit defined by default in the web-server configuration (Nginx) is less that what your current usages are, the web-server is truncating the files, hence the parsing doesn't happen.

We could try increasing the file upload limit using this variable in nginx configuration:
client_max_body_size . Adding a stack overflow issue for further understanding. Let us know if this works.
Or if the web-server is caddy then we would have to look for separate variables.
Let us know if you require help with setting up the configuration we can get on a call if required. Thanks!

from appsmith.

Hi @sondermanish - Thanks for your response!

I must say, I am not entirely following your suggestion. As provided previously, we are using the Appsmith AWS AMI on multiple instances. To access these instances, we only defined some DNS A records to point towards the public IP addresses of the instances. The only web server configuration we have, is in the AWS AMI of Appsmith itself. We looked through the instance and docker container and found a configuration file for Caddy called caddy-reconfigure.mjs. In this file, some properties including the Caddy client_max_body_size equivalent are defined. This property is set as follows:

  request_body {
    max_size ${process.env.APPSMITH_CODEC_SIZE || 150}MB
  }

So if done nothing, it should default to 150MB, but to verify, we looked at our docker.env in our EC2 instance. The APPSMITH_CODEC_SIZE property was defined in the docker.env, but it had leading # and was therefore commented out.

Am I looking at the wrong thing, or am I misunderstanding something?

from appsmith.

Thanks for the response @Peterkrol12
The APPSMITH_CODEC_SIZE is also used to control this spring variable spring.webflux.multipart.max-in-memory-size
which in essence is controlling the size of multipart request, by default it's set at 150 MB, we can try increasing that. Since this is also controlling the caddy file size, it would be easy for us to tweak this. Could you try increasing the value from 150 to a desired file size value?

from appsmith.

Thanks for the continues support @sondermanish!

I changed the APPSMITH_CODEC_SIZE environment variable in the docker.env to 500 and restarted Appsmith. Afterwards I tried the file upload part of our application and received the same exception.

from appsmith.

@Peterkrol12 Apologies it's not working for you, let me reproduce this and find an RCA for you.

from appsmith.