RocketChat / RocketChat/Rocket.Chat
Federation: Public Key missing in 4.8.3 and 5.0.2 (Snap on Ubuntu Server 22.04)
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 46.1k
- Forks
- 13.9k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 130
Description
Description:
After a clean install using snap method on Ubuntu Server 22.04, which installs 4.8.3 per default at the moment, when you go to the federation settings, the public key information is not shown (empty box). Therefore one is not able to create the required TXT entry for his domain. If you update to 5.0.2 afterwards, the problem still remains.
Steps to reproduce:
- Install Ubuntu Server 22.04
- Install Rocketchat Server (# snap install rocketchat-server)
- Complete Setup Wizard
- Got to federation settings in Admin Panel > Public Key information is missing
Expected behavior:
Public Key should be generated automatically and be shown in the federations settings menu.
Actual behavior:
Public Key is not shown in the federations settings menu.
Server Setup Information:
- Version of Rocket.Chat Server: 4.8.3, problem remains after update to 5.0.2
- Operating System: Ubuntu Server 22.04
- Deployment Method: Snap
- Number of Running Instances: 1
- MongoDB Version: 4.4.15
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 at Admin Panel > federation settings and reproduce the missing public key on a clean Ubuntu Server 22.04 Snap installation, including the reported upgrade from 4.8.3 to 5.0.2. Trace how the federation public key is generated and exposed there; done means the key is automatically generated and shown so the TXT record can be created.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- mongodb, ubuntu
- Domain
- backend, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100