nextcloud / nextcloud/whiteboard
WebSocket Server setup with misleading status message
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 215
- Forks
- 39
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 32
Description
I've followed the instructions on the project page and search the issues, but I thought I can't get the websocket server to work. Well, the server works and responds, but adding the server and the secret to the admin config in my NC instance responds with the error message Failed to verify the connection: timeout.
However, the server is reachable from the NC instance, and it responds with HTTP/2 200.
I thought, it doesn't work at all, but then realized by accident, that clients using the whiteboard are actually getting connected.
The screenshot shows the error message in the admin UI, the clients are working, though.
And there is nothing in the logs either.
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 admin UI verification with the WebSocket server and secret, then compare the reported timeout with the successful HTTP/2 response and working whiteboard clients. Done means the admin status accurately reflects whether the server is reachable and usable, with the behavior covered by an appropriate check.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- full-stack
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100