Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[arpesenti]

I have a problem with Amazon S3 synchronisation. After I have configured everything and I click finish, it gives me "connection error". Even if I try to start the backup, it gives me "error", nothing more specific...
On the same network I have another d-link NAS, the dns-320, configured the same way for S3, and it works. Anyone does know a possible solution? Is it a firmware bug? I am using firmware 1.01b03.
Thank you

[arpesenti]

If someone is interested, I have found the problem and the solution.
Login in through ssh, I have found this error of the S3 upload script:

Code: [Select]

ERROR: ErrorRequestTimeTooSkewed 101
  Message: The difference between the request time and the current time is too large.
  Extra Details:
    MaxAllowedSkewMilliseconds: 900000
    RequestId: 943525BD92A127B8
    HostId: 3G59SwUoC6FtCdryD+Z7nnE+FI6pY95gUF0boLBeKQXWhgo+Fs4JrN0j4FdKXSFW
    RequestTime: Tue, 09 Apr 2013 18:59:49 GMT
    ServerTime: 2013-04-09T20:00:05Z
In another words, it compare the local time with the server time, and if the local time is not correct, BANG!
The solution is simply adjust time and date, manually or setting a NTP server...

[Kalei]

I use a D-Link DNS-320L. When I try to upload some file to Amazon S3 I get an unspecific error after 1 hour (less or more). There are no error informations in detail. The activation of the NTP server doesn't help. Any other ideas?

[jloram]

If someone is interested, I have found the problem and the solution.
Login in through ssh, I have found this error of the S3 upload script:

Code: [Select]

ERROR: ErrorRequestTimeTooSkewed 101
  Message: The difference between the request time and the current time is too large.
  Extra Details:
    MaxAllowedSkewMilliseconds: 900000
    RequestId: 943525BD92A127B8
    HostId: 3G59SwUoC6FtCdryD+Z7nnE+FI6pY95gUF0boLBeKQXWhgo+Fs4JrN0j4FdKXSFW
    RequestTime: Tue, 09 Apr 2013 18:59:49 GMT
    ServerTime: 2013-04-09T20:00:05Z
In another words, it compare the local time with the server time, and if the local time is not correct, BANG!
The solution is simply adjust time and date, manually or setting a NTP server...

Didn't work for me... I had my DNS-320 connected to a NTP server and time was right on. So still looking for a solution the the ERROR message.

-john-

[Acnescar]

It seems we are not alone!

https://forums.aws.amazon.com/thread.jspa?messageID=462937&#462937

Do Dlink really disavow any knowledge of an app that ships installed on their own products? Could anyone here point us towards any other ideas, investigation or support for this feature?

Thanks
Acne

[RobEcho]

Yes, I've also started threads related to this issue and contacted D-link tech support. Their answer is here:

https://forums.aws.amazon.com/thread.jspa?threadID=124862

[igglepiggle]

I am having the same problem - using firmware 1.03b04(3.07.0904.2013).

The time of the system is correctly synchronized with the NTP server and time zone is also correct.

Please help! This is so frustrating :-(

[Chill]

Not that I am trolling but had been searching online trying to figure out a solution. Same situation.
Any reply from DLink would be highly appreciated.


Thanks