-
Notifications
You must be signed in to change notification settings - Fork 10.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Avatar upload to S3 bucket only works when initial avatar is set #15470
Comments
I just got some S3 logs from our cloud provider, related to this. For the last described profile image change with the posted mongodb entry where s3 object does not exist:
Matched based on
it seems the PUT came before DELETE which would explain why the image is not there |
I still see this with version 2.2.0 |
Same here.
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
well, its still broken... |
As far as I understand, the file is deleted when Rocket.Chat/app/file-upload/server/lib/FileUpload.js Lines 317 to 324 in 0351814
|
Workaround is to first set the Avatar to the initial avatar (First Character of your Name). Then Save. And only then upload the new avatar. |
Hi guys, is there a final solution for this issue? |
Same problem, but this workaround does not work |
Description:
RocketChat is configured to use AmazonS3 (but not with AWS S3 Service) as FileUpload storage type. Setting a new user avatar (upload or gravatar) works when the current avatar is the initial avatar (1st letter of name). When the avatar is set and a user uploads a new avatar, the new avatar is not stored in the S3 bucket and a broken image is shown. MongoDB entry is fine but object does not exist in S3 bucket. Reverting to initial avatar, does remove the MongoDB entry.
Steps to reproduce:
Expected behaviour:
the new user avatar should be store correctly no matter what previous avatar was used
Actual behavior:
MongoDB entry with initial avatar set:
MongoDB Entry when changing from initial avatar to a new profile picture. S3 Object exists
MongoDB after changing profile picture again. S3 Object does not exist
Server Setup Information:
Additional context
Relevant logs:
The text was updated successfully, but these errors were encountered: