I have an instance of gitlab which when I installed, I set up mattermost but didn't use it at the time.Now that I've upgraded gitlab and plan to use it, I run the interactive upgrade but it says I have 0 teams (expected), but I can't do the upgrade because I can't choose any team for the script to keep running.
Please see http://www.mattermost.org/upgrade-to-3-0/ WARNING This upgrade process will be irreversible. Have you performed a database backup? (YES/NO): YES We found 0 teams. Please pick a primary team from the list above:
we have Gitlab Mattermost running here and are very happy with it. Our users only authenticate through Gitlab.
Now, we had to change a user's email address in Gitlab. Unfortunately the one used by Mattermost is still the old one. How can I trigger a sync or change it manually?
I went through the process of enabling mattermost in my gitlab install tonight. I configured it using a url, logged in saw it worked. Then decided that url wasn't great. I changed the url (domain) in /etc/gitlab/gitlab.rb and reconfigured gitlab with gitlab-ctl reconfigure. I then tried to login to mattermost using the new url.
It was redirecting me to a gitlab page saying the redirect url was invalid. After checking settings I decided to deauthorize the application in gitlab for my user and under the admin application settings.
Now when I try to login using a gitlab account I get the following error.
Client authentication failed due to unknown client, no client authentication included, or unsupported authentication method.
I'm try to use my Gitlab Omnibus Mattermost but it's doesn't work at all.
Gitlab and Lattermost are both on a server B, and accessible via server A using an apache reverse proxy.
So both are reachable with there subdomain ( gitlab.mydomain.com and mattermost.mydomain.com ) on port 80 on server A and configure on different ports on server B ( here gitlab on 29280 and mattermost on 29281).
Is there a way to increase the name limitation? When I try to create a channel called "Application Lifecycle Management" it stops after the second space (which is 22 chars, 20 in the URL).
When disabling user/team creation in the System Console, inviting members gives "User creation has been disabled for your team. Please ask your team administrator for details." message. And there's no option to generate an invite link.
Steps to reproduce
Version is 3.3.0, GitLab is at 8.11.2.
Create a team and auth via GitLab
Disable user and team creation
Click the three-dot menu in the team
No team invite link is given. And the above message is displayed when you try to "Invite Member"
No errors of any sort in the log file.
This could honestly be a misconfiguration on my part. But the "Invite Member" message is still off, since user creation shouldn't have to be enabled if you're going via GitLab.
Unless user creation is a process in which a GitLab auth-ed user gets a Mattermost account, in which case user creation should be enabled, but limited to GitLab?
Like I said, could just be a configuration issue on my part.
I've upgraded Gitlab install from source to omnibus. Everything works fine, except for Mattermost integration. I can enter the mattermost website, click on "Click here to sign in.", and then I get redirected to the page below. There are no errors in the browser or in the files /var/log/gitlab/mattermost/mattermost.log and /var/log/gitlab/nginx/gitlab_mattermost_error.log, but also there are no buttons or menu to do.. well... anything. Any idea what is going on? Thank you very much.
Wondering if someone from the GitLab Mattermost community could help update the guide to make things more clear--ideally someone who knows how GitLab admins think and where best to place the information so it'll be noticed.
Is there a way I can manually consolidate database users myself via DB updates since at least in my case all users are GitLab users and I can be sure that we can consolidate everyone.
When Mattermost is installed with GitLab and uses GitLab SSO, I wonder how we could integrate with bots. In my use case, webhooks are no option because the outgoing webhooks are not available for private channels. So I wanted to use a bot that uses the API and therefore should login as a bot user to Mattermost. But that doesn't seem possible when SSO with Gitlab is enabled. Is there something I'm missing?
I've installed GitLab Omnibus CE 8.13.3 and would like to understand the different settings in gitlab.rb for mattermost.
I am trying to change the notifications on GitLab events that gets published to our Mattermost channel, right now the notification is coming from "root" even though we have a different username defined in the outgoing web hook in GitLab.
Where can I find what service_enable_post_username_override means? I'm wondering if this setting is related. Plus I want to understand what all these different settings are.
I'm happily working with Mattermost 3.5.0 (Build Hash: 3f19ccf1b1a6efdcc990cf8a0270ec4ffc0c6e22, Build Date: Tue Nov 15 18:55:53 UTC 2016), which is bundled with the most recent GitLab Omnibus (8.14.1). I've never used the CLI before, so I don't know if it worked in older releases.
Whenever I run the CLI with the -config option, I get the following error (it doesn't matter if i sudo or not):
$ sudo -u mattermost /opt/gitlab/embedded/bin/mattermost -config=/var/opt/gitlab/mattermost/config.json -version
[2016/12/01 14:00:57 CET] [EROR] Failed to load system translations for 'en' attempting to fall back to 'en'
panic: Failed to load system translations for 'en'
goroutine 1 [running]:
panic(0xb5c580, 0xc4204b5af0)
/usr/local/go/src/runtime/panic.go:500 +0x1a1
github.com/mattermost/platform/utils.GetTranslationsBySystemLocale(0x0)
/var/lib/jenkins/jobs/msr/jobs/platform-release/workspace/src/github.com/mattermost/platform/utils/i18n.go:50 +0x374
github.com/mattermost/platform/utils.InitTranslations(0xc4204b55f0, 0xc4204b5600, 0xc4204b5610)
/var/lib/jenkins/jobs/msr/jobs/platform-release/workspace/src/github.com/mattermost/platform/utils/i18n.go:27 +0x54
main.main()
/var/lib/jenkins/jobs/msr/jobs/platform-release/workspace/src/github.com/mattermost/platform/mattermost.go:114 +0xa4
If I run the command without the path to the config file it complains, obviously, it can't find the config file, but at least it doesn't panic:
$ sudo -u mattermost /opt/gitlab/embedded/bin/mattermost -version
[14:02:45 CET 2016/12/01] [EROR] (main.main:107) Unable to load mattermost configuration file: utils.config.load_config.opening.panic
I don't know how Mattermost searches for its translation files, but in my understanding the files are there (again, it doesn't matter if I change the owner of the files):
$ ls -alh /opt/gitlab/embedded/service/mattermost/i18n
total 2.1M
drwxr-xr-x 2 root root 4.0K Nov 28 19:45 .
drwxrwxr-x 7 root root 4.0K Nov 28 19:45 ..
-rw-r--r-- 1 root root 187K Nov 28 17:22 de.json
-rw-r--r-- 1 root root 174K Nov 28 17:22 en.json
-rw-r--r-- 1 root root 190K Nov 28 17:22 es.json
-rw-r--r-- 1 root root 193K Nov 28 17:22 fr.json
-rw-r--r-- 1 root root 207K Nov 28 17:22 ja.json
-rw-r--r-- 1 root root 184K Nov 28 17:22 ko.json
-rw-r--r-- 1 root root 184K Nov 28 17:22 nl.json
-rw-r--r-- 1 root root 185K Nov 28 17:22 pt-BR.json
-rw-r--r-- 1 root root 236K Nov 28 17:22 ru.json
-rw-r--r-- 1 root root 166K Nov 28 17:22 zh_CN.json
-rw-r--r-- 1 root root 168K Nov 28 17:22 zh_TW.json
I've looked at the following issues, but they relate to much older versions of Mattermost and none of them brought up a solution that worked in this case:
forum.mattermost.org/t/mattermost-init-script/2187 (sorry, I'm not allowed to post more than two links)
Steps to reproduce
install most recent GitLab Omnibus (8.14.1) on Ubuntu 14.04.5 LTS
fire the CLI with the path to the config file: sudo -u mattermost /opt/gitlab/embedded/bin/mattermost -config=/var/opt/gitlab/mattermost/config.json -help
EDIT: I forgot to mention, there are no log entries to this error. But just a few moments ago I've found a workaround in forum.mattermost.org/t/solved-how-to-authenticate-bots-using-the-api/2405/2
This is more of a summary of what I did, to help others if need be. I switched from a source installation of mattermost, with Mysql DB, to the packaged version in omnibus-gitlab with the included PostgreSQL DB.
Activate mattermost in gitlab-omnibus and launch reconfigure
Prepare the SQL dump
Dump the MySQL DB: mysqldump --compatible=postgresql --default-character-set=utf8 -r mattermost.mysql -u root mattermost -p --complete-insert
Update the dump to match the PostgreSQL DB schema: Only keep the INSERT INTO commands, convert to lowercase all the column and table names, insert TRUNCATE table_name before each block of INSERT commands if you want to clean the DB.
The tricky part : booleans are stored as int4 in MySQL, and appear as 0 and 1 in the dump, while PostgreSQL expects '0' and '1' for boolean values. You need to edit all the corresponding values. (I wrote a script using https://sqlparse.readthedocs.io to do this.)
Now the cleaned-up dump is ready.
Copy data
You just have to copy the mattermost data folder to /var/opt/gitlab/mattermost/data.
I am trying to get SSO for mattermost from gitlab working in the Omnibus installation. Any ideas on how to troubleshoot would be greatly appreciated.
Setup
I have the Omnibus package installed in an lxc container running Ubuntu 16.04 with traffic from the internet routed through nginx running in another container. I'm terminating the ssl connections in the nginx container where the certs are, and then forwarding traffic to the gitlab lxc container via server configurations for each of my gitlab and mattermost urls.
The Problem
When I click the sign in with gitlab button it takes me to the authorization url, but then when I click authorize, I get:
Token request failed
and in /var/log/gitlab/mattermost/mattermost.log, I get:
[2017/01/13 22:36:08 UTC] [EROR] websocket connect err: websocket: could not find connection header with token 'upgrade' [2017/01/13 22:36:08 UTC] [EROR] /api/v3/users/websocket:connect code=500 rid=ojqur6wyubybmqyhegpptbmwey uid= ip=76.90.41.133, 10.29.248.10 Failed to upgrade websocket connection [details: ] [2017/01/13 22:37:28 UTC] [EROR] SMTP server settings do not appear to be configured properly err=Failed to open connection details=dial tcp :0: getsockopt: connection refused [2017/01/13 22:37:45 UTC] [EROR] /signup/gitlab/complete:AuthorizeOAuthUser code=500 rid=i9eat3i7e7gjjpxddnp168oj9c uid= ip=76.90.41.133, 10.29.248.10 Token request failed [details: Post https://git.calebeverett.io:80/oauth/token: dial tcp 45.79.111.122:80: getsockopt: connection refused]
What is odd to me is that initial request to https://git.calebeverett.io/oauth/authorize was successful.
Right now we use authentication via Gitlab-OAuth-Api which then authenticates against our LDAP. Works perfect.
We now want to be able to use Mattermost from outside the coporate network without "publishing" our Gitlab services. Also we don't want to have seperate user accounts for gitlab and mattermost. Did anyone manage this or could give me some advises/thought about that?
We are currently using the Omnibus-Gitlab package "gitlab-ce-8.15.3-ce" on CentOS 7. Mattermost is running version 3.5.1. Both on the same server.
2017-02-12_02:26:12.82313 [2017/02/11 22:26:12 AST] [CRIT] The database schema version of 2.2.0 cannot be upgraded. You must not skip a version.
2017-02-12_02:26:14.01786 [2017/02/11 22:26:14 AST] [INFO] Loaded system translations for 'en' from '/opt/gitlab/embedded/service/mattermost/i18n/en.json'
2017-02-12_02:26:14.01787 [2017/02/11 22:26:14 AST] [INFO] Current version is 3.5.0 (3.5.0/Tue Nov 15 18:55:53 UTC 2016/3f19ccf1b1a6efdcc990cf8a0270ec4ffc0c6e22/none)
2017-02-12_02:26:14.01787 [2017/02/11 22:26:14 AST] [INFO] Enterprise Enabled: false
2017-02-12_02:26:14.01788 [2017/02/11 22:26:14 AST] [INFO] Current working directory is /opt/gitlab/embedded/service/mattermost
2017-02-12_02:26:14.01788 [2017/02/11 22:26:14 AST] [INFO] Loaded config file from /var/opt/gitlab/mattermost/config.json
2017-02-12_02:26:14.01789 [2017/02/11 22:26:14 AST] [INFO] Server is initializing...
2017-02-12_02:26:14.01789 [2017/02/11 22:26:14 AST] [INFO] Pinging SQL master database
2017-02-12_02:26:14.02038 [2017/02/11 22:26:14 AST] [INFO] Pinging SQL replica-0 database
2017-02-12_02:26:14.02712 [2017/02/11 22:26:14 AST] [CRIT] The database schema version of 2.2.0 cannot be upgraded. You must not skip a version.
Steps to reproduce
Configure /etc/gitlab/gitlab.rb with the following settings:
sudo -u mattermost -i bash
cd /opt/gitlab/embedded/service/mattermost
/opt/gitlab/embedded/bin/mattermost -config='/var/opt/gitlab/mattermost/config.json' -upgrade_db_30
Then I get an error:
Error: unknown shorthand flag: 'u' in -upgrade_db_30
I also want to mention that I do not care about any Mattermost history. It's completely fine if all previous Mattermost data is lost, as I had only briefly tested Mattermost over a year ago. Any help would be greatly appreciated, thanks.
Installed mattermost on my omnibus system, using the instructions here.
The install seems to be fine, ssl all seems okay. When I browse to https://blather.gitlab.mydomain.com, I am redirected to signup_user_complete.
This gives me the "Preview Mode: Email notifications have not been configured" clicky across the top, and Create an account with: GitLab Single-Sign-On
Clicking GitLab Single-Sign-On gives me the oauth/authorize page.
When I click authorize, I'm rewarded with:
GitLab Mattermost needs your help:
Your password must contain at least 5 characters.
Go back to Mattermost
How do I assign this password?
Error Log
[2017/02/15 19:51:54 UTC] [EROR] /signup/gitlab/complete:User.IsValid code=500 rid=887djxpdai88tbdo4e8zzd4xoy uid= ip=XXX.XXX.XXX.XXX Your password must contain at least 5 characters. [details: ]
