-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AWS S3 Region Missing #241
Comments
Hi, Have you double checked that eu-central-1 is in fact where the bucket is located? A common mistake is to mix the region that the AWS console is using with the region of the bucket. Ie, check the list of buckets for your account, and check what the region column says. If that checks out, make sure the (correct) env var is set, and check that that's in fact what ends up in your config file (doing If both of those seems ok, let me know and I'll look into if something in AWS has changed recently that I need to look at. A quick test shows that the S3 integration still works in my test environment, so it's either a config- or environment-specific thing. |
Hi André, yes that's the bucket region. The env var is correct it returns eu-central-1. Craft itself is handling the S3 upload fine. |
Ok, I'll try to set up a new bucket based on Andrew´s setup and see if I can reproduce. |
Hi, I've tested again, setting up a brand new AWS setup using Andrew's tutorial, and everything works as expected. I've tried provoking the error you're seeing, and the only way to get that exact error, is if |
I did try that. Somehow the error log for the missing region is gone in general. But I am still not seeing any image. Maybe there is something with my S3 setting. When I open the broken image I get an access denied xml file. |
I checked the debug toolbar.
|
I'm submitting a...
Description
I am gettin these missing region errors when I try to transform images from S3.
The default craft transforms are working fine.
Displayed errors, stack trace, relevant logs
my aws config for imager
Region is eu-central-1
Additional info
The text was updated successfully, but these errors were encountered: