Failing to increase maxFileSize to upload files larger than 200 MB

[Hellwest]

When I try to configure upload max file size it's always stuck at default value of 200 MB

Steps to reproduce the behavior
https://github.com/Hellwest/strapi-failing-upload-max-size (see commit history)

1. Initialize Strapi app with docker (I'm using PostgreSQL database)
2. Try to adjust your configurations in config/request.js

module.exports = {
  parser: {
    enabled: true,
    multipart: true,
    formidable: {
      maxFileSize: 900 * 1024 * 1024,
    },
  },
}

It fails.
3. Try to configure in extensions/upload/config/config.js

module.exports = {
  enabled: true,
  provider: "local",
  providerOptions: {
    sizeLimit: 900 * 1024 * 1024,
  },
}

It fails.

Expected behavior
I can upload a 700MB mp4 video file

Actual behavior/Screenshots

You can see maxFileSize is still ~200 MB on the screen

System

• Node.js version: 12.18.2
• NPM version: 6.14.5
• Strapi version: 3.0.5
• Database: PostgreSQL
• Operating system: Ubuntu 18.04/Linux Mint 19.3/Linux Mint 20

Additional context
Similar issues: #4156, #1975, #1906 and maybe #2737 (Suggested solutions don't work. I'm not using nginx, it's a clean repository, so body size can't be configured any other way)

[GiovanniFrigo]

I somehow managed to fix this by doing two things:

1. Putting the configuration for the formidable maxFileSize in extensions/upload/middlewares/upload/defaults.json (as somehow hinted here: https://strapi.io/documentation/v3.x/plugins/upload.html#configuration)
2. Freezing the formidable resolved version to "1.1.1" as the later versions seem to have some issues (node-formidable/formidable@39f27f2#commitcomment-28221459)

So, in practice:

1. create or edit the file extensions/upload/middlewares/upload/defaults.json with the following content (insert your own maxFileSize here, mine was 10 GB:

{
  "upload": {
    "enabled": true,
    "multipart": true,
    "formidable": {
      "maxFileSize": 10737418240
    }
  }
}

2. add the following lines to your package.json file:

 "resolutions": {
    "formidable": "1.1.1"
  }

then run yarn && yarn build to apply these settings.

This is most probably not the best way to solve this, but hey! it works ;)

[emmahyde]

I tried your approach @GiovanniFrigo and still getting

                                                                                                                                            
strapi_1  | [2020-07-20T15:38:04.779Z] error Error: maxFileSize exceeded, received 209780592 bytes of file data
strapi_1  |     at Stream.<anonymous> (/srv/node_modules/formidable/lib/incoming_form.js:222:19)

I have tried pretty much everything that seems to be on the docs, I really can't figure it out. I am not OP, but I've been struggling with this same issue all night! I cannot even remotely tell where this config is supposed to go. It is driving me insane.

[Hellwest]

@GiovanniFrigo worked for me. I didn't run yarn build though

[GiovanniFrigo]

@emmajhyde I honestly do not know what's fixing the thing anymore. I later deleted the extensions/upload/middlewares/upload/defaults.json, cleared the cache and rebuild (rm -rf .cache/ build && yarn build) and still is working.. so I'm now not sure anymore where the configuration lives ¯_(ツ)_/¯

In the trial and error phase that preceded my posting here, I experimented with many different config files (see them all here: https://gist.github.com/GiovanniFrigo/499e4ab1774d21eb6e9c8670eaaf943a) in a dumb attempt to try and find a way of setting the upload size.. but again, I'm not sure any of them is correct anymore.

Waiting for some maintainer to help us out.

[emmahyde]

@GiovanniFrigo I have no idea which config file gets used (I have so many at this point), but I noticed that NPM does not offer dependency version locks in the same way as yarn. I switched all my npm install & npm run builds to yarn & yarn builds, and did a yarn start. It appears that it's working! I would say that it's clear that the formidable version is a huge factor.

[jeanverster]

Thanks for this @GiovanniFrigo , worked for me 🎉

[RileyMShea]

@GiovanniFrigo I will try this shotgun approach and see what sticks.

[modjke]

For anybody struggling with where to put your config for upload middleware, use config/middleware.js
Contents:

module.exports = ({ env }) => {
  return {
    settings: {
      parser: {
        enabled: true,
        multipart: true,
        formidable: {
          maxFileSize: 10737418240 
        }
      }
    }
  }
}

[RyanPrentiss]

Was this issue resolved?

With or without middleware.js, I found through testing I can upload up to approximately 900MB, but nothing more, whether it be locally (Windows 10) or the Heroku deployment.

//version 3.1.1
module.exports = {
  settings: {
      parser: {
        enabled: true,
        multipart: true,
        formidable: {
          maxFileSize: 5 * 1024 * 1024 * 1024,
        },
      },
    },
  };

[silveur]

Had same issue until I specified a correct size in bytes in the middleware.js such as 1073741824 or like the above 5 * 1024 * 1024 * 1024
Then run npm run build

[gustawdaniel]

In my case

• solution of @modjke works
• solution of @GiovanniFrigo does not works
• no yarn build / npm run build was required