WS connections refused with 1006, even though token is correct
Nobody has claimed this yet.
- Dominant language
- Haskell
- Stars
- 2.8k
- Forks
- 334
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 50
Description
- I have seen https://docs.wire.com/ and https://github.com/wireapp/wire-server-deploy - the documentation there does not answer my question.
My question:
After running the production installation of wire server for ~ 20+ days, the ws connections are failing the upgrade with error code 1006, I have tried restarting cannon and nginz (because it was giving http 420, which I assume is a rate limit), but nothing helped.
Apart from re-deploying the entire backend I have not found a way to fix this behaviour, any Ideas on what I should check / do.
Currently I have failed over the misbehaving cluster to a "fresh one".
The normal requests that also require authorization are resolved with no issue with the same token (e.g. /notifications /list-connections)
Contributor guide
No contributing guide indexed for this repository
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 with the failing WebSocket upgrade path through cannon and nginz, reviewing their logs and the reported HTTP 420 alongside the successful /notifications and /list-connections requests. Compare the misbehaving cluster with the fresh cluster; done means the cause of code 1006 is identified and WebSocket upgrades succeed without redeploying the backend.
Written by the indexing model from the issue text.
Assessment
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100