Forbidden with Glacier

[planck]

Hello,

I have been trying to setup a profile to backup in Glacier. I'm sure that IAM permissions in Amazon are set correctly for my vault. Syncovery won't connect though:

Code: Select all

Left Side Volume Name:                Files

FTP Exception (3): EIdHTTPProtocolException HTTP/1.1 403 Forbidden @ 00F1DAE0
FTP Exception (3): EIdHTTPProtocolException HTTP/1.1 403 Forbidden @ 00F1DAE0

ERROR
GL://plbackup: Cannot access GL://plbackup
(HTTP/1.1 403 Forbidden at 00F1DAE0)


************************************************************************
Error (EPrepException): Cannot access GL://plbackup
(HTTP/1.1 403 Forbidden at 00F1DAE0) @ 010D6399
************************************************************************

Thanks
A.

[planck]

Here's also the ftplog.txt:

Code: Select all

Next FTP server: plbackup
18/11/2013 17:05:35 FTPConnect with timeout = 60000
StringToSign="AWS4-HMAC-SHA256
20131118T150535Z
20131118/eu-west-1/glacier/aws4_request
90a311f227f445dcfa456d0353dd61519b91b8521a488023fcd686894fce98f5"

DerivedKey=L'ϊ΅ΫG΅6““ŽF   ‰ˆδ/+
Γ[=ˆ`”q
ConnCheck: FALSE
ConnCheck: FALSE
ConnCheck: FALSE
ConnCheck: FALSE
ConnCheck: FALSE
ConnCheck: FALSE
WRITING TO SOCKET:
GET /-/vaults HTTP/1.1
x-amz-date: 20131118T150535Z
x-amz-glacier-version: 2012-06-01
Authorization: AWS4-HMAC-SHA256 Credential=AKIAJ425GRVOOEEWNF5Q/20131118/eu-west-1/glacier/aws4_request,SignedHeaders=host;x-amz-date;x-amz-glacier-version,Signature=befaca5c66d21e5a73af6686a77744593ae60e06d1112054770d43510adb0411
Host: glacier.eu-west-1.amazonaws.com
Accept: text/html, */*
Accept-Encoding: identity
User-Agent: Mozilla/3.0 (compatible; Indy Library)


WRITE END
ConnCheck: TRUE
ConnCheck: TRUE
RESPONSE:
HTTP/1.1 403 Forbidden

RESPONSE END
SyncFTPTraverser.Connect Result: FALSE

[planck]

Any ideas about this?

[superflexible]

I can only produce this result by specifying an incorrect Access ID or Secret Key. I think you have to make sure you copy and paste these credentials correctly from Amazon.

Also make sure that your machine's timezone and clock is set 100% correctly. A few seconds off, and the authentication will fail. Also if the timezone is not correct.