Discourse + Wasabi (S3-Compatible Storage)

Is it currently possible to backup to Wasabi? I attempted to configure this, but could not seem to get it to work with the most recent version of Discourse. It seems like this would be a straightforward matter, but no combination of settings seems to have worked. Perhaps something is off with region selection?

@gerhard do you know if that’s possible?

1 Like

It depends on how compatible Wasabi is, but I’d expect that the basic stuff will work. Downloading and or uploading to/from the client might fail unless they also support pre-signed URLs.

Are you getting any errors in the logs?
Looking at the documentation of Wasabi, it supports 2 regions:

  • us-east-1, US East (N. Virginia)
  • us-west-1, US West (N. California)

Have you tried those two?

4 Likes

I tried quite a few different regions, including us-east-1 and us-west-1.

Here are the two errors showing up in the logs:

Failed to list backups from S3: Aws::S3::Errors::BadRequest

Failed to list backups from S3: The authorization header is malformed; the region 'us-east-1' is wrong; expecting 'us-west-1'

(n.b., for testing purposes, I’m working with root-level permissions, so that is one potential issue that can almost certainly be eliminated.)

1 Like

It seems to be working now with the following combination:

  1. us-west-1 (US West (N. California) in Discourse; Hillsboro (OR) for Wasabi)

  2. https://s3.us-west-1.wasabisys.com as the endpoint (s3.wasabisys.com is the endpoint for the East region)

As any S3-compatible storage can be used with Discourse, it may be clearer to have the drop-down menu for region selection display the region identification (e.g., us-west-1) instead of or along with the region name (e.g., US West (N. California)).

4 Likes

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.