Skip to content

WS connections refused with 1006, even though token is correct #3377

@Twiggeh

Description

@Twiggeh

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)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions