开发环境CarrierWave可传至S3，Heroku生产环境上传失败求助

Hey there! Let's troubleshoot this CarrierWave + S3 issue on Heroku together—this is a super common gotcha, but totally fixable. Here are the key steps to diagnose and resolve it:

1. Double-Check Heroku Environment Variables #

First, confirm your AWS credentials are properly set in Heroku's environment—this is the #1 culprit for production upload failures. Run this command in your terminal:

heroku config

Verify that AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, AWS_BUCKET, and AWS_REGION are all present, with no typos. Pay extra attention to the bucket name (it must match your S3 bucket exactly) and region format (use the short code like us-east-1, not the full display name).

2. Validate Your carrierwave.rb Production Config #

Ensure your config file explicitly enables S3 storage for production. It should look something like this—don't skip the fog_provider line, it's easy to overlook:

CarrierWave.configure do |config|
  if Rails.env.production?
    config.storage = :fog
    config.fog_provider = 'fog/aws' # Critical for AWS integration
    config.fog_credentials = {
      provider: 'AWS',
      aws_access_key_id: ENV['AWS_ACCESS_KEY_ID'],
      aws_secret_access_key: ENV['AWS_SECRET_ACCESS_KEY'],
      region: ENV['AWS_REGION']
    }
    config.fog_directory = ENV['AWS_BUCKET']
    config.fog_public = true # Set to false if you need private files
  else
    config.storage = :file # Local storage for dev/test
  end
end

3. Make Sure Your Uploader Isn't Overriding Storage #

Open your uploader file (e.g., app/uploaders/your_uploader.rb) and check for any hardcoded storage :file that might override the global config. The ideal setup is to let the global config handle storage, or conditionally set it like this:

class YourUploader < CarrierWave::Uploader::Base
  # Let the global carrierwave.rb config decide storage
  storage Rails.env.production? ? :fog : :file
end

4. Confirm Your Gem Setup #

Ensure your Gemfile includes the correct Fog gem for AWS—fog-aws, not just the generic fog gem:

gem 'carrierwave'
gem 'fog-aws'

Run bundle install, commit the updated Gemfile.lock, and push to Heroku with git push heroku main.

5. Dig Into Heroku Logs for Clues #

Run this command while testing an upload in production to catch hidden errors:

heroku logs --tail

Look for messages about invalid credentials, bucket permission issues, or Fog initialization failures. Common red flags include:

• IAM user missing s3:PutObject permissions for your bucket
• Bucket policy blocking uploads from your app
• Mismatch between your config's region and the bucket's actual region

6. Verify S3 Bucket Permissions #

Make sure your IAM user has a policy that allows writing to the bucket. Here's a basic example policy to adapt:

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Action": ["s3:PutObject", "s3:GetObject", "s3:DeleteObject"],
      "Resource": "arn:aws:s3:::YOUR_BUCKET_NAME/*"
    }
  ]
}

If you're using public files, also confirm your bucket isn't set to block public access (adjust fog_public in your config if you need private files).

7. Restart Heroku Dynos #

After making any config or code changes, run:

heroku restart

Old configs can sometimes stick around until dynos are restarted, so this is a quick fix to rule out that issue.

内容的提问来源于stack exchange，提问作者Laurence