By David Smith on Tuesday, 13 May 2014
Posted in Technical Issues
Replies 9
Likes 0
Views 616
Votes 0
Hi ES Team,

I have just updated my site to use Amazon S3 for remote file storage but am unable to get any files to sync. I have followed the guide and configured remote storage with an AWS IAM identity which I have checked via firefox s3 organizer.

It seems to me like I have set everything up appropriately but ES just isn't reacting to it.

My cron is appropriately configured (aka sends emails without a problem) and produces the following output:

[{"status":"200","contents":"There is nothing to dispatch currently.","time":"2014-05-13 09:51:21"},{"status":"200","contents":"No photos to upload to Amazon S3 right now.","time":"2014-05-13 09:51:21"},{"status":"200","contents":"No avatars to upload to Amazon S3 right now.","time":"2014-05-13 09:51:21"},{"status":"200","contents":"Nothing to process for files","time":"2014-05-13 09:51:21"}]

As always any help would be appreciated. Many thanks!
Hello David,

Is it possible for you to provide us with the back end and FTP access to your site to check on this issue?
·
Tuesday, 13 May 2014 21:39
·
0 Likes
·
0 Votes
·
0 Comments
·
Here it is
·
Wednesday, 14 May 2014 00:00
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi David,

I am sorry for the delay of this reply.

When I logged into your Joomla backend and when I attempt to access EasySocial setting page, I get this 'You are not authorised to view this resource.'. Anyway, regarding your issue, do you have the bucket created for S3? If yes, is the bucket region configured correctly?

Maybe you can send your S3 account so that we can verify your setting again?
Please advise.
Sam
·
Wednesday, 14 May 2014 17:55
·
0 Likes
·
0 Votes
·
0 Comments
·
Apologies for the settings mess up. I've fixed that user's permissions. I've also included s3 login below.

Since my last post I've discovered that s3 successfully pulls information that has been added to the site AFTER I set up the account. My understanding was that EasySocial would try and upload all of the media specified to s3 including locally stored items from before s3 was configured. Is that correct?

Additionally: the only user info on s3 right now is from a test user that I subsequently deleted. The users files are still on s3. Is that normal behavior?

Many thanks as always for amazing service,
·
Thursday, 15 May 2014 17:46
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi David,

I am sorry for the delay of this reply.

My understanding was that EasySocial would try and upload all of the media specified to s3 including locally stored items from before s3 was configured. Is that correct?


Yes, EasySocial will pull those photos files that haven't been synced before and push to S3

Additionally: the only user info on s3 right now is from a test user that I subsequently deleted. The users files are still on s3. Is that normal behavior?


Yes, currently EasySocial do not remove the photos from S3. This is what we actually planned to implement. When a user removed, all photos file that created by this user should get remove from S3 too We will see if we can put this into EasySocial 1.3 or not

Thanks and have a nice day
Sam
·
Monday, 19 May 2014 17:07
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi Sam,

You have confirmed how the site should be working - many thanks. It doesn't work though :/

I'm in the process of migrating servers right now. I will write back later today and let you know if something has changed. If not I'll update the login information for the site to reflect the new server.
·
Monday, 19 May 2014 17:35
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi David,

Sure, do let us know once you've done migrating your server and we will then look into your issues again.
Have a nice day!
Sam
·
Tuesday, 20 May 2014 10:53
·
0 Likes
·
0 Votes
·
0 Comments
·
Ok Sam it looks like it's working fine now. I'll let you know if anything else happens!
·
Tuesday, 20 May 2014 21:12
·
0 Likes
·
0 Votes
·
0 Comments
·
Thanks for updating David Glad that your issues are resolved now
·
Tuesday, 20 May 2014 22:38
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post