Summary Constant websocket errors on version 7.0.1. Steps to reproduce Since updating to version 7.0.0 about two weeks ago, our server is constantly getting this websocket error. I’ve checked the logs prior to the update, and there was no instance of this error before. During the weekend we have …

Thanks for the detailed reply. Indeed, our log level was at INFO, which could explain the lack of errors prior to the update. Unfortunately, we are not using load-balancers, so that shouldn’t be our issue. Users used to occasionally report, and continue to do so, the failure of sending messages (…

There’s a lot of unrelated issues here and we shouldn’t confuse it with the websocket issue. The limit exceeded error is due to rate limiting and unrelated. Failure to send messages is also not related to websocket as it’s an API call. If you are not using load-balancers, can you think of somethin…

I also have lots of the i/o timeout error messages in the logfile with self hosted Mattermost E10 v7.0.1. error [2022-07-13 10:59:37.016 +02:00] websocket.NextReader: closing websocket caller=“app/web_conn.go:834” user_id=ji86zwegt7rbfqgfxbs1niqd6y error=“read tcp 127.0.0.1:8065->127.0.0.1:5…

Hello @TI-Admin - as noted before, the timeout error was always getting logged in the debug level. Only a recent change in 6.6 started to log it at error level. There has been no code changes to cause this. Something in your infrastructure is causing this - please have a read through Constant webso…

[image] Podesta: {“timestamp”:“2022-06-27 18:59:36.184 Z”,“level”:“error”,“msg”:“websocket.NextReader: closing websocket”,“caller”:“app/web_conn.go:834”,“user_id”:“rrwhycr46fgb5m143xcpqdoxma”,“error”:“read tcp 127.0.0.1:8080->127.0.0.1:56834: i/o timeout”} @Podesta - You mentioned that you ar…

@TI-Admin - Your log line says 127.0.0.1:8065->127.0.0.1:51470: i/o timeout. So it seems like something at 127.0.0.1 is connecting to Mattermost? Do you know what that is? If it was a direct client connection, I’d expect the client IP to be something other than 127.0.0.1.

I thought you tell me. The log is full of those errors and the ports start at 127.0.0.1:32768 up to 127.0.0.1:60998. Is it possibly nginx related which is used as a proxy?

Yes, please check your nginx logs (/var/log/nginx/error.log). Do you see any “upstream connection failed” messages or something like this in there?

Yes, there are lots of GET and POST errors like these: 2022/07/15 04:00:28 [error] 853417#853417: *43108 connect() failed (111: Connection refused) while connecting to upstream, client: 94.134.231.35, server: wetalk.informatik.uni-kiel.de , request: “GET /api/v4/websocket?connection_id=kcu6trax1pb7…

Constant websocket errors

Troubleshooting

TI-Admin (Henrik S.) July 13, 2022, 6:01pm 13

I’ve read this but we do not use a load balancer and since the infrastructure did not change since we started to use Mattemost almost two years ago, I have no clue how to fix this problem.

Topic		Replies	Views
WebSocket connection to failed（wss） Troubleshooting	0	1423	December 28, 2021
How to fix websocket error? Troubleshooting	12	23361	August 20, 2018
Upgraded from 3.7 to 3.8 broke websockets! help! Troubleshooting	27	5484	May 8, 2017
Many errors in logs- "websocket.NextReader: closing websocket" Troubleshooting	7	1228	December 21, 2022
Mattermost error websocket Troubleshooting	0	781	October 3, 2023

Constant websocket errors

Related topics