RocketChat / RocketChat/Rocket.Chat
No Push Notifications after update to 6.11.1
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 46.1k
- Forks
- 13.9k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 130
Description
Hi,
i have a problem with my selfhosted Chatserver.
After the automatic Update from Version 6.9.3 to Version 6.11.1 no Push-notification are send or receive and after every reboot/restart of the Server pops an notification on my client, that the id has significant changend and i have to make a new workspace or update an existing one. If i use the option to update the workspace no connect to the Chatserver are posible anymore and i have to reboot the server to make a new login possible. So i use the "new workspace" and it works. But this happens every reboot/restart of the server. So i deleted all workspaces in cloud.rocket.chat and assign my Server as a new self hostet one. But no push-notivications anymore.
What can i do to resolve this problem?
Server:
- Ubuntu 22.04
- Rocket.chat: 6.11.1
- Node: v14.21.2
- MongoDB: 5.0.15
- Numer of Users: 7
- Number of Running Instances: 1
- Clients: Android App/iOS App/ Browser: Chrome,Firefox and Edge
Thanks für your help!
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
Start by reproducing the upgrade from Rocket.Chat 6.9.3 to 6.11.1 using the reported Ubuntu 22.04, Node v14.21.2, and MongoDB 5.0.15 setup, with the listed Android, iOS, and browser clients. Check push delivery and the workspace ID-change prompt across server restarts; done means push notifications work and the workspace remains usable after reboot.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- mongodb, node.js, typescript, ubuntu
- Domain
- backend, mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100