You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Aws\S3\Exception\S3Exception
Error executing "PutObject" on "https://s3.eu-central-1.amazonaws.com/tabbie/tournaments/TournamentLogo-test-iv--23.jpg"; AWS HTTP error: Client error: `PUT https://s3.eu-central-1.amazonaws.com/tabbie/tournaments/TournamentLogo-test-iv--23.jpg` resulted in a `403 Forbidden` response:
<?xml version="1.0" encoding="UTF-8"?>
<Error><Code>InvalidAccessKeyId</Code><Message>The AWS Access Key Id you provided (truncated...)
InvalidAccessKeyId (client): The AWS Access Key Id you provided does not exist in our records. - <?xml version="1.0" encoding="UTF-8"?>
<Error><Code>InvalidAccessKeyId</Code><Message>The AWS Access Key Id you provided does not exist in our records.</Message><AWSAccessKeyId>AKIAI3LZY3B2LAUFIX3Q</AWSAccessKeyId><RequestId>8F8EDEE373965D00</RequestId><HostId>g5o8qty+LnSdvr04bb6HvIiJ8O+ssbvB5+PYUDZy7uqXvGRHyOBnWZARajrkgKiVi9mGzc09JBg=</HostId></Error>
↵
Caused by: GuzzleHttp\Exception\ClientException
Client error: `PUT https://s3.eu-central-1.amazonaws.com/tabbie/tournaments/TournamentLogo-test-iv--23.jpg` resulted in a `403 Forbidden` response:
<?xml version="1.0" encoding="UTF-8"?>
<Error><Code>InvalidAccessKeyId</Code><Message>The AWS Access Key Id you provided (truncated...)
in /var/www/virtual/tabbie/tabbie2/tabbie2.git/vendor/guzzlehttp/guzzle/src/Exception/RequestException.php at line 107
Looks like the AWS credentials have expired?
The text was updated successfully, but these errors were encountered:
philipbelesky
changed the title
Creating tournaments fails
Creating a new tournament fails
Feb 11, 2018
Yup, the workaround is to not provide an image when creating a tournament. But this is probably not clear unless you are good at reading error messages!
Full error report:
Looks like the AWS credentials have expired?
The text was updated successfully, but these errors were encountered: