-
Notifications
You must be signed in to change notification settings - Fork 23
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
Error: Unable to retrieve bucket contents. #12
Comments
Sorry, I have no way of helping without further error logs. On May 10, 2014 at 8:43:50 PM CDT, lBroth [email protected] wrote:Hi, I have an Error: Unable to retrieve bucket contents. on ./autosmush subdomain.domain.com The name of bucket is a subdomain because i have enabled website hosting for get images by subdomain.domain.com Thanks —Reply to this email directly or view it on GitHub. |
@lBroth : Were you able to resolve the error? Even I am getting same error. After digging into autosmush.php, I realized that Amazon was returning status 301 instead of 200 and therefore this error is getting logged. |
No, i don't use Autosmush on my bucket. Unfortunately with subdomain autosmush not get the bucket. |
That is shocking. I thought autosmush supports subdomain. Thanks for the reply. |
@tylerhall How can I get you the error logs or what do you need as I am also experiencing the same issue and get the error "Unable to retrieve bucket contents". My bucket is in the form of "subdomain.domain.com". |
Just an update for anyone intrigued. If I bypass this check, when it retrieves the bucket contents through the AWS API, it returns 0 and the script again fails. Anyone have any ideas? |
I am also facing same error because bucket headers are returning 403 status code. Is there any settings or configurations to be done in s3 bucket ? |
Hi,
I have an
Error: Unable to retrieve bucket contents. on ./autosmush subdomain.domain.com
The name of bucket is a subdomain because i have enabled website hosting for get images by subdomain.domain.com
Thanks
The text was updated successfully, but these errors were encountered: