RocketChat / RocketChat/Rocket.Chat
video-conference/jitsi.update-timeout returns "405 method not allowed"
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 46.1k
- Forks
- 13.9k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 130
Description
Description:
Calling /api/v1/video-conference/jitsi.update-timeout returns "405 method not allowed" instead of updating the jitsi timeout
Steps to reproduce:
- Call the endpoint (POST) using
GENERALasroomId
Expected behavior:
The call succeeds
Actual behavior:
The call returns "405 method not allowed"
Server Setup Information:
- Version of Rocket.Chat Server: 5.0.1
- Operating System: Ubuntu 22.04
- Deployment Method: Docker
- Number of Running Instances: 1
- DB Replicaset Oplog: Enabled
- NodeJS Version: 14.19.3
- MongoDB Version: 5.0.10
Client Setup Information
- Desktop App or Browser Version: -
- Operating System: -
Additional context
Relevant logs:
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
Begin by locating the POST handler and route registration for /api/v1/video-conference/jitsi.update-timeout, using GENERAL as the roomId to reproduce the 405 response. Done means the endpoint accepts the POST request and updates the Jitsi timeout instead of returning "method not allowed".
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 35/100