Mattermost marking users "offline" when they are "away"

Troubleshooting
41

Hi @cpc Following up here, has the issue been resolved for you or do you need further assistance? Let me know and I will ask an engineer to take a look!

42

Hi @amy.blais Still have this issue.
With a new server/db installation everything is ok, when i use the old db, the issue comes back again.
I guess the problem is with the old db working with this newer version.

43

Hi @cpc Thank you for letting me know!

We have this ticket open here to investigate issues with online status: https://mattermost.atlassian.net/browse/MM-7569.

I recommend using the new database and also upgrading to the latest server version (v.4.10). Let me know if you have any questions or if there is any other relevant information that you would like to share!

44

Hi there,

I’m facing the same issue with a fresh install (server 5.10.0, desktop app 4.2.1).

Desktop apps are run under MACOS & Windows.

Server is run in a LXC container on a Debian Stretch host, behind a Ngnix proxy. Here’s the conf:

upstream backend {
        server mattermost:8065;
        keepalive 32;
}

proxy_cache_path /var/cache/nginx levels=1:2 keys_zone=mattermost_cache:10m max_size=3g inactive=120m use_temp_path=off;

server {
        listen 80;
        server_name chat;

        access_log  /var/log/nginx/chat.access.log;
        error_log   /var/log/nginx/chat.error.log;

        location ~ /chat/api/v[0-9]+/(users/)?websocket$ {
                proxy_set_header Upgrade $http_upgrade;
                proxy_set_header Connection "upgrade";
                client_max_body_size 50M;
                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;
                proxy_set_header X-Forwarded-Proto $scheme;
                proxy_set_header X-Frame-Options SAMEORIGIN;
                proxy_buffers 256 16k;
                proxy_buffer_size 16k;
                client_body_timeout 60;
                send_timeout 300;
                lingering_timeout 5;
                proxy_connect_timeout 90;
                proxy_send_timeout 300;
                proxy_read_timeout 90s;
                proxy_pass http://backend;
        }

        location /chat/ {
                client_max_body_size 50M;
                proxy_set_header Connection "";
                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;
                proxy_set_header X-Forwarded-Proto $scheme;
                proxy_set_header X-Frame-Options SAMEORIGIN;
                proxy_buffers 256 16k;
                proxy_buffer_size 16k;
                proxy_read_timeout 600s;
                proxy_cache mattermost_cache;
                proxy_cache_revalidate on;
                proxy_cache_min_uses 2;
                proxy_cache_use_stale timeout;
                proxy_cache_lock on;
                proxy_http_version 1.1;
                proxy_pass http://backend;
        }
}

This proxy itself is behind another Nginx proxy with the following conf:

        location /chat/ {
                proxy_pass      http://chat/chat/;
                proxy_set_header Upgrade $http_upgrade;
                proxy_set_header Connection "upgrade";
                client_max_body_size 50M;
                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;
                proxy_set_header X-Forwarded-Proto $scheme;
                proxy_set_header X-Frame-Options SAMEORIGIN;
                proxy_buffers 256 16k;
                proxy_buffer_size 16k;
                client_body_timeout 60;
                send_timeout 300;
                lingering_timeout 5;
                proxy_connect_timeout 90;
                proxy_send_timeout 300;
                proxy_read_timeout 90s;
        }