RocketChat / RocketChat/Rocket.Chat
Timeout while changing avatar without internet connection
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 editing the profile, users have to wait for the "Loading suggestions..." timeout to change their avatar, even if the option "Accounts_SetDefaultAvatar" is disabled.

Server Setup Information:
- Version of Rocket.Chat Server: 0.62.1
- Operating System: Debian
- Deployment Method(snap/docker/tar/etc): Tar
- Number of Running Instances: 3
- DB Replicaset Oplog: Enabled
- Node Version: 8.9.3
- mongoDB Version: 3.2.12
Steps to Reproduce:
- Disable the Internet connection or block gravatar.com on the rocketChat server
$ sudo iptables -A OUTPUT -d 192.0.73.2 -j DROP - Edit user profil in RocketChat
Expected behavior:
Do not try to contact gravatar.com when "Accounts_SetDefaultAvatar" is disabled or anything else that allow changing avatar without to wait for the timeout.
Actual behavior:
Users have to wait the timeout to gravatar.com to change their avatar
Relevant logs:
Mar 13 10:04:27 srv-01 nodejs-rocketchat0[26280]: rocketchat_logger rocketchat_logger.js:278 #033[34mMeteor ➔ method#033[39m getAvatarSuggestion -> userId: c8P5ygFNHtd2a4qDz , arguments: {}
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names the getAvatarSuggestion method and the Accounts_SetDefaultAvatar setting; start by tracing those references through the profile avatar flow. Reproduce with gravatar.com blocked or without an internet connection. Done means the disabled setting no longer triggers a Gravatar request or timeout, while users can still change their avatar.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, typescript
- Domain
- backend, frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100