[Mattermost] Chat group discussion

Here is the solution to this Mattermost installation problem : admin password should only be made with alphanumeric

To follow up on this issue, if there is a `‘’ character in the password, the logging helper isn’t happy…

/usr/share/yunohost/helpers.d/logging: eval: line 145: unexpected EOF while looking for matching `''

@AntoineC salut, pourrais-tu me dire si tu arrive à activer des plugins. j’ai installé mattermost sur freebox et je pense que la carte ARM64 fait que les plugins sont impossible à activer ?. je te remercie.

@AntoineC hi, could you tell me if you manage to activate plugins. i installed mattermost on freebox and i think the ARM64 board makes plugins impossible to activate ?. I thank you.

Thank you so much @kemenaran for the last update which fix the links previews in mattermost. So nice ! <3

1 Like

@kemenaran many thanks for this app package:I managed to keep my family in contact during the pandemic and it really made our lives more bearable!!
Now I have hit a problem:
I cannot login to my mattermost via browser or via desktop and get this error message:

Your session has expired. Please log in again.

I have tried to follow solutions from mattermost forum but I cannot make it work at all. I have only an iOS logged in that is working OK.
Any help is very welcome …

Err – hmm, I don’t really know. So an existing app is still logged in fine (the iOS app), but you cannot log in using the website.

This feel a very generic error, and I don’t know where to start. In the Yunohost Tools > Services panel, there’s a Mattermost service than can give you some logs (and the Mattermost’s System Console can even increase the log level if needed). Do you see anything suspicious there when you try to log in?

these are last entries in the log:

{"timestamp":"2023-05-01 15:16:38.092 +01:00","level":"info","msg":"Server is listening on [::]:8065","caller":"app/server.go:952","address":"[::]:8065"}
{"timestamp":"2023-05-01 15:16:38.092 +01:00","level":"info","msg":"Sending systemd READY notification.","caller":"commands/server.go:130"}
{"timestamp":"2023-05-01 15:19:23.566 +01:00","level":"info","msg":"Post.Message has size restrictions","caller":"sqlstore/post_store.go:2516","max_characters":16383,"max_bytes":65535}
{"timestamp":"2023-05-01 15:19:23.777 +01:00","level":"info","msg":"api endpoint requires a license","caller":"web/context.go:115","path":"/mattermost/api/v4/users/rwkk9ccx5id4x8edx8mapzqk9r/groups","request_id":"7s6sz6ixzigyjj5detakxp6yih","ip_addr":"127.0.0.1","user_id":"rwkk9ccx5id4x8edx8mapzqk9r","method":"GET","err_where":"","http_code":501,"error":": api endpoint requires a license"}
{"timestamp":"2023-05-01 15:19:48.238 +01:00","level":"info","msg":"api endpoint requires a license","caller":"web/context.go:115","path":"/mattermost/api/v4/groups","request_id":"uz754u7esbngxe8znz9qxkiasr","ip_addr":"127.0.0.1","user_id":"nksbpyo6z3y18n7qdq96tcamfh","method":"GET","err_where":"","http_code":501,"error":": api endpoint requires a license"}
{"timestamp":"2023-05-01 15:27:41.183 +01:00","level":"info","msg":"SimpleWorker: Job is complete","caller":"jobs/base_workers.go:96","worker":"ExpiryNotify","job_id":"5tfq6gp76trrzxbkxhtaguiw4y"}

Here is last entries in /var/log/mattermost/mattermost.log:

{"timestamp":"2023-05-01 17:13:02.830 +01:00","level":"info","msg":"api endpoint requires a license","caller":"web/context.go:115","path":"/mattermost/api/v4/users/aph45eyjkfnndr5nx54x9sdayw/groups","request_id":"m3szn3pmki88ifyacfq8iekeyy","ip_addr":"127.0.0.1","user_id":"aph45eyjkfnndr5nx54x9sdayw","method":"GET","err_where":"","http_code":501,"error":": api endpoint requires a license"}
{"timestamp":"2023-05-01 17:16:58.503 +01:00","level":"info","msg":"api endpoint requires a license","caller":"web/context.go:115","path":"/mattermost/api/v4/users/rwkk9ccx5id4x8edx8mapzqk9r/groups","request_id":"w7u4dr8k4jbx7edc36aau6b91o","ip_addr":"127.0.0.1","user_id":"rwkk9ccx5id4x8edx8mapzqk9r","method":"GET","err_where":"","http_code":501,"error":": api endpoint requires a license"}
{"timestamp":"2023-05-01 17:17:32.109 +01:00","level":"warn","msg":"Error while creating session for user access token","caller":"app/session.go:90","error":"createSessionForUserAccessToken: Invalid or missing token., resource: UserAccessToken id: token=o1n69jq8s3dfp885qknppshx9h"}
{"timestamp":"2023-05-01 17:17:32.272 +01:00","level":"info","msg":"api endpoint requires a license","caller":"web/context.go:115","path":"/mattermost/api/v4/users/rwkk9ccx5id4x8edx8mapzqk9r/groups","request_id":"m9mmg1y37irempuhrpkharaf4e","ip_addr":"127.0.0.1","user_id":"rwkk9ccx5id4x8edx8mapzqk9r","method":"GET","err_where":"","http_code":501,"error":": api endpoint requires a license"}
{"timestamp":"2023-05-01 17:22:16.201 +01:00","level":"info","msg":"SimpleWorker: Job is complete","caller":"jobs/base_workers.go:96","worker":"ExpiryNotify","job_id":"fbwu1nmhnbfc9xrw4f1txje6th"}
{"timestamp":"2023-05-01 17:33:16.291 +01:00","level":"info","msg":"SimpleWorker: Job is complete","caller":"jobs/base_workers.go:96","worker":"ExpiryNotify","job_id":"a8upxw6nc3fp3d6ou3k7ssgmpw"}
{"timestamp":"2023-05-01 17:33:49.609 +01:00","level":"info","msg":"api endpoint requires a license","caller":"web/context.go:115","path":"/mattermost/api/v4/users/rwkk9ccx5id4x8edx8mapzqk9r/groups","request_id":"qyyuerpccirttkym9d5b6buw5e","ip_addr":"127.0.0.1","user_id":"rwkk9ccx5id4x8edx8mapzqk9r","method":"GET","err_where":"","http_code":501,"error":": api endpoint requires a license"}
{"timestamp":"2023-05-01 17:34:17.072 +01:00","level":"info","msg":"api endpoint requires a license","caller":"web/context.go:115","path":"/mattermost/api/v4/groups","request_id":"zspi3km3o7y7jykeuzhr5yrj6c","ip_addr":"127.0.0.1","user_id":"rwkk9ccx5id4x8edx8mapzqk9r","method":"GET","err_where":"","http_code":501,"error":": api endpoint requires a license"}

@kemenaran do you think that the log entry gives you more info to look for error?

Er, not really.

I think the “API endpoint require a license” are not relevant (they pop up even on normal installations). That said, which edition of Mattermost is currently installed? Did it switch maybe from Entreprise edition to Team edition? (I don’t see why that would happened, or why it would cause this issue, but I don’t have any other clues).

Thanks for trying to help …
I have solved it but I have not enough knowledge to explain why it went away.
I read lot about the issue in MM forums and decided to change LengthOfSession from 720 hr to a year 8760 hrs. and suddenly it allowed me to login without the error message.
Maybe this will help somebody in a yesrs time :interrobang::interrobang:Thanks.
PS: one of the big issues is that Yunohost uses completely different directory structure for appps compared to installing directly to Debian. I spent hours trying to find the config files in yunohost after reading MM documentation giving instructions how to modify those config files!!

Please avoid opening multiple posts on the same issue.

Hi everyone,

I recently wanted to install Mattermost in order to use the Playbook feature for my little business. Then I discovered recent changes in the pricing policy of Mattermost, already notified here.

In short :

  • :money_with_wings: Mattermost put previously free features behind paywalls (group calls and playbooks)
  • :no_entry_sign: Mattermost hard-encoded a number limit to users and messages

Well, in my situation, I won’t engage with a software that might loose accessible features in the future. I have the feeling Mattermost is turning back the open-source community and willing to prior cash flow over users interest. As a self-employed worker, I need to have control over my working tools and I can’t afford investing in a software that may lure me with useful features then blackmail me on these. :imp:

I discovered that Framasoft already forked Mattermost to remove the encoded user and messages limit : Framasoft / Framateam / Mostlymatter · GitLab
It may be a platform to welcome the open-source contributors disappointed by the new Mattermost policy.

I think that as a FOSS project, YuNoHost also has a role and could take position : do we want to support the new Mattermost policy, or do we want to promote a more ethic alternative ?
Or in other words : is it time to switch from Mattermost to Mostlymatter (or any other FOSS fork that may appear) ?

More info :

I agree, YunoHost has a role as a FOSS project, but you also have a role as user that wants to promote FOSS projects, you can start mostlymatte_ynh package so that everyone can enjoy free software :sweat_smile:

1 Like

Hi @ericg , of course I could do that, despite I’m not the most qualified, I try when I can to contribute to the code. I also make a yearly donation. Building a new package, especially for a big app like mattermost is still a terrifying challenge to me :sweat_smile:

Well in terms of work charge, my suggestion would not be to support both mattermost and mostlymatter (or any fork), but to switch from mattermost to the other.

Still I put it at discussion, because the risks of useless work are real :

  • finally Mattermost policy could change backwards and come back to the previous situation
  • the open-source community could continue to work on Mattermost despite of the policy, and the forks don’t get the community attention
  • the development of the FOSS fork may be too slow compared to classic Mattermost and users get disappointed with the fork
  • etc.