You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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)
The text was updated successfully, but these errors were encountered:
I do have logs, but I don't know from which pod you would like to have the logs from, e.g. cannon returns an empty file kubectl logs $(kubectl get pods | grep cannon | awk '{print $1}') -c cannon
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 restartingcannon
andnginz
(because it was givinghttp 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
)The text was updated successfully, but these errors were encountered: