How can I remove Teams from Gitlab Mattermost
This is great, thank you so much for your patient support @BlueAnanas For the record, here is the working command: sudo -u mattermost /opt/gitlab/embedded/bin/mattermost...
View ArticleChanging from HTTP to HTTPS results in ERR_CONNECTION_REFUSED for both...
I tried setting up SSL, but I was having issues because I don't actually have DNS configured yet, I'm just using a HOSTS file locally. I tried reverting back to HTTP, but now I'm getting a 502 Bad...
View ArticleCan I white label mattermost?
In your announcement it says that the compiled versions are released under the MIT, not the source code. According to your license file in the root of the github project, source code is under the AGPL...
View Article[Found workaround]CLI tool still crashing and throwing errors in 2.1.0
Currently best practice to use mattermost 2.1.0 CLI in a GitLab omnibus install: copy en.json from /opt/gitlab/embedded/service/mattermost/i18n/ to /opt/gitlab/embedded/service/mattermost/ make...
View ArticlePUSH-PROXY: how can I turn on logging for the mm-push-proxy?
Hi,got it all working now. Removing the password from the private key did the trick. openssl rsa -in pkey.pem -out newkey.pemWhich raises the question whether this is still a private key ... anyway,...
View ArticleHow should we transition a user to gitlab authentication?
It's your database so feel free to massage it to do whatever you like but our policy is to not suggest making manual changes to your Mattermost database, as a simple mistake could cause major issues...
View ArticleAbout the International category
This top level category is for non-English Mattermost communities to discuss and ask questions about Mattermost within the English-language forum. If you'd like to start a conversation in language not...
View ArticleAbout the Français / French category
Bienvenue sur le forum de Mattermost en Français !
View ArticleBienvenue aux francophones!
Bonjour à tous les francophones, de Belgique, de Suisse, du Luxembourg, de France et d'ailleurs !Ian nous a gentiment ouvert un espace sur le forum de Mattermost où nous pourrons discuter en français...
View ArticleChanging from HTTP to HTTPS results in ERR_CONNECTION_REFUSED for both...
revxx14: Could it be trying to use the same port as my HTTPS-enabled GitLab still? no, mattermost doesn't use any port, it just dies in initialization: revxx14: down: mattermost: 0s, normally up, want...
View Article[Solved] Losing Mattermost settings after GitLab update
The few missing that I had to do manually that were related to webhook enabling and icon and name overriding were in the link you sent so I copied the relevant lines into my gitlab.rb and set them the...
View ArticleSSO using a custom oAuth
I'm in need of a similar feature. We already have our our user DB and user authentication. We would love to integrate with Mattermost for a single-sign-on solution. We could implement an Oauth setup...
View ArticleChanging from HTTP to HTTPS results in ERR_CONNECTION_REFUSED for both...
Thanks much! It's definitely something with the email. I commented out my email settings, ran gitlab-ctl reconfigure and chat is now working again. I'll double check the email settings and see if I...
View ArticleChanging from HTTP to HTTPS results in ERR_CONNECTION_REFUSED for both...
Okay, I've definitely confirmed its something with the mail settings, but I can't figure out what. Everything looks perfectly correct to me, and using the exact same settings via system console sends...
View ArticlePublishing android app?
In the repo it mentions you should deploy with apk instead of the app store-- is there a reason for this?
View ArticleInternational discussions on forum.mattermost.org
Most of the world doesn't speak English as a native language so we're creating some sub-categories for non-English discussion: French Spanish Portuguese German If you'd like any additional languages...
View ArticleChanging from HTTP to HTTPS results in ERR_CONNECTION_REFUSED for both...
revxx14: Password is correct, email is correct, port is correct, domains are correct... Not all combinations of these parameters are considered legal by the go smtp library You'll need a stack trace...
View Article