Still problems with S3 after upgrading amazon.php file
By Rod Suskin on Wednesday, 27 January 2016
Posted in Technical Issues
Replies 9
Likes 0
Views 353
Votes 0
Hi
I have had the same issues with Amazon S3 US Standard as other users. I found and applied the amazon.php file.
When attempting to upload an image, I now get a new error:
"The request signature we calculated does not match the signature you provided. Check your key and signing method."
I have checked my key, I have tried with creating new keys with a new IAM user, but whatever I do I get this message. Can you help?
Thanks
Rod
Hey Rod,

What I would suggest you is the following:

1. Move the folders under the "images" to the root folder under nunkifiles/
2. Reconfigure your Amazon S3 settings and just set the bucket to nunkifiles

or

1. Provide me with the ftp and see if there's anything I can do to tweak the new Amazon S3 library (We needed to update the library because Amazon released a new authentication algorithm)
Mark
·
Thursday, 28 January 2016 00:34
·
0 Likes
·
0 Votes
·
0 Comments
·
Hey Rod,

Your bucket settings is actually incorrect, http://screencast.com/t/nQw3IpbxHO . It should just be nunkifiles . I have fixed this for you and it should work fine now
Mark
·
Wednesday, 27 January 2016 22:36
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi Mark

No this is not correct - this 'fix' broke my site and now no images are showing at all, only question marks where all the hundreds of images used to be. The path was always nunkifiles/images, it has been for years and was working until just few days ago. All the existing images are in nunkifiles/images and if you have a look at the bucket itself you can see it is set up this way.

I have changed it back - and all the existing images immediately returned. Doesn't the error message suggest that the incorrect key is being sent through to the S3 server? I have provided the correct keys in the settings, I have tried with two different S3 IAM users, is it possible the new amazon.php file is making a new error?

Thanks
Rod
Rod Suskin
·
Thursday, 28 January 2016 00:14
·
0 Likes
·
0 Votes
·
0 Comments
·
Hm, we have actually updated the Amazon S3 framework. I am not too sure if they are allowing this. Anyway can you please edit your first post above and include the FTP access?

If it doesn't work, can you move the files to the root of the bucket?
Mark
·
Thursday, 28 January 2016 00:20
·
0 Likes
·
0 Votes
·
0 Comments
·
Here is the S3 page
Rod Suskin
·
Thursday, 28 January 2016 00:22
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi Mark

Thanks for the help. I am trying your first suggestion - moving the folders to the root folder - and will let you know later when its done if it worked (seems to be a slow process on the S3 server side.) Otherwise I'll try the second suggestion but hopefully this will do it.

Rod
Rod Suskin
·
Thursday, 28 January 2016 00:45
·
0 Likes
·
0 Votes
·
0 Comments
·
Hey Rod,

Thanks, remember to change your bucket too in Settings > Remote Storage
Mark
·
Thursday, 28 January 2016 00:58
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi Mark

I have completed the copying process and changed the bucket settings, and it seems to be fixed! Clearly Amazon no longer allows subfolder paths for buckets. Thanks as always for your great support.

Rod
Rod Suskin
·
Thursday, 28 January 2016 14:43
·
0 Likes
·
0 Votes
·
0 Comments
·
Hey Rod,

Thanks for updating Glad that your issues are resolved now!
Mark
·
Thursday, 28 January 2016 15:08
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post