Fails with "Invalid secret key"

Bug #362899 reported by Michael Terry
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Déjà Dup
Fix Released
High
Michael Terry

Bug Description

I'm using Deja Dup 8.1 on Jaunty (from the PPA). I get the above whenever I try a test backup to Amazon S3. My S3 account is active and I use it through other means so I know it is valid. I've tried a number of variations and it always comes back to the same message. Just to verify:

I set backup location to Amazon S3. Next I enter my Access Key ID from Amazon (not my Secret Key). I leave the folder as /, though I have tried using a known subfolder from the account. I chose a sample local folder with data for a test and leave exclude on Trash. I then check Encryption and close. When I select Backup it gives me a summary with the backup location "Folder / on Amazon S3." It says "preparing" then "backing up" and the first couple of file names flash across then it pops up "Backup Failed" and the message above, "Invalid Secret Key."

I've tried it with and without encryption. I have cleared the values from gconf and begun again. I even placed my existing bucket name in the gconf slot where Deja Dup was making up a new one. I've deleted the password/passphrase from the keyring and it then pops up a secondary window asking for a password along with my "username" (which is my Amazon S3 Access Key ID). I've used my Secret Key and I've used a random passphrase for encryption.

Let me know if I can try something else. I like the simplicity of this app and would like to start using it. With a couple more small features, I think it might be just the thing for basic Linux backups.

Thanks.

Revision history for this message
Michael Terry (mterry) wrote :

Thanks so much for the report, David. I like the detail! :) To help figure this out, can you provide me:

The file /tmp/deja-dup.log after running the following line and replicating the problem:
    DEJA_DUP_DEBUG=1 deja-dup | tail -n 200 > /tmp/deja-dup.log

Changed in deja-dup:
importance: Undecided → High
status: New → Incomplete
Revision history for this message
David Rahrer (david-rahrer) wrote : Re: [Bug 362899] Re: Fails with "Invalid secret key"
  • deja-dup.log Edit (8.0 KiB, text/x-log; charset=US-ASCII; name="deja-dup.log")

Hi Michael,

I've attached the log file as requested. I didn't think it wise to post a
file on the bug thread in the open with my Amazon Access key so I have
replaced any instances of it appeared there with "07xxxxxxxxxxxxxxxxx02". If
that won't suffice, let me know and I'm sure we can work it out so I can
send it directly to you.

I don't mind testing whatever you need -- it's the least one can do for
great software!

David Rahrer

On Fri, Apr 17, 2009 at 8:39 AM, Michael Terry
<email address hidden>wrote:

> Thanks so much for the report, David. I like the detail! :) To help
> figure this out, can you provide me:
>
> The file /tmp/deja-dup.log after running the following line and replicating
> the problem:
> DEJA_DUP_DEBUG=1 deja-dup | tail -n 200 > /tmp/deja-dup.log
>
> ** Changed in: deja-dup
> Importance: Undecided => High
>
> ** Changed in: deja-dup
> Status: New => Incomplete
>
> --
> Fails with "Invalid secret key"
> https://bugs.launchpad.net/bugs/362899
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message
David Rahrer (david-rahrer) wrote :

Hi Michael,

I've attached the log file as requested. I didn't think it wise to post a file on the bug thread in the open with my Amazon Access key so I have replaced any instances of it appeared there with "07xxxxxxxxxxxxxxxxx02". If that won't suffice, let me know and I'm sure we can work it out so I can send it directly to you.

I don't mind testing whatever you need -- it's the least one can do for great software!

Revision history for this message
Michael Terry (mterry) wrote :

Thanks! I'll look at this over the weekend, but at first glance, it looks like what it says: a bad secret key for the given access key, though it sounds like you're pretty sure you've entered it correctly. I'll test with some of my S3 accounts and see if I can reproduce on my end.

Changed in deja-dup:
status: Incomplete → New
Revision history for this message
Marcel Hecko (maco) wrote :

Hi Michael,
I am a newbie to the S3, however I am having the same problem with the S3 as written in the bug definition. I can log-in to S3 using http://s3browse.com but cannot using deja-dup.

I'm using the default distribution from [upgraded] jaunty.

Revision history for this message
Marcel Hecko (maco) wrote :

I have upgraded to 8.1, however does the same thing. I am attaching the debug file - same as David.

Revision history for this message
Marcel Hecko (maco) wrote :

Michael, let me apologize for my faulty bugreport! It has obviously been my fault - I have been copy&pasting the secret key from AWS page and it looks like when you double-click the key on they portal page it gets copied with a blank character at the beginning of the string. Other software obviously ignore these blank spaces.
From the users perspective I suggest deja-dub does the same for Amazon S3 accounts, since I doubt there can be a key with blank characters likely to occur in the secret key.
I'm syncing already! :)

Revision history for this message
Michael Terry (mterry) wrote :

Marcel, that's a great idea. Unfortunately, I didn't see your comment until after I just released 9.0. I'll put it in for the next release. Thanks for the catch!

David, try pasting your secret key into gedit or something first. Do you think the extra space was your problem too?

Changed in deja-dup:
assignee: nobody → Michael Terry (mterry)
status: New → In Progress
Revision history for this message
Michael Terry (mterry) wrote :

The 'extra space' issue is so likely to have been the problem, that I'm closing this bug now that Deja Dup 9.1 is out with a fix for that (released today). David, if that turns out not to have been your problem, please let us know!

Changed in deja-dup:
status: In Progress → Fix Released
Revision history for this message
David Rahrer (david-rahrer) wrote :

I apologize for the delay. This does appear to have been my problem as well. It works now -- thank you!

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related questions

Remote bug watches

Bug watches keep track of this bug in other bug trackers.