Hi @rakeshbalguri,
Feedback from one of our community members: the issue seems to be that 127.0.0.1 inside any Docker container is different from 127.0.0.1 outside that container. In other words, the DB server reachable on Windows’ 127.0.0.1 is unreachable from within the Mattermost Docker container. (You need to use a different listen address for your DB server.)
Hi @Sandmonster,
From one of our community members: That option is called --hidden - please see pr-desktop-571.
@x0nn, Also feedback from one our community members: Any particular reason you are using an old release candidate ( v5.5.0-rc1 )? Also, you can increase the verbosity of the Mattermost logging to debug (via system console).
Hi @larvel, would you be open to joining our Matterpoll channel and pinging Hanzei (he is the maintainer of the Matterpoll plugin)?
Hi @ChristopherBrand, I can reproduce this and it does explain why users might click the wrong channel. I think this is meant to be expected behaviour (I mean the fact that the sidebar will scroll as the channels move away from the unread list as they are viewed), but I will ask our UX team if the experience here could be improved.
Hi,
I did reach out to @Hanzei. We agreed that this is not a problem with the plugin itself, but rather a general one.
How would you activate a plugin using environment variables?
Here is what we have tried: (in docker-compose.yml)
- MM_PLUGINSETTINGS_PLUGINS: |
“com.github.matterpoll.matterpoll”: {
“Enable”: true
}
- MM_PLUGINSETTINGS_PLUGINSTATES="{“com.github.matterpoll.matterpoll”:{“Enable”:true}}"
- MM_PLUGINSETTINGS_PLUGINSTATES_COM.GITHUB.MATTERPOLL.MATTERPOLL_ENABLE=true
- MM_PLUGINSETTINGS_PLUGINSTATES_COM_GITHUB_MATTERPOLL_MATTERPOLL_ENABLE=trueThe formatting was not good. What you see is four different attempts to try and set the plugin as activated upon start.
the prieview docker server requires default login credentials
so what is the default username and password?
Hi there!
I out company we have changed TFA method on our SSO service (ADFS) to AzureMFA.
And there is an issue on Mattermost classic mobile app for iOS - app refused to login if user going to approve OTP, but only in case if MM apps go to background. In this case login screen appears again after approval.
Is this any possibility to fix it?
Can you help with a link to the content where you read this? This way I’ll have the full context and I can help you out more efficiently.
Hi @dimych,
Can you help with more details on your environment, config settings and any errors that you see (please see this page for reference: https://docs.mattermost.com/process/support.html#general-questions-for-any-issues)? Also, can you help with step-by-step reproduction steps?
Also, the classic app is an older version of our mobile apps, and I strongly recommend taking a look at our newer version of our mobile apps: https://itunes.apple.com/us/app/mattermost/id1257222717?mt=8.
Hi @amy.blais,
Our set-up is:
Steps:
There is no any problems with modern ios mobile app on this moment
I have read it on this page: https://mattermost.com/download/
I did it by running the following command:
docker run --name mattermost-preview -d --publish 8065:8065 mattermost/mattermost-preview
*its running on a vps
The Enterprise Edition LDAP group sync feature has been in active development for a couple of months and we are excited to be releasing our alpha version this week. This feature automates user onboarding by allowing customers to set default team and channel membership based on LDAP groups. This is useful if you have a large amount of users to onboard at one time, or if you onboard users frequently. We expect a beta version to be available in Mattermost v5.8.
What does the alpha release entail?
An alpha release allows customers to test the feature in their staging environments and ensure the feature works with different varieties of LDAP systems and group structures including nested groups. It also allows us to get feedback on the functionality and user experience prior to releasing in beta.
Contributing to alpha testing
The alpha release will be available to E20 customers as a custom build. We are looking for customers that are open to work closely with us and provide feedback about their LDAP system and group structure, performance, and their deployment environment. If you have interest in testing, accessing the feature early, and working closely with our product development team in future enhancements to this feature, please reach out to Katie Wiersgalla, Product Manager for the feature, on community.mattermost.com or via email at katie[at]mattermost.com.
Roadmap for Group Sync Feature
The LDAP group sync is the first phase of a larger Group feature. Later phases for groups are currently planned to include:
Phase 2:
Phase 3:
Phase 4:
Great. Will this feature also be available for E10?
Hi @mohsensalahshoor, do you have docker set up? If not, you’ll first need to set up Docker using one of the install guides you’ll find below the command.
Hi @amy.blais
I have docker set up, and the container gets up and running, but when I open mattermost by this url:
http://46.4.152.185:8065/
I get the login page, but I don’t know what is the default username and password
Thank you for your interest in this feature @JtheBAB .
At this time, the ability to sync LDAP with Groups will be an E20 feature. We are planning on releasing functionality listed in Phase 2 to E10 customers targeting early 2019.
I’m trying to install mattermost on Centos 7 using postgresql
I’m getting an error message when testing the mattermost server sudo -u mattermost ./bin/mattermost
err=pq: no pg_hba.conf entry for host “\ user “mmuser”, database “mattermost”, SSL off”}
Ive followed all the instruction here to this point including editng the hba.conf and config.json files
Server consistently shut down with SIGSEGV when triggering a specific webook.
Mattermost 5.4.0
Successful webhook post, or error in log
Several attempts to post messages via the webhook failed because the destination hostname could not be resolved. Those errors were visible in the log.
After that, there was nothing else in the log immediately prior to the event. Presumably another trigger word was encountered, and then we saw:
Dec 14 03:23:57 syalv085.trading.imc.intra start-mattermost.sh[114318]: panic: runtime error: invalid memory address or nil pointer dereference
Dec 14 03:23:57 syalv085.trading.imc.intra start-mattermost.sh[114318]: [signal SIGSEGV: segmentation violation code=0x1 addr=0x38 pc=0xeb8acd]
Dec 14 03:23:57 syalv085.trading.imc.intra start-mattermost.sh[114318]: goroutine 50655814 [running]:
Dec 14 03:23:57 syalv085.trading.imc.intra start-mattermost.sh[114318]: github.com/mattermost/mattermost-server/app.(*App).TriggerWebhook.func1.1()
Dec 14 03:23:57 syalv085.trading.imc.intra start-mattermost.sh[114318]: /home/ubuntu/jenkins/workspace/msr/mattermost-platform-release/src/github.com/mattermost/mattermost-server/app/webhook.go:108 +0xfd
Dec 14 03:23:57 syalv085.trading.imc.intra start-mattermost.sh[114318]: github.com/mattermost/mattermost-server/app.(*App).Go.func1(0xc00f3e18b0, 0xc000100580)
Dec 14 03:23:57 syalv085.trading.imc.intra start-mattermost.sh[114318]: /home/ubuntu/jenkins/workspace/msr/mattermost-platform-release/src/github.com/mattermost/mattermost-server/app/app.go:505 +0x27
Dec 14 03:23:57 syalv085.trading.imc.intra start-mattermost.sh[114318]: created by github.com/mattermost/mattermost-server/app.(*App).Go
Dec 14 03:23:57 syalv085.trading.imc.intra start-mattermost.sh[114318]: /home/ubuntu/jenkins/workspace/msr/mattermost-platform-release/src/github.com/mattermost/mattermost-server/app/app.go:504 +0x52
This crash was repeated a further two times.