Can not change avatar in sentry on premise

On-Premise
1

Hi, i just already set up sentry on premise with docker.
When i want to change avatar, i got error :

image
image2440×1470 425 KB

How to solve this?

2

I don’t know you should share the logs of the error. Errors would get spewed to stderr of the web processes and also get logged to the internal project. But without that information, and infinite number of things could be wrong.

3

Thanks Matt for responding.
My config.yml

################
#File storage#
################

#Uploaded media uses these filestore settings. The available

#backends are either filesystem or s3.

#filestore.backend: ‘filesystem’

#filestore.options:

#location: ‘/data/files’

#dsym.cache-path: ‘/data/dsym-cache’

#releasefile.cache-path: ‘/data/releasefile-cache’

filestore.backend: ‘s3’

filestore.options:

access_key: ‘AK****’

secret_key: ‘Ul*****’

bucket_name: ‘my-bucket’

system.internal-url-prefix: ‘https://my-domain.ralali.com’

symbolicator.enabled: true

symbolicator.options:

url: “http://symbolicator:3021”

When i check the error by doing this :

docker logs sentry_onpremise_web_1

The logs when uploading avatar :

ClientError: An error occurred (AccessDenied) when calling the PutObject operation: Access Denied

54.169.173.154 - - [16/Apr/2020:10:10:12 +0000] “PUT /api/0/organizations/ralali_sentry/avatar/ HTTP/1.0” 500 649 “https://my-domain/settings/sentry/” “Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.132 Safari/537.36”

So, i double checked my access key by doing put object from aws-cli. It worked without Access Denied error.

Screen Shot 2020-04-16 at 17.38.30
Screen Shot 2020-04-16 at 17.38.301752×136 38.4 KB

Question

  1. Is there another way to check the log? Im just curious
  2. Why i got access denied error when my access key is already has the access to put object?
4

I really don’t know. The error message is obviously what we’re getting back from S3. We used to use this years ago, but haven’t since then. It worked fine back then. If there’s a bug or something now, happy to accept a PR. But it seems more the credentials are wrong.