ad 1)
OK, when you see it the next time, please write down the time you experienced it, it should contain entries in the mobile app’s logs which we might be able to refer to afterwards.
ad 2)
The server logs are usually available in /opt/mattermost/logs/mattermost.log
, but the directory might be different depending on your installation type, for docker deployments the path is volumes/app/mattermost/logs/mattermost.log
relative to your docker base directory, for the Omnibus setup it’s /var/log/mattermost/mattermost.log
.
ad 3)
Yes, please note down the timestamp when the connection errors happen and once both have happened (the first one and the websocket one), grab the logs for this timeframe and upload them here (or send them to me so I can filter them out for the relevant parts). If only one of the errors happens, let’s tart with this one, don’t need to wait for both of them.
ad 4)
Same here, write down the time when this happens, the mobile app also keeps all the logs, so if we know what to look for in the logs, it might help to find the culprit then.
ad 5)
Also timestamp here please along with the logs.
ad 6)
It should be part of the logs we’re gathering anyways then ideally, but you can also send them to Mattermost directly for the developers to take a look at.
ad 7)
This is a known issue: [MM-51389] - Mattermost