Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error Getting Session Token #18

Closed
dillonbailey opened this issue Mar 14, 2018 · 5 comments
Closed

Error Getting Session Token #18

dillonbailey opened this issue Mar 14, 2018 · 5 comments

Comments

@dillonbailey
Copy link

dillonbailey commented Mar 14, 2018

Hello!

Running into an issue that has been a little difficult to track down. The attached error message appears whenever I try to upload a file via the Admin. I have tried using admin level API Key/Secret so I do not believe it's an IAM permissions issue with S3 as this still results in the error.

screen shot 2018-03-15 at 8 51 07 am

##Admin Configuration
screen shot 2018-03-15 at 8 56 09 am

# The AWS API key with read/write access to S3
S3_API_KEY="xxx"

# The AWS API key secret
S3_SECRET="xxx"

# The name of the S3 bucket
S3_BUCKET="assets.thewellresource.org.au"

# The region the S3 bucket is in
S3_REGION="ap-southeast-2"
<?php

return [
    's3Uploads' => [
        'hasUrls' => true,
        'url' => 'https://'.getenv('S3_BUCKET').'.s3.amazonaws.com/',
        'keyId' => getenv('S3_API_KEY'),
        'secret' => getenv('S3_SECRET'),
        'bucket' => getenv('S3_BUCKET'),
        'region' => getenv('S3_REGION'),
    ],
];
@dillonbailey
Copy link
Author

Quick follow-up...

As soon as I attempted the same configuration from my EC2 instance it worked like a charm. So I do not know if there are any specific issues with this working from a local vagrant box?

@dillonbailey
Copy link
Author

And...after rebooting vagrant the issue is gone...

Opened and closed in 15 minutes ‼️

@angrybrad
Copy link
Member

Been waiting all day to us this, so thanks!

https://www.youtube.com/watch?v=p85xwZ_OLX0

@andris-sevcenko
Copy link
Contributor

For future reference, you get that error when the system making the call does not have the system clock set correctly.

@dillonbailey
Copy link
Author

Cheers, I was trying to decipher the meaning of time travel with that error message, but makes perfect sense.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants