-
Notifications
You must be signed in to change notification settings - Fork 6.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Edits fail if internet connection is spotty #24038
Comments
Hi @svenssonaxel ,
|
1. What Mattermost server version and Mattermost desktop app version are you currently on?Server
Desktop app 2. Do you see any errors either in the server logs or in the developer console when the issue happens?The server logs accessible via the web admin UI contains hundreds of errors on the following form:
The The mattermost docker container STDOUT contains similar errors to the above, I assume they are the same. The STDOUT contains lots of output, the latest being:
I'm using mattermost/docker. The nginx log seems to have nothing pertinent in
Also note that I have adjusted the nginx config as follows: diff --git a/nginx/conf.d/default.conf b/nginx/conf.d/default.conf
index d24a624..8263115 100644
--- a/nginx/conf.d/default.conf
+++ b/nginx/conf.d/default.conf
@@ -93,7 +93,7 @@ server {
location ~ /api/v[0-9]+/(users/)?websocket$ {
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
- client_max_body_size 50M;
+ client_max_body_size 10000M;
proxy_set_header Host $http_host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
@@ -102,18 +102,18 @@ server {
proxy_set_header Early-Data $ssl_early_data;
proxy_buffers 256 16k;
proxy_buffer_size 16k;
- client_body_timeout 60;
- send_timeout 300;
- lingering_timeout 5;
+ client_body_timeout 6000;
+ send_timeout 7200;
+ lingering_timeout 60;
proxy_connect_timeout 90;
- proxy_send_timeout 300;
- proxy_read_timeout 90s;
+ proxy_send_timeout 7200;
+ proxy_read_timeout 7200s;
proxy_http_version 1.1;
proxy_pass http://backend;
}
location / {
- client_max_body_size 50M;
+ client_max_body_size 10000M;
proxy_set_header Connection "";
proxy_set_header Host $http_host;
proxy_set_header X-Real-IP $remote_addr;
@@ -123,7 +123,7 @@ server {
proxy_set_header Early-Data $ssl_early_data;
proxy_buffers 256 16k;
proxy_buffer_size 16k;
- proxy_read_timeout 600s;
+ proxy_read_timeout 7200s;
proxy_cache mattermost_cache;
proxy_cache_revalidate on;
proxy_cache_min_uses 2; 3. Do you see the same issue on webapp/browser?Haven't tried that, and unfortunately am no longer able to. |
@svenssonaxel Would you be open to or do you have an ability to upgrade to a more recent version (v7.8 or newer) to see if the issue reproduces on a supported version? v7.1 is currently an unsupported version. |
I'd love to do that, but it's difficult for us to reproduce this very soon, as we no longer have access to the problematic connection. |
Summary
When using the desktop client with a spotty internet connection, edits will fail frequently and silently.
Steps to reproduce
Get on an internet connection with frequent packet drops and failed/dropped connections.
Use the desktop client to type out and then send messages.
Some will succeed and some will fail.
Expected behavior
When sending a message fails, it does so visibly, allowing the user to retry and/or edit.
Observed behavior
When sending a message fails, it does so silently, losing the content of the message.
The text was updated successfully, but these errors were encountered: