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
I would like to set up webrecorder to use Linode's object storage service, which is s3 compatible. I noticed that webrecorder uses boto3 for s3 related functionality. I have updated the wr.env file with values for S3_ROOT=s3://mybucket.us-east-1.linodeobjects.com, AWS_ACCESS_KEY_ID=someid, and AWS_SECRET_KEY_ID=somesecret. Is there another variable that might need to be configured / exposed for boto3 to use an endpoint other than an AWS S3 endpoint?
When I try to start a capture, the browser console displays this error:
Hi, sorry that you're having trouble.. we haven't tested it in with other storage services, but in theory it should work! Perhaps something else is an issue.
It seems like the backend app container is perhaps not running/crashed... can you take a look at the log of the app container by running docker-compose logs app to see if there are any errors?
Also, just in case, try adding a / at the end of the S3_ROOT, as it assumes a path not just a bucket (can be a sub-path inside a bucket), so S3_ROOT=s3://mybucket.us-east-1.linodeobjects.com/
wr.env
file with values forS3_ROOT=s3://mybucket.us-east-1.linodeobjects.com
,AWS_ACCESS_KEY_ID=someid
, andAWS_SECRET_KEY_ID=somesecret
. Is there another variable that might need to be configured / exposed for boto3 to use an endpoint other than an AWS S3 endpoint?The text was updated successfully, but these errors were encountered: