RocketChat / RocketChat/Rocket.Chat

[6.3.3] Updating user profile image fails

Open
#30,330 11 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
46.1k
Forks
13.9k
Avg merge
3d 3h
Merged PRs (30d)
130

Description

Description:

When trying to set a new profile image via the web interface (https://rocketchat.example.com/account/profile), the application fails to set the new image when clicking the save button. A notification Internal server error appears.

The network tab of both Firefox and Chromium do not even show a submitted network request. There is also no error in the browser console. That means beyond the obviously wrong message (no request was ever sent to the server), there is not much to go on.

Updating the profile image via the Android app works without any issues.

There is one error in the browser console when opening the profile page:

image

Steps to reproduce:
  1. Open the path /account/profile on your server
  2. Select a new profile image from you local file system
  3. Hit the save button
  4. See the Internal server error message in the upper right corner
Expected behavior:

Show a better error message and work in the end.

Actual behavior:

image

Server Setup Information:
  • Version of Rocket.Chat Server: 6.3.3
  • Operating System: Debian GNU/Linux 11 (bullseye)
  • Deployment Method: tar
  • Number of Running Instances: 1
  • DB Replicaset Oplog:
  • NodeJS Version: 6.14.18
  • MongoDB Version: 5.0.20
Client Setup Information
  • Desktop App or Browser Version: Firefox 117.0 (64-bit) / Chromium 116.0.5845.110 (openSUSE Build) stable (64-Bit)
  • Operating System: Linux
Additional context

I'm operating multiple Rocket.Chat servers on the same version with the same Nginx and MongoDB versions (exactly the same, all deployed from the same configuration templates). This happens only on one of them. The main difference: the one that breaks uses a SAML login. I do not expect that this is relevant, but could be.

Relevant logs:

None at all that would be directly related to the error message.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at the /account/profile entry point and reproduce the failure in Firefox or Chromium, comparing the affected SAML server with a working server. Trace why selecting and saving an image produces no network request; done means the profile image is updated through the web interface and the error message is accurate.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.