Ok yes that’s how it looks. This isn’t impacting just me, this is impacting the 4 users using the server. through the last couple days I’ve noticed that it is doing a few weird things:
1.) When you open the iOS app, it will take you to a random position above the current messages
2.) Sometimes the unread indicator inside the app will kind of stick
3.) If I get the unread count to show, i have to close the app to get it to mark as read and then it won’t show the unread count for a while
4.) The unread count indicator doesn’t seem to work on any of the apps - whether it’s on the Mac or iOS
Yes, please. Please provide all the configuration as well as the mattermost.log when you reproduce the issue so we can dig deeper into this issue. Thanks.
I’m not really sure how I can forcibly reproduce it - they just don’t work. I would say maybe 1 out of every 100 messages now, if that, I get the badge number.
I’m looking through the logs and these are the only errors I see:
A little bit on my setup (and, again, this all worked fine before upgrading to version 5.x - the only difference was I was using an Apache proxy but I had this in place still post-upgrade and it was not working with Apache either):
Chat server: CentOS 8, went through the Mattermost Documentation for the setup and didn’t modify anything. SELinux is running.
Proxy Server: CentOS 8, nginx 1.14.1, here’s the conf file for the proxy:
upstream backend {
server 10.20.5.30:8065;
keepalive 32;
}
I’ve made an interesting observation the last few days. If I let maybe 10-12 messages go without reading any of them, THEN it will show the badge count. That seems to be the only way I get to see it is when that happens.
I don’t see anything obvious in the proxy configuration with reference to Configuring NGINX with SSL and HTTP/2 that could impact the badge counter on the iOS app directly. This one is definitely out of the ordinary:
@amy.blais I’ll ping the mobile developers on this to get their insight on what could have impacted the unread counter.
Thanks for the update. Before I share this with the team, can you please provide me with the following information so I can cross check the log entries?
SELECT u.Id, u.Username, u.Email, s.DeviceId, s.Props FROM Users AS u RIGHT JOIN Sessions AS s ON s.UserId = u.Id AND u.Username = "<username>";
That looks a handful. Can you please log out from every session and only log in to the iOS device to reproduce the issue before generating a new notification.log? That will help to narrow down the issue better. Thanks.
Been a little crazy at work and home and just settling down. Ok - should I sign out EVERYONE or just me from all devices? I think I did that not long before I sent that log but I can do this again
{“level”:“error”,“ts”:1587400887.3557847,“caller”:“mlog/log.go:175”,“msg”:“Enter a valid email or username and/or password.”,“path”:“/api/v4/users/login”,“request_id”:“5xnbmf5sgfyoxk1a7rpwarqpcr”,“ip_addr”:“10.10.3.162”,“user_id”:“”,“method”:“POST”,“err_where”:“login”,“http_code”:401,“err_details”:“”}
{“level”:“error”,“ts”:1587400931.431108,“caller”:“mlog/log.go:175”,“msg”:“Enter a valid email or username and/or password.”,“path”:“/api/v4/users/login”,“request_id”:“bxcsicbt8tymfbrbereifobppa”,“ip_addr”:“10.10.3.162”,“user_id”:“”,“method”:“POST”,“err_where”:“login”,“http_code”:401,“err_details”:“”}
{“level”:“error”,“ts”:1587401002.8468738,“caller”:“mlog/log.go:175”,“msg”:“Enter a valid email or username and/or password.”,“path”:“/api/v4/users/login”,“request_id”:“swnmirbykfrupydinosorrix9h”,“ip_addr”:“10.10.3.162”,“user_id”:“”,“method”:“POST”,“err_where”:“login”,“http_code”:401,“err_details”:“”}
{“level”:“error”,“ts”:1587401017.8027334,“caller”:“mlog/log.go:175”,“msg”:“Enter a valid email or username and/or password.”,“path”:“/api/v4/users/login”,“request_id”:“kg6ufdmmxtg39g13naw8jxs1fh”,“ip_addr”:“10.10.3.162”,“user_id”:“”,“method”:“POST”,“err_where”:“login”,“http_code”:401,“err_details”:“”}
{“level”:“error”,“ts”:1587401044.8230484,“caller”:“mlog/log.go:175”,“msg”:“Enter a valid email or username and/or password.”,“path”:“/api/v4/users/login”,“request_id”:“opdrxohr5bbumm639c6jjr5sgo”,“ip_addr”:“205.237.121.1”,“user_id”:“”,“method”:“POST”,“err_where”:“login”,“http_code”:401,“err_details”:“”}
{“level”:“error”,“ts”:1587401055.4120007,“caller”:“mlog/log.go:175”,“msg”:“Enter a valid email or username and/or password.”,“path”:“/api/v4/users/login”,“request_id”:“936riusf378bzgmsj9p9u9wqje”,“ip_addr”:“205.237.121.1”,“user_id”:“”,“method”:“POST”,“err_where”:“login”,“http_code”:401,“err_details”:“”}
And I’m also seeing these:
{“level”:“error”,“ts”:1587711497.1088774,“caller”:“mailservice/mail.go:153”,“msg”:“Failed to open a connection to SMTP server”,“error”:“EOF”}
{“level”:“error”,“ts”:1587711497.10896,“caller”:“app/notification_email.go:103”,“msg”:“Error while sending the email”,“user_email”:“jeremy@domain.one”,“error”:“SendMail: Failed to open TLS connection, EOF”}
The error log you shared only shows the error with the login:
Enter a valid email or username and/or password
However, the last part of the log is the one that catches my attention, the info related to invalid session token. Are you getting that from the mattermost.log or notification.log itself and is the token xyk4yx9xn3rstb3cfcajzdt7wa associated with any of the accounts?
Can you also install the latest 1.30.1 mobile app too? Once done, please go through the Testing push notifications and let me know how it goes.
I don’t think I have the tokens setup really but I can check if you tell me how. I made sure I have the log level set to DEBUG and then I did the troubleshooting process after I signed out of all devices that were not my iPhone. I get the push notification, but the badge indication never shows up. I am on the latest version of the iOS app.