Home/ Questions/Q 6572637
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-25T15:01:53+00:00

I store my uploaded files in amazon s3 services with the following command AWS::S3::S3Object.store(params[:uploadfile].original_filename,

  • 0

I store my uploaded files in amazon s3 services with the following command

AWS::S3::S3Object.store(params[:uploadfile].original_filename, open(params[:uploadfile]), 'mybucket', :access => :private, :content_type => params[:uploadfile].content_type)

I can upload file’s up to 30Mb without having a problem. I have read in other posts that this could be due to the fact the file is being loaded into memory(confused). The largest file i am going to upload is 40Mb, how can i achieve this without the upload failing.

My chrome browser returns the following error to me

Error 101 (net::ERR_CONNECTION_RESET): The connection was reset.

When i tried uploading from my development machine(localhost), i could upload large file > 80-100Mb, however its not working from heroku, i don’t understand why, because i am uploading files directly to s3.

Strangely my downloads fail after 30 seconds , which is the timeout limit that heroku sets, however i do not recieve any error of timeout or failed upload from heroku logs

Thank you for your help

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    After many months on this issue, i found a gem that works well, by uploading directly to amazon s3, without any complex flash, and javascript suff. I also integrates into carrierwave.
    The gem is called Carrierwave_direct

    Works without a problem, however if you are using rails 3.0.x checkout this page for a solution.

    If you are using rails rails 3.1.x, you are all set to go.

    • 0