I am also experiencing the same issue. Files on the server are created but they are not streaming to S3. I did some digging around and looks like curl_exec fails in lib.s3.php, line 291 with “Couldn’t resolve host ‘mybucketname.s3.amazonaws.com'”. Hope this helps Brad with troubleshooting.
Thanks, Abel
I think it may be that Amazon changed the way buckets work now.
I had to create ACL’s for the bucket in question and it seems to work ok now. Doing that through the Amazon S3 web interface is totally incomprehensible (I’m not a coding noob either). I found a program called “Bucket Explorer” which seems to work ok, although it’s not cheap.
I just futzed around with various ACL settings until it worked.
Thanks for digging into this guys. I’m not sure when I’m going to get to this, but I’m definitely open to pull requests at https://github.com/bradt/wp-tantan-s3 if you’d like to take a crack at fixing it yourself. 🙂
yeah, looking like this plugin is no longer working on a whole bunch of installs. Drag – when it works, it was pretty cool!
D C
(@dcervenka)
Hi – I’m looking for an S2 plugin and I’m curious if this issues with the plugin has been fixed?
I just uploaded images to the WP Media Library and found nothing in S3. Is there any activity analyzing this problem & fixing it?
Is this plugin still not working? Any fixes?
I think it depends on your install – it works fine on ours. We’re using cloudfront as opposed to just the general s3 buckets.
I just set it up last week on a new site locally (MAMP) and deployed it to AppFog and it worked fine in both environments.
I found I had to add an ACL to the bucket to allow uploads; essentially
{
“Version”: “2008-10-17”,
“Statement”: [ {
“Sid”: “AllowPublicRead”,
“Effect”: “Allow”,
“Principal”: { “AWS”: “*” },
“Action”: “s3:GetObject”,
“Resource”: “arn:aws:s3:::<bucketname>/*”
} ]
}
I just released a complete rewrite of this plugin (version 0.6) that takes care of this. 🙂
I have version 0.6.1 and i still can’t upload. This just happened overnight with no changes to the env.
Tried adding the policy to no avail.
@maciekish Are you getting an error?
It is not working for me either. I tried two different websites and while the files do upload to the website server, nothing is showing up at S3.
The connection with S3 does work because all of the images etc that were uploaded with FTP are available to the wordpress installation.
I just tried it again. After uploading I choose to edit image and I see the image. When I choose “view attachment page” the page shows up with no image. Just the broken image icon. If I click the broken image icon, the following url and error appear.
http://s3-us-west-1.amazonaws.com/cdn.happehtheory.com/wp-content/uploads/2013/10/Dome_Head_Example_0003.jpg
<Error>
AccessDenied
<Message>Access Denied</Message>
<RequestId>1F8DEE6C32EED1B7</RequestId>
<HostId>
1tUCbmCvksv5Vsnyr2qiMIaj4XqYSAkxgdsowNOY5dM9cEBuWvEfsyAM75FRd+PE
</HostId>
</Error>
I have checked the AWS plugin and it says:
“You’ve already defined your AWS access keys in your wp-config.php. If you’d prefer to manage them here and store them in the database (not recommended), simply remove the lines from your wp-config.”
I checked the security keys and they look correct. They were cut and pasted, not hand keyed, so I am pretty sure they are right.
I just chose a random image that was uploaded through FTP previously and if the same series of steps as described above is repeated, the image can be seen at the amazon S3 Url,
http://s3-us-west-1.amazonaws.com/cdn.happehtheory.com/wp-content/uploads/2013/09/Inspiration_00079.jpg
so I am pretty sure the connection between the website and S3 is fine.
I was going to post the solution to my problem but the thread has been marked “resolved” so I guess it doesn’t matter anymore.
