@kyryus wrote:

Hello everyone,

I am using gitlab and mattermost behind reverse proxy on same domain and same server (as I use omnibus installation).

When I try to make the link between mattermost and gitlab by creating a team on the mattermost startup screen, I am redirected to Gitlab to validate the application but I have this error : The redirect URI included is not valid.

When I check the url, I can see that there is http instead of https : https://git.domain.com/oauth/authorize?response_type=code&client_id=xxxxxx&redirect_uri=http%3A%2F%2Fmat.domain.com%2Fsignup%2Fgitlab%2Fcomplete&state=yyyyyyyyy

How can I change http to https in the redirect_uri parameter ? When I change it manually, Gitlab seems to detect mattermost.

Here is my gitlab.rb : external_url 'https://git.domain.com'

....
nginx['listen_port'] = 80
nginx['listen_https'] = false
....
mattermost_external_url 'https://mat.domain.com'
mattermost_nginx['listen_port'] = 80
mattermost_nginx['listen_https'] = false

Thank you in advance for your help

Posts: 1

Participants: 1

Read full topic

@it33 wrote:

While GitLab omnibus is set up to manage Mattermost via the gitlab.rb file and a custom layout of Mattermost files, some community members want more control by using the Mattermost CLI tool, which requires additional configuration steps because of the GitLab omnibus layout.

This request is to ask help from the community to make a merge request to document the additional steps in the GitLab Mattermost Admin Guide, which can be verified by the GitLab omnibus team and included in a future release.

There is a GitLab issue posted on this as well.

Posts: 1

Participants: 1

Read full topic

@fircx wrote:

Hey guys.
I don't remember from which version I started using gitlab but mattermost wasn't not included back than, so I decided to install new gitlab omnibus on a different server and than integrate with my existing gitlab. I did and It works fine, but when I try authorize mattermost I get 404 from gitlab.

mattermost.png1207x378 17.3 KB

this is the error:

Started POST "/oauth/authorize" for 127.0.0.1 at 2016-05-07 21:51:24 +0400
Processing by Oauth::AuthorizationsController#create as HTML
Parameters: {"utf8"=>"✓", "authenticity_token"=>"[FILTERED]", "client_id"=>"84c196d399b550d69ff147bb424a287f665768c6e4a6f6cd2f96cdf7815d9146", "redirect_uri"=>"http://url/signup/gitlab/complete", "state"=>"eyJhY3Rpb24iOiJzaWdudXAiLCJoYXNoIjoiJDJhJDEwJGFKdlp3Z3Bpdi5GdndtU1ZxSXhpdHVFMGV2SzhCbzBwVzVGeTJFQzhLSXVyQ21ZZU1KeWI2IiwidGVhbSI6InFhcnZhMDEyMzQ1Njc4OTEwMTExMjEzMTQxNTE2MTcxODE5MjAyMTIyMjMyNDI1MjYyNyJ9", "response_type"=>"code", "scope"=>"api", "commit"=>"Authorize"}
Redirected to http://url/signup/gitlab/complete?code=2b47d406beec1cca4332a9611a148be53a3662f2e411392ae608642ee03c46e5&state=eyJhY3Rpb24iOiJzaWdudXAiLCJoYXNoIjoiJDJhJDEwJGFKdlp3Z3Bpdi5GdndtU1ZxSXhpdHVFMGV2SzhCbzBwVzVGeTJFQzhLSXVyQ21ZZU1KeWI2IiwidGVhbSI6InFhcnZhMDEyMzQ1Njc4OTEwMTExMjEzMTQxNTE2MTcxODE5MjAyMTIyMjMyNDI1MjYyNyJ9
Completed 302 Found in 77ms (ActiveRecord: 67.0ms)
Started GET "/signup/gitlab/complete?code=[FILTERED]&state=eyJhY3Rpb24iOiJzaWdudXAiLCJoYXNoIjoiJDJhJDEwJGFKdlp3Z3Bpdi5GdndtU1ZxSXhpdHVFMGV2SzhCbzBwVzVGeTJFQzhLSXVyQ21ZZU1KeWI2IiwidGVhbSI6InFhcnZhMDEyMzQ1Njc4OTEwMTExMjEzMTQxNTE2MTcxODE5MjAyMTIyMjMyNDI1MjYyNyJ9" for 127.0.0.1 at 2016-05-07 21:51:24 +0400
Processing by NamespacesController#show as HTML
Parameters: {"code"=>"[FILTERED]", "state"=>"eyJhY3Rpb24iOiJzaWdudXAiLCJoYXNoIjoiJDJhJDEwJGFKdlp3Z3Bpdi5GdndtU1ZxSXhpdHVFMGV2SzhCbzBwVzVGeTJFQzhLSXVyQ21ZZU1KeWI2IiwidGVhbSI6InFhcnZhMDEyMzQ1Njc4OTEwMTExMjEzMTQxNTE2MTcxODE5MjAyMTIyMjMyNDI1MjYyNyJ9", "id"=>"signup/gitlab/complete"}
Completed 404 Not Found in 48ms (Views: 0.9ms | ActiveRecord: 2.4ms)

Gitlab version is 8.7.0 and mattermost gitlab 8.7.3

this is mattermost config:

`mattermost_external_url 'http://mattermost.url'

Tell GitLab Mattermost to integrate with gitlab.example.com

mattermost['gitlab_enable'] = true
mattermost['gitlab_secret'] = "secret"
mattermost['gitlab_id'] = "id"
mattermost['gitlab_scope'] = ""
mattermost['gitlab_auth_endpoint'] = "http://gitlab/oauth/authorize"
mattermost['gitlab_token_endpoint'] = "http://gitlab/oauth/token"
mattermost['gitlab_user_api_endpoint'] = "http://gitlab/api/v3/user"

Shut down GitLab services on the Mattermost server

gitlab_rails['enable'] = false
`

Posts: 1

Participants: 1

Read full topic

@wpostma wrote:

I would like all GitLab CI failures to be posted to a team room on mattermost.

How can I do that? Do I need this integration thing to be set up? I have mattermost and gitlab running on my own private host. I have a chat project and chat rooms set up. Right now there is zero links between Gitlab and Mattermost.

Besides CI activity, I can imagine that people creating Forks, and pushing to repos might also be cool to see in Mattermost.

We don't use the Gitlab bug trackers yet, but if we did, I'm sure we'd like to see that too.

W

Posts: 3

Participants: 2

Read full topic

@pacheung wrote:

Hello,

I am evaluating Mattermost team edition and have made several attempts to integrate my on-AWS mattermost server with Gitlab SSO integration but still failed.
I have followed the instructions on http://docs.mattermost.com/deployment/sso-gitlab.html with gitlab.com account and also AWS hosted Gitlab powered by Bitnami but still cannot find the successful way to integrate. Any hints?

Thanks
Patrick

Posts: 1

Participants: 1

Read full topic

@rsokoll wrote:

Hi,

maybe this is the most stupid question for this week/month:
How should the mattermost start page look like? I have the feeling that mine is not correct, as there is no real login form, see screenshot.
Latest gitlab omnibus, mattermost on the same server.

Bildschirmfoto 2016-05-27 um 09.51.31.png874x726 39.5 KB

Thank you,

Rainer

Posts: 2

Participants: 2

Read full topic

@rsokoll wrote:

Hi,

latest version of mattermost shipped with gitlab is v2.2.0, while upstream mattermost is v3.0.3.
Since the mobile clients expect v3, there is no way to connect to gitlab-mattermost with a smart phone.

Is there a roadmap for bundling v3 with gitlab?

Posts: 3

Participants: 3

Read full topic

@it33 wrote:

This is a thread started to help troubleshoot issues with upgrading to GitLab 8.9, which upgrades users to Mattermost 3.1.

If you're having issues with the automated install, try running:

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

If this doesn't work, please post a new topic to this forum with:

1. A brief description of your issue as title
2. The step on which you're having issues
3. The relevant portion of the Mattermost log file at /var/log/gitlab/mattermost/mattermost.log

To start a new topic, click this link to the Gitlab Mattermost forum category then click New Topic. See bottom right button in screenshot for an illustration:

Pasted image1098x228 24.8 KB

Posts: 21

Participants: 10

Read full topic

@peteryates wrote:

We have been using GitLab (via the Omnibus RPM) for about 2.5 years and earlier this week decided that Mattermost would be useful too, so we set it up. I was under the assumption that email notifications would 'just work' as they do in GitLab, but this doesn't seem to be the case.

In the admin console, Send Email Notifications is set to false and all of the other email-related inputs are blank. Is there a simple way for me to have Mattermost use Gitlab's email settings? Or do I need to look at my GitLab config and copy them manually (I'm not sure where this is configured but I'll be able to find it if required).

Thanks for any help!

Posts: 4

Participants: 2

Read full topic

@revxx14 wrote:

I can't figure out how to backup the database. Can someone please send me a tutorial or something?

Updated June 28, 2016, here's the command:

sudo -u mattermost -i bash
/opt/gitlab/embedded/bin/pg_dump -U gitlab_mattermost -h /var/opt/gitlab/postgresql -p 5432 mattermost_production > mattermost_production_backup

Posts: 6

Participants: 2

Read full topic

@wpostma wrote:

What do you have to do in Gitlab 8.9 OMNIBUS to be able to access your mattermost.yourcompany.com/admin/ url?

1. I set up a clean Ubuntu 16 LTS vm. Completely clean and fresh.
2. I installed the Gitlab 8.9 omnibus edition.
3. I enabled the mattermost integration as per its docs:
   https://gitlab.com/gitlab-org/omnibus-gitlab/tree/master/doc/gitlab-mattermost

I expect that if I open http://mattermost.mycompany.com/ I can see the mattermost page. Instead I get a nginx 502 bad gateway.

Even though this is a clean install, I see the following database upgrade failure message in /var/log/gitlab/mattermost/mattermost.log:

root@cleanvm:/var/log/gitlab/mattermost# cat mattermost.log
!!!!Automatic database upgrade failed.!!!

    If you are upgrading from Mattermost v2 to v3
    make sure that you have backed up your database
    and then in /etc/gitlab/gitlab.rb set:

    mattermost['db2_backup_created'] = true
    mattermost['db2_team_name'] = TEAMNAME


    where TEAMNAME is the name of the default team.
    Run gitlab-ctl reconfigure again.

Should I follow the notes above anyways? Ie, adding:

mattermost['db2_backup_created'] = true
mattermost['db2_team_name'] = TEAMNAME

You know, it would be friendlier to non-ruby-coders to point out that really they would write:

mattermost['db2_backup_created'] = true
mattermost['db2_team_name'] = "TEAMNAME"

I did that, and still I have 502 bad gateway.

Did anybody else do a clean 8.9 install and enable mattermost? Does it Just Work or is it Just Broken?

A rather kludgy workaround for me is to manually launch mattermost from a little shell script, in my case I called it run-mattermost.sh, it looks like this:

#!/bin/sh
cd /opt/gitlab/embedded/service/mattermost/
sudo -u mattermost /opt/gitlab/embedded/bin/mattermost -config=/var/opt/gitlab/mattermost/config.json

That runs it, and now my bad gateway error is gone. Now I can create my initial team (companyname).

The mattermost logs contain an ugly panic like this:

2016-06-23_16:54:26.85623 panic: runtime error: invalid memory address or nil pointer dereference [recovered]
2016-06-23_16:54:26.85624       panic: interface conversion: interface is runtime.errorString, not string
2016-06-23_16:54:26.85624 [signal 0xb code=0x1 addr=0x0 pc=0x775569]
2016-06-23_16:54:26.85624
2016-06-23_16:54:26.85624 goroutine 1 [running]:
2016-06-23_16:54:26.85624 panic(0xcd1aa0, 0xc820045b00)
2016-06-23_16:54:26.85625       /usr/local/go/src/runtime/panic.go:481 +0x3e6
2016-06-23_16:54:26.85625 main.doLoadConfig.func1(0xc820145d48)
2016-06-23_16:54:26.85625       /var/lib/jenkins/jobs/mattermost-platform-release/workspace/src/github.com/mattermost/platform/mattermost.go:73 +0x6f
2016-06-23_16:54:26.85625 panic(0xccbec0, 0xc820012070)
2016-06-23_16:54:26.85625       /usr/local/go/src/runtime/panic.go:443 +0x4e9
2016-06-23_16:54:26.85625 github.com/mattermost/platform/utils.configureLog(0xc820070c70)

I think to fix that ugly logging error I have to manually change unix file owners:

chown -R mattermost:mattermost /var/log/gitlab/mattermost/

Alternatively I could add mattermost to the git group in /etc/group.

Warren

Posts: 3

Participants: 2

Read full topic

@xrain0610 wrote:

Hi, I add mattermost_external_url 'http://chat.simcu.com' , but the mattermost can't work well , notice:{"id":"api.context.404.app_error","message":"Sorry, we could not find the page.","detailed_error":"There doesn't appear to be an api call for the url='/api/v3/oauth/gitlab/'. Typo? are you missing a team_id or user_id as part of the url?","request_id":"","status_code":404,"is_oauth":false}

i try to delete the mattermost database and data folder , but not work also

Posts: 2

Participants: 2

Read full topic

@gl893 wrote:

Using Apache 2.4.7 on Ubuntu 14.04.4. Gitlab SSL configuration derived from https://gitlab.com/gitlab-org/gitlab-recipes/blob/master/web-server/apache/gitlab-omnibus-ssl-apache24.conf; copied and modified for Mattermost as well.

When a user navigates to https://mattermost.servername.com, a sign-in screen is presented. The button to "Login via Gitlab" is shown. Clicking this button initiates a request to https://mattermost.servername.com/api/v3/oauth/gitlab/signup, which returns a 302 Redirect to: https://gitlab.servername.com/oauth/authorize?response_type=code&client_id=xxxx&redirect_uri=http%3A%2F%2Fmattermost.servername.com%3A4443%2Fsignup%2Fgitlab%2Fcomplete&state=xxxx. Notice that the redirect_uri is missing the 's' for HTTPS. This causes the loaded Gitlab page to return "The redirect URI included is not valid."

Relevant gitlab.rb lines:

mattermost_external_url 'https://mattermost.servername.com'
mattermost['enable'] = true
mattermost['service_use_ssl'] = true
mattermost['service_address'] = "127.0.0.1"
mattermost['service_port'] = "8065"
mattermost_nginx['enable'] = false
mattermost_nginx['redirect_http_to_https'] = true # this likely does nothing


How can I fix the redirect_uri that is presented by the main Mattermost login page?

Posts: 2

Participants: 1

Read full topic

@janwillhaus wrote:

We run GitLab EE (installed via Omnibus) on premise at git.megacorp.example, with GitLab Pages configured as subdomains to an external URL like megacorp.io. In addition to that I'd like to set up GitLab Mattermost, but utilize the same domain, using mattermost.megacorp.io as the Mattermost URL. Is there any way to do this, like excluding the mattermost. subdomain from those available to GitLab Pages config? Currently if activating Mattermost for the mentioned URL I get the regular 404 error page that GitLab Pages outputs on non-existent pages.

Posts: 1

Participants: 1

Read full topic

@Quintasan wrote:

Hi,

I have successfully installed GitLab 8.9 using the Omnibus package.

After I managed to resolve the 502 error (the permissions on /var/log/gitlab/mattermost were wrong) I'm getting Client authentication failed due to unknown client, no client authentication included, or unsupported authentication method. when trying to sign in using GitLab.

Mattermost relevant lines from gitlab.rb:

mattermost_external_url 'https://m.mydomain.com'
mattermost['enable'] = true 
mattermost['username'] = 'mattermost'
mattermost['group'] = 'mattermost'
mattermost['home'] = '/var/opt/gitlab/mattermost'
mattermost['database_name'] = 'mattermost_production'

mattermost['service_use_ssl'] = true 
mattermost['service_enable_incoming_webhooks'] = true
mattermost['team_site_name'] = "Mattermost @ MyDomain"
mattermost['gitlab_enable'] = true
mattermost['gitlab_secret'] = "sekrit"
mattermost['gitlab_id'] = "even more sekrit"
mattermost['gitlab_scope'] = ""
mattermost['gitlab_auth_endpoint'] = "https://git.mydomain.com/oauth/authorize"
mattermost['gitlab_token_endpoint'] = "https://git.mydomain.com/oauth/token"
mattermost['gitlab_user_api_endpoint'] = "https://git.mydomain.com/api/v3/user"

mattermost_nginx['enable'] = true
mattermost_nginx['redirect_http_to_https'] = true
mattermost_nginx['ssl_certificate'] = "/etc/letsencrypt/live/m.mydomain.com/fullchain.pem"
mattermost_nginx['ssl_certificate_key'] = "/etc/letsencrypt/live/m.mydomain.com/privkey.pem"

What am I doing wrong?

Posts: 1

Participants: 1

Read full topic

@wpostma wrote:

Some basic documentation questions I can't find anything about:

1. Suppose I just want to DELETE all mattermost configuration and start again in a gitlab+mattermost situation? HOW can I wipe everything to do with mattermost out and start again?

2. Suppose I just want to go into some system console or admin, how do I do that?

3. Suppose I want to find out what accounts exist, how do I do that?

4. Suppose I want to find out what accounts exist that have administrative priveleges, how do I do that?

5. Suppose I type MyCompanyName in when I get to the page that lets me create a mattermost team. Why doesn't it warn me when I have done that before? Maybe because Mattermost is designed to be at Web Scale and it allows seventy people to have teams with the same names? Can we turn that off?

6. Suppose I open my mattermost team url up on one browser, and I can see it and I open it in another and I get a 404 error? What the heck is going on?

404.png1274x899 45.9 KB

7 - Suppose I want to upgrade from 8.8 to 8.9.x of gitlab, is that working yet? It seems it always breaks if you have mattermost enabled. I am in a VM so I can at least revert, but when oh when will it be possible to update to 8.9 of gitlab (and 3.0 of mattermost) without it just breaking?

Posts: 1

Participants: 1

Read full topic

@it33 wrote:

There's a known issue in GitLab 8.9 where error messages aren't pulling properly from localization files and Mattermost issues a "panic" message.

A common cause is attempting to automate SMTP email setup with configuration information would throw an error.

To address this:

1. Set mattermost['email_send_email_notifications'] = false in /etc/gitlab/gitlab.rb and run reconfigure
2. After the Mattermost server starts go to System Console > Notifications > Email to enter your SMTP information and click "Test Connection" to find the error and setup SMTP.

The fix for the error in log messages is already on master and will be released with Mattermost 3.2 on July 16.

Posts: 1

Participants: 1

Read full topic

@cr-slindsay wrote:

We recently migrated to GitLab 8.9 / Mattermost 3.1, and one of our users discovered that he was unable to log back in. Turns out he had never moved his account off of email sign-in, and since I had disabled email sign-in (allowing only GitLab SSO), he was now unable to log back in.

I re-enabled email sign-in so he could get back in and change his Sign-in Method under Account Settings > Security. He reported that this option does not appear for him. Confused, I logged in myself and checked the menu - sure enough, I do not have a "Sign-in Method" option available, either.

I have reloaded the page, cleared cache, tried different browsers, restarted the Mattermost service itself, and even run a gitlab-ctl reconfigure, but to no avail. The "Sign-in Method" is simply not available under Account Settings > Security, and users are thus unable to change their sign-in method.

Any help would be greatly appreciated.

Posts: 1

Participants: 1

Read full topic

@paulbdavis wrote:

Trying to use the cli tool in the gitlab omnibus installation and I am getting the following error:

$ /opt/gitlab/embedded/bin/mattermost -config /var/opt/gitlab/mattermost/config.json -permanent_delete_team -team_name="team012"

panic: Failed to load system translations for 'en'

goroutine 1 [running]:
github.com/mattermost/platform/utils.GetTranslationsBySystemLocale(0xc8201c67a3)
        /go/src/github.com/mattermost/platform/utils/i18n.go:44 +0x19a
github.com/mattermost/platform/utils.InitTranslations()
        /go/src/github.com/mattermost/platform/utils/i18n.go:29 +0x2e9
main.main()
        /go/src/github.com/mattermost/platform/mattermost.go:55 +0x48

goroutine 17 [syscall, locked to thread]:
runtime.goexit()
        /usr/local/go/src/runtime/asm_amd64.s:1696 +0x1

goroutine 5 [syscall]:
os/signal.loop()
        /usr/local/go/src/os/signal/signal_unix.go:22 +0x18
created by os/signal.init.1
        /usr/local/go/src/os/signal/signal_unix.go:28 +0x37

goroutine 8 [runnable]:
github.com/alecthomas/log4go.NewFileLogWriter.func1(0xc820129e00)
        /go/src/github.com/mattermost/platform/Godeps/_workspace/src/github.com/alecthomas/log4go/filelog.go:78
created by github.com/alecthomas/log4go.NewFileLogWriter
        /go/src/github.com/mattermost/platform/Godeps/_workspace/src/github.com/alecthomas/log4go/filelog.go:119 +0x38b

Trying to delete extra temas made while troubleshooting a certificate error

Posts: 7

Participants: 4

Read full topic

@manica wrote:

I have a working installation of 8.9.6 Gitlab + Mattermost. When I paste urls to Wikipedia and YouTube into Mattermost, I see the link previews. However, when I link to Gitlab commits or issues, I don't see any preview. Also, I'm assuming there is a short-hand for referring to issues, commits, diffs, etc. from Gitlab in Mattermost. How can I achieve gitlab link previews and what short-hand syntax is available?

Thank you!
Darin

Posts: 2

Participants: 2

Read full topic