If you're still unable to connect the add-on to your S3 endpoint then please feel free to create a ticket. Make sure you're using the correct keys for the correct fields. Your Access key or Secret key is incorrect.To use this operation, you must be allowed to perform the s3:PutBucketCORS action. If the configuration exists, Amazon S3 replaces it. Also make sure to add in front of the endpoint URL, so one of Wasabi's endpoints is s3. then fill in as endpoint URL.ĭigitalocean spaces: $. Description ¶ Sets the cors configuration for your bucket.
Some providers require you to include the region in the endpoint URL so make sure you're using the correct region. Wasabi or Digitalocean spaces) you will need to provide an endpoint URL, make sure you use the correct one. Below are a couple things that may cause the S3 add-on to not work properly
0 kommentar(er)
