-
Notifications
You must be signed in to change notification settings - Fork 575
Bucket name contains invalid characters #68
Comments
@xcompass Any thoughts on this question? |
Is there any special characters in your bucket name? Are you sure the error is triggered by Wal-E? Wal-E is only for backup, not image storage. Also it looks like it is trying to write to S3 from the error message, it doesn't sound like getting profile. Did you setup mattermost to use S3 as storage? It seems the error came from mattermost not wal-e based on the id (api.file.write_file.s3.app_error). https://github.com/mattermost/platform/blob/master/api/file.go#L754 If your bucket have "-" or any other special characters, that might be the cause. Because mattermost platform switched S3 library from goamz to minio-go (mattermost/mattermost@f02620b) And minio-go doesn't like "-". (https://github.com/minio/minio-go/blob/d02caa62b9e1034f93a82d41da806651a666c5a3/api-put-bucket_test.go#L145) And maybe some other characters. |
@xcompass I also noticed that it's not possile to include a folder name like |
Thanks @mtrofimm. It seems you have to use the bucket instead of the subfolder. It could be bug in Wal-E. |
I'm closing this for now. Let me know if there is any question. |
Having just upgrade from version 3.2 to version 3.5.1, I'm finding the Wal-E set-up against S3 complaining about bucket name. This wasn't something I was previously aware of.
In the console, I'm getting 500 errors when mattermost tries to get a user's profile image:
http://myserver.com:8001/api/v3/users/65k7nxg67t8uzknbzwtzeiqfnc/image?time=1464276885722
In the app, the user profile images are failing.
The bucket prefix looks like this:
WALE_S3_PREFIX=s3://mybucket.mattermost/version_3.0
As I've said, I used this in earlier versions without a problem.
Can't see any references to this problem on https://github.com/wal-e/wal-e
Any thoughts on what might be going wrong here?
The text was updated successfully, but these errors were encountered: