S3Sync.net
February 02, 2014, 01:19:45 PM *
Welcome, Guest. Please login or register.

Login with username, password and session length
 
   Home   Help Search Login Register  
Pages: [1]
  Print  
Author Topic: s3 suddenly completely broken - 403 forbidden  (Read 7756 times)
jh
Newbie
*
Posts: 12


View Profile
« on: March 20, 2008, 07:56:15 AM »

All of sudden, I'm getting "403 forbidden" messages and nothing with s3 works.  Here's the output of "s3cmd -v listbuckets"

list all buckets {}
S3 command failed:
list_all_my_buckets
With result 403 Forbidden

I haven't changed anything on my end.

Ideas?
Logged
ferrix
Sr. Member
****
Posts: 363


(I am greg13070 on AWS forum)


View Profile
« Reply #1 on: March 21, 2008, 05:05:52 PM »

Try with another app to confirm it's not a config issue.  Try with SSL, maybe you are being proxied.  If that fails, then I'd blame the id/secret next.  If that fails, check if you paid your S3 bill? Wink

If you can wireshark or tcpdump the non-ssl transaction (whole packets not just the useless headers) you may be able to see a more detailed error in the response.
Logged
diezmon
Newbie
*
Posts: 3


View Profile
« Reply #2 on: June 01, 2008, 09:40:13 PM »

I was having the same issue.. looks like it's a clock issue with my PC.

http://developer.amazonwebservices.com/connect/entry.jspa?externalID=1109&categoryID=55#04
Logged
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2013, Simple Machines Valid XHTML 1.0! Valid CSS!