- This topic has 8 replies, 3 voices, and was last updated 4 years, 12 months ago by
.
Viewing 9 posts - 1 through 9 (of 9 total)
-
Posts
-
I'm testing the Amazon S3 plugin. Small videos upload fine. However, when I try to upload a large file (about 300MB), I get a "413 Request Entity Too Large" error. My current hosting plan doesn't allow me to set the max file size above 128MB, and I don't understand max file size should be a problem because the video is being upload to Amazon anyway.hello, this is surely memory issue. please contact to your webhost for this. follow the steps as guided in another topic.As I mentioned, I cannot increase the memory beyond 128M, and most videos are going to be above that. How can I get around this with my limit? Isn't the video being uploaded to Amazon S3 anyway?Well actually im sorry there is not any solution available for this .The issue is in both video vibe and wplms s3 plugins . In both first the video file is uploaded to your server and then we read the whole file contents of the uploaded file in one go and upload it to the amazon s3 and vimeo servers . now when we read the content makes request to vimeo and amazon servers the request contents contains the video file binary data which is large . To upload the videos you need to increase your upload limit(upload_max_filesize) , and post max file size(post_max_size) in your php configuration on your server. Please contact your webhost to increase those and check again .Moving to wplms s3 forums.Well as of now there is no quick fix for this . But this is possible and we are surely gonna do it in upcoming updates of both amazon s3 and video vibe for vimeo .
Viewing 9 posts - 1 through 9 (of 9 total)
- The topic ‘Amazon S3 upload problem’ is closed to new replies.