Below are a couple things that may cause the S3 add-on to not work properly
- Your endpoint URL is incorrect. If you're using a non-AWS endpoint (e.g. Wasabi or Digitalocean spaces) you will need to provide an endpoint URL, make sure you use the correct one. Some providers require you to include the region in the endpoint URL so make sure you're using the correct region. Also make sure to add https:// in front of the endpoint URL, so one of Wasabi's endpoints is s3.us-east-2.wasabisys.com then fill in https://3.us-east-2.wasabisys.com as endpoint URL.
Some popular providers endpoints are:
Wasabi: https://wasabi-support.zendesk.com/hc/en-us/articles/360015106031-What-are-the-service-URLs-for-Wasabi-s-different-storage-regions-
Digitalocean spaces: ${REGION}.digitaloceanspaces.com
Linode spaces: https://www.linode.com/docs/guides/how-to-use-object-storage/#bucket-names
Backblaze B2: https://help.backblaze.com/hc/en-us/articles/360047425453-Getting-Started-with-the-S3-Compatible-API - Your Access key or Secret key is incorrect. Make sure you're using the correct keys for the correct fields.
If you're still unable to connect the add-on to your S3 endpoint then please feel free to create a ticket.
Comments
0 comments
Please sign in to leave a comment.