↧
Managing members in the any team available any team member
↧
HipChat Importation
The error message may not be in the file. I’ve noticed that during the import, MatterMost will compare the users listed in the .jsonl file with the users listing in the database. The issue may actually be the password of the user stored in the database itself.
↧
↧
Mattermost Recipe: Encrypting Internal Traffic
Thanks buddy, nicely explained working fine as of now. 
Regards,
Smith
↧
[solved] Not listening to IPv6 connections
Summary
Apparently MM is only working for IPv4 connections, and not IPv6
Steps to reproduce
Install Omnibus Gitlab on an IPv6 enabled host, enable included GitLab Mattermost
Found out today, while I wasn’t able to use MM at the office I had no issues in using it from home. Then I was testing Webhooks from server and I was getting 404 errors, while from my PC they were working fine. Digging a little bit into the response I found out it was being generated by GL, and not by MM!
While GL is perfectly working on IPv6 it seems that the GL Mattermost enabled hostname is not.
The only doubt I have is that MM has 127.0.0.1:8065 as Listen address. Should it be just :8065?
Installed version: 5.5 (GL 11.6.3)
Thanks
↧
[solved] Not listening to IPv6 connections
Found it!!
Add in /etc/gitlab/gitlab.rb:
mattermost_nginx['listen_addresses'] = ['*','[::]']
Now MM correctly listens to IPv6!
↧
↧
Managing members in the any team available any team member
Hi @0xSheff,
I believe currently the only way to do that is if you have Advanced Permissions enabled (it is an E10 and E20 feature) - more information here: https://docs.mattermost.com/deployment/advanced-permissions.html#system-scheme-e10.
↧
Managing members in the any team available any team member
I think this is a bug, isn’t it? According to the documentation only Team Admins and System Admins can manage members. (https://docs.mattermost.com/help/getting-started/managing-members.html)
↧
Managing members in the any team available any team member
Hi @0xSheff,
The “Manage Members” link on your screenshot is different from the “Manage Members link” under Main Menu > Manage Members. The one on your screenshot is specific to channels which is accessible to all users, and the one under Main Menu > Manage Members is specific to Teams and is accessible to Team Admins and System Admins (which the document is referring to). Does this help clarify things? Let me know if I can help clarify it further!
↧
HipChat Importation
Hello,
all import worked fine when I did a fresh ire-install Mattermost (without ttracks of my previous experiments) - private rooms data was loaded successfully.
But notice: to display data in the UI I had to consistently add users to team and channel both from CLI.
Thank you very much for your help!
Sincerely,
Sergiy.
↧
↧
HipChat Importation
I have a similar problem to @Sergiy (the answers already cleared it up mostly) that on import, users who have sent messages in the imported team/channel are not members. I also cant figure out how to edit the import of the team or channel to automatically add the users to that channel.
I had a few problems with this as when I added a new team called “all” and tried to enter it after adding myself to that team, mattermost was trying to redirect me to “all”'s “townsquare” constantly but this resulted in looping rejections as I was not a member of “all”'s “townsquare” channel yet. I ended up having to use the command line tools to add an additional public team called “Aa” (I had a theory I was being redirected to “all” townsquare as it was alphabetically the first team I was in) and add myself to it’s townsquare, as even when I added myself to “all” I was still rejected til I was able to get Mattermost to redirect me somewhere else. After that I was able to enter “all” fine. All the same, it would be nice to be able to add users to channels and teams automatically on import (especially adding them to the townsquare automatically!) to avoid this problem, so if anyone can direct me as to what to edit in the json files or add to them, itd be a great help.
↧
Managing members in the any team available any team member
Maaaybe you are right, this is different links. But how do you think, the fact that any member can remove someone from any chat – this is good idea at all? This is a basic delineation of access rights, this should be prohibited to members.
Also, when someone does this, it’s not clear who did it. 
↧
Push notifications sometimes does not arrive (Mobile App / Android)
Dear Forum,
we are using mattermost team with a local setup.
Issue:
Using Mattermost mobile client (Android) notifications sometimes does not arrive if multiple messages are sent at once.
As this issue is really painful to us any support here would be appreciated. Maybe there is also a work around?
Best regards
Daniel.
↧
Push notifications sometimes does not arrive (Mobile App / Android)
Hi @Spreenaut,
Both Google and Apple have rate limits on push notifications that limit repeated messages like this, and each have their own criteria for limiting them. When there is a failed push notification to a device Mattermost also removes the DeviceId from that session so that there aren’t multiple push requests sent, which will cause Apple and Google to blacklist Mattermost push notifications. So the push notification system appears to be working as written. There was another report on this recently and this feedback has been passed along to the product team to consider a possible workaround.
↧
↧
Managing members in the any team available any team member
Hi @0xSheff,
Restricting that permission can be done with Advanced Permissions (E10 and E20 feature) - I posted a link to the document with more details on one of my previous messages.
Also, I have passed along your feedback on the System message ("[user] was removed from the channel") to our UX team.
↧
Managing members in the any team available any team member
Alright, thank you. We aren’t planning to take E10 and E20 at the moment. But if the devs think it’s normal and that ordinary members may have administrative powers, then at least make sense to show who deleted the user in that system message
↧
Restoring config.json fails
@arnuschky, can you clarify this point? How is your server successfully starting up (and connecting to the database) if the config.json is removed altogether? May I assume some kind of environment variables at play?
↧
Restoring config.json fails
Sorry that was nonsense. What I did (I think) was: I removed config.json and then did a gitlab-reconfigure, which re-writes config.json with the correct base values (like db connection etc). I suspect gitlab does this only on the first install and doesn’t touch the config file afterwards. Or maybe it sets some env vars, I am not 100% how MM is integrated into gitlab.
What remains is that copying a config file from the same MM version, same gitlab version, from another install, doesn’t work.
I can test this again if necessary.
↧
↧
Restoring config.json fails
Got it: it might be useful to diff the copied config file with the auto-generated one.
There shouldn’t be anything OS dependent in the configuration file. The error you’re seeing is supposed to signal that the file is not valid JSON and that the error occurred at the start of the file (or perhaps that the file was completely empty).
↧
Configuration options switch back when press save button
The issue is not solved. Mattermost team + kubernetes. No console errors.
k8s 1.13.1-do.2
Mattermost from helm repo
mattermost/mattermost-team-edition 5.6.2
log:
{“level”:“info”,“ts”:1547070795.952318,“caller”:“utils/i18n.go:78”,“msg”:“Loaded system translations for ‘en’ from ‘/mattermost/i18n/en.json’”}
{“level”:“info”,“ts”:1547070795.9571805,“caller”:“app/app.go:143”,“msg”:“Server is initializing…”}
{“level”:“info”,“ts”:1547070795.9600437,“caller”:“sqlstore/supplier.go:207”,“msg”:“Pinging SQL master database”}
{“level”:“info”,“ts”:1547070797.0999415,“caller”:“commands/server.go:82”,“msg”:“Current version is 5.6.0 (5.6.2/Sat Dec 22 14:58:39 UTC 2018/3aed6efc6bb5a67fdb8237aac38d46fab3266e8d/2c2d33b22b4c2938938eade4b9914748c1be9d3b)”}
{“level”:“info”,“ts”:1547070797.1000738,“caller”:“commands/server.go:83”,“msg”:“Enterprise Enabled: true”}
{“level”:“info”,“ts”:1547070797.1000998,“caller”:“commands/server.go:84”,“msg”:“Current working directory is /mattermost”}
{“level”:“info”,“ts”:1547070797.100166,“caller”:“commands/server.go:85”,“msg”:“Loaded config file from /mattermost/config/config.json”}
{“level”:“info”,“ts”:1547070797.1019926,“caller”:“filesstore/localstore.go:33”,“msg”:“Able to write files to local storage.”}
{“level”:“info”,“ts”:1547070797.1042979,“caller”:“app/license.go:44”,“msg”:“License key from https://mattermost.com required to unlock enterprise features.”}
{“level”:“info”,“ts”:1547070797.105763,“caller”:“app/plugin.go:130”,“msg”:“Starting up plugins”}
{“level”:“info”,“ts”:1547070798.4837222,“caller”:“app/server.go:168”,“msg”:“Starting Server…”}
{“level”:“info”,“ts”:1547070798.4852965,“caller”:“app/server.go:228”,“msg”:“Server is listening on [::]:8065”}
{“level”:“info”,“ts”:1547070798.5024097,“caller”:“app/web_hub.go:75”,“msg”:“Starting 2 websocket hubs”}
{“level”:“info”,“ts”:1547070798.5099773,“caller”:“sqlstore/post_store.go:1286”,“msg”:“Post.Message supports at most 16383 characters (65535 bytes)”}
{“level”:“info”,“ts”:1547070798.585491,“caller”:“jobs/workers.go:68”,“msg”:“Starting workers”}
{“level”:“info”,“ts”:1547070798.5873446,“caller”:“jobs/schedulers.go:72”,“msg”:“Starting schedulers.”}
{“level”:“error”,“ts”:1547070938.6159284,“caller”:“web/context.go:60”,“msg”:“Login failed because of invalid password”,“path”:"/api/v4/users/login",“request_id”:“54fkgnd617rn5yt8nfo1d4m94e”,“ip_addr”:“10.135.7.143”,“user_id”:"",“method”:“POST”,“err_where”:“checkUserPassword”,“http_code”:401,“err_details”:“user_id=xx1c7o4bwbg3frenurojisx9mc”}
↧
Restoring config.json fails
It wasn’t, I checked that. It looked completely sane. I also ran it through a JSON linter; it passed without errors. So the error MM is showing is either bogus or it fails to read the file for some unknown reason.
↧