Unable save large file to S3 using Parse server

[kesongxie]

I tried to save to S3 bucket using Parse, and it can be saved correctly when the file is small, such as 864.2KB. However, when the file is large, say 5MB, it complaints with a message saying: "The data couldn’t be read because it isn’t in the correct format"

I'm using the following code to save the the video file to the S3

 func saveVideo(withVideoURL url: URL){
        let post = PFObject(className: "Post")
        post["caption"] = "Out of the game for 6 months, but back with vengeance. Meet your 2017 AO Men's champion"
        do{
            let data = try Data(contentsOf: url)
            print(data)
            post["media"] = PFFile(data: data)
            post.saveInBackground { (success, error) in
                if success{
                    print("video saved")
                }else{
                    print("failed")
                    if error != nil{
                        print(error!.localizedDescription)
                    }else{
                        print("erorr is nil")
                    }
                }
            }
        }catch let error as NSError{
            print("can't read")
            print(error.localizedDescription)
        }
    }

Besides, even when the small video file is indeed being saved to the S3, it contains an extension .bin instead of, for example .mp4. I wonder what's happening here
The url end up looking something like this

https://s3-us-west-1.amazonaws.com/sampleApp/19d5bce20f8b55te1b1b8f370212533e5_file.bin

[kesongxie]

Update: I have to use post["media"] = PFFile(data: data, contentType: "video/mp4"), now the video is correctly stored in the S3 with mp4 extension, and I can also stream it using AVPlayer, and now the remaining problem is the size, it seems I can't upload a video that is more than 1MB or something

[flovilmart]

Probably a problem with the load balancer in front of parse-server or the maxUploadSize option.

[kesongxie]

@flovilmart can you point me to any resources that I can verify or change the maxUploadSize. I understand the the default max upload size is 20 MB, is that correct?

[flovilmart]

The default should be 20Mb, you're right, the option is passed directly to express body parser: https://github.com/ParsePlatform/parse-server/blob/d5940b17b6914f04462420812aed9efe54a2b37f/src/Routers/FilesRouter.js#L22

[kesongxie]

In this case, can I just set my environment variable the same as how I set the variable such as MASTER_KEY or APP_ID, etc, and I add a new environment variable called maxUploadSizewith its value equals to 20mb. Will this overwrite the default setting?

[flovilmart]

That should be possible with "PARSE_SERVER_MAX_UPLOAD_SIZE"

[kesongxie]

Still complaining "The data couldn’t be read because it isn’t in the correct format." using saveInBackground when the file size is just 2.8MB

[flovilmart]

What is complaining? The client or the server?

[kesongxie]

The output from the Xcode, also just found this on the log on ELB
2017/02/19 20:48:40 [error] 26869#0: *120 client intended to send too large body: 2771673 bytes, client: 172.31.20.12, server: , request: "POST /parse/files/file HTTP/1.1", host: "parseserver-bjqgv-env.us-east-1.elasticbeanstalk.com"

I think it may be the AWS that is setting the file size limit somewhere

[flovilmart]

so that's on your elastic beanstalk configuration then:

http://lmgtfy.com/?q=elastic+beanstalk+set+max+upload+size
http://serverfault.com/questions/618101/aws-elastic-beanstalk-file-upload-limit-issue#679854

[kesongxie]

Now it works after setting the client_max_body_size to a larger value. See how you set the value, you can refer it here http://websistent.com/fix-client-intended-to-send-too-large-body-nginx-error/

[HackShitUp]

@flovilmart could the default should be 20Mb file size be modified from the index.js file from the example parse server?

[flovilmart]

You should set it in your configuration object

[omarojo]

I have the same issue but in Heroku which I think it uses Express. I set the server property.
Im still getting the error, any ideas?