You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Finish the setup and complete the installation wizard
Upload a file and try to download it
Go to the Admin app and upload the attached file to the File Manager
Attempt to download the file
This results in the lambda returning "internal server error", instead of downloading the file
File that causes the problem
hein_test.mp4
What is the expected behavior?
The file should be downloaded successfully
What do you see instead?
{"message":"Internal Server Error"}
Additional information
The interesting part is that larger files and smaller files do work. However, we have several files in this ~5 Mb file range and they all seem to fail. It looks like it has something to do with the fact that the filemanager lambda switches to a 301 for larger files and serves smaller files directly. But somewhere in the middle it fails.
Possible solution
No response
The text was updated successfully, but these errors were encountered:
We did some further experimentation, and it seems that files smaller than 4703427 bytes and files larger than 5095107 always seem to work. But somewhere between that range the file-manager is unable to serve the files and returns internal server error.
Version
5.38.1 (but also applies to 5.33.0)
Operating System
Mac OSX
Browser
Google Chrome
What are the steps to reproduce this bug?
Setup a fresh Webiny project:
npx create-webiny-project my-filemanager-test
yarn webiny deploy
Upload a file and try to download it
File that causes the problem
hein_test.mp4
What is the expected behavior?
The file should be downloaded successfully
What do you see instead?
{"message":"Internal Server Error"}
Additional information
The interesting part is that larger files and smaller files do work. However, we have several files in this ~5 Mb file range and they all seem to fail. It looks like it has something to do with the fact that the filemanager lambda switches to a 301 for larger files and serves smaller files directly. But somewhere in the middle it fails.
Possible solution
No response
The text was updated successfully, but these errors were encountered: