{"action":"created","issue":{"url":"https://api.github.com/repos/ParsePlatform/parse-server/issues/1616","repository_url":"https://api.github.com/repos/ParsePlatform/parse-server","labels_url":"https://api.github.com/repos/ParsePlatform/parse-server/issues/1616/labels{/name}","comments_url":"https://api.github.com/repos/ParsePlatform/parse-server/issues/1616/comments","events_url":"https://api.github.com/repos/ParsePlatform/parse-server/issues/1616/events","html_url":"https://github.com/ParsePlatform/parse-server/issues/1616","id":150752081,"number":1616,"title":"File uploads over 1MB fail (Code=3840) when using AWS vs Heroku or Parse.com","user":{"login":"barnaclejive","id":5251331,"avatar_url":"https://avatars.githubusercontent.com/u/5251331?v=3","gravatar_id":"","url":"https://api.github.com/users/barnaclejive","html_url":"https://github.com/barnaclejive","followers_url":"https://api.github.com/users/barnaclejive/followers","following_url":"https://api.github.com/users/barnaclejive/following{/other_user}","gists_url":"https://api.github.com/users/barnaclejive/gists{/gist_id}","starred_url":"https://api.github.com/users/barnaclejive/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/barnaclejive/subscriptions","organizations_url":"https://api.github.com/users/barnaclejive/orgs","repos_url":"https://api.github.com/users/barnaclejive/repos","events_url":"https://api.github.com/users/barnaclejive/events{/privacy}","received_events_url":"https://api.github.com/users/barnaclejive/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2016-04-25T05:28:32Z","updated_at":"2016-04-25T11:14:57Z","closed_at":null,"body":"This may sound strange but I have been able to consistently reproduce it.\r\n\r\nI have been testing using my app using 3 different backends and have noticed a difference in file upload success for files over 1MB.\r\n\r\n- Parse.com uploads work ok for all file uploads ✔️\r\n- Heroku hosted parse-server using S3 file adapter work ok for all file uploads ✔️\r\n- AWS hosted parse-server using S3 file adapter fail if the image size is over 1 MB. ❌ \r\n\r\nThe exception is:\r\n> Error Domain=NSCocoaErrorDomain Code=3840 \"JSON text did not start with array or object and option to allow fragments not set.\" UserInfo={NSDebugDescription=JSON text did not start with array or object and option to allow fragments not set.}\r\n\r\nThe Heroku and AWS hosted parse-servers use the exact same configuration (fileKey, mLab db, S3 bucket, S3 credentials, etc). Both are using the same version of parse-server-example which I have configured to use parse-server 2.2.7. They are both deployed from the same git repo.\r\n\r\nI understand this doesn't seem like it would be an issue with the parse-server itself, but in any case I would appreciate any thoughts on why parse-server would be responding with a JSON failure. The 1MB threshold makes it seem like there must be some explicit size check occurring along the way somewhere (AWS, S3, parse-server, or S3 Adapter)."},"comment":{"url":"https://api.github.com/repos/ParsePlatform/parse-server/issues/comments/214268435","html_url":"https://github.com/ParsePlatform/parse-server/issues/1616#issuecomment-214268435","issue_url":"https://api.github.com/repos/ParsePlatform/parse-server/issues/1616","id":214268435,"user":{"login":"mattgoldspink","id":415690,"avatar_url":"https://avatars.githubusercontent.com/u/415690?v=3","gravatar_id":"","url":"https://api.github.com/users/mattgoldspink","html_url":"https://github.com/mattgoldspink","followers_url":"https://api.github.com/users/mattgoldspink/followers","following_url":"https://api.github.com/users/mattgoldspink/following{/other_user}","gists_url":"https://api.github.com/users/mattgoldspink/gists{/gist_id}","starred_url":"https://api.github.com/users/mattgoldspink/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mattgoldspink/subscriptions","organizations_url":"https://api.github.com/users/mattgoldspink/orgs","repos_url":"https://api.github.com/users/mattgoldspink/repos","events_url":"https://api.github.com/users/mattgoldspink/events{/privacy}","received_events_url":"https://api.github.com/users/mattgoldspink/received_events","type":"User","site_admin":false},"created_at":"2016-04-25T11:14:57Z","updated_at":"2016-04-25T11:14:57Z","body":"Hi - I hit similar limits with server on AWS. Assuming you have a similar setup it's likely due to the limits on request size in the default nginx config. You can increase it following this blog post:\r\n\r\nhttps://kroltech.com/2014/09/14/quick-tip-increase-upload-size-in-aws-elastic-beanstalk-node-js-env/\r\n\r\nHope that helps."}}