WS connections refused with 1006, even though token is correct
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- networking
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.
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)
- Dominant language
- Haskell
- Stars
- 2.8k
- Forks
- 332
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 49
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing 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.
More from wireapp/wire-server
-
Difficulty 1/5 Under an hour Newbie friendliness 83/100
wireapp/wire-server#5632 ·
Maintainers usually reply within 2 days
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
wireapp/wire-server#5443 · 1 comment ·
Maintainers usually reply within 2 days
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
wireapp/wire-server#5315 · 4 comments · 1 reaction ·
Maintainers usually reply within 2 days
-
Dependency DashboardOpen
Difficulty 5/5 Over a week Newbie friendliness 20/100
wireapp/wire-server#4754 ·
Maintainers usually reply within 2 days
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
wireapp/wire-server#4613 ·
Maintainers usually reply within 2 days
All issues in wireapp/wire-server
Similar issues
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
alunduil/siren-json.hs#264 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
alunduil/network-arbitrary#210 ·
Maintainers usually reply within 1 day
-
console: no way to refresh row data in Browse Rows without a full page reloadPossibly taken @12fahed claimed this 1 day ago. Openk/enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
hasura/graphql-engine#10895 · 1 comment ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
MorphRule, DataizeRule and ContextualizeRule silently accept unknown YAML keys, unlike rewrite `Rule`Possibly taken @renyamamoto2026-cmyk claimed this 2 days ago. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
objectionary/phino#2107 ·
Maintainers usually reply within 1 day