@lvornholt wrote:

Summary

we use the gitlab omnibus package and want to use mattermost. We set up mattermost and gitlab on same host with two different DNS-Names. Both running on HTTPS.

After a short test with some developers we try to clean up and delete some empty teams called "test" or "Admin".
If I try to delete the teams with

 sudo -u mattermost ./mattermost -config=/var/opt/gitlab/mattermost/config.json team delete Admin

here you see command and Error out put

sudo -u mattermost ./mattermost -config=/var/opt/gitlab/mattermost/config.json team delete Admin
Have you performed a database backup? (YES/NO):
YES
Are you sure you want to delete the teams specified?  All data will be permanently deleted? (YES/NO):
YES
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x416488]

goroutine 1 [running]:
panic(0xbde860, 0xc4200100c0)
        /usr/local/go/src/runtime/panic.go:500 +0x1a1
main.getTeamFromTeamArg(0x7ffc3f3918e4, 0x5, 0x1)
        /var/lib/jenkins/jobs/msr/jobs/platform-release/workspace/src/github.com/mattermost/platform/cmd/platform/teamargs.go:21 +0x28
main.getTeamsFromTeamArgs(0xc4200cd3c0, 0x1, 0x2, 0x3, 0x1, 0x0)
        /var/lib/jenkins/jobs/msr/jobs/platform-release/workspace/src/github.com/mattermost/platform/cmd/platform/teamargs.go:13 +0xa2
main.deleteTeamsCmdF(0x106b700, 0xc4200cd3c0, 0x1, 0x2, 0x0, 0x0)
        /var/lib/jenkins/jobs/msr/jobs/platform-release/workspace/src/github.com/mattermost/platform/cmd/platform/team.go:187 +0xdf
github.com/mattermost/platform/vendor/github.com/spf13/cobra.(*Command).execute(0x106b700, 0xc4200cd1a0, 0x2, 0x2, 0x106b700, 0xc4200cd1a0)
        /var/lib/jenkins/jobs/msr/jobs/platform-release/workspace/src/github.com/mattermost/platform/vendor/github.com/spf13/cobra/command.go:632 +0x23e
github.com/mattermost/platform/vendor/github.com/spf13/cobra.(*Command).ExecuteC(0xc4200986c0, 0x0, 0x0, 0x0)
        /var/lib/jenkins/jobs/msr/jobs/platform-release/workspace/src/github.com/mattermost/platform/vendor/github.com/spf13/cobra/command.go:722 +0x367
github.com/mattermost/platform/vendor/github.com/spf13/cobra.(*Command).Execute(0xc4200986c0, 0xc42010ea40, 0xb)
        /var/lib/jenkins/jobs/msr/jobs/platform-release/workspace/src/github.com/mattermost/platform/vendor/github.com/spf13/cobra/command.go:681 +0x2b
main.main()
        /var/lib/jenkins/jobs/msr/jobs/platform-release/workspace/src/github.com/mattermost/platform/cmd/platform/mattermost.go:50 +0x49f

I got the same error when calling other command like team add Admin username

Posts: 1

Participants: 1

Read full topic

@icanogbh wrote:

Summary

After installing gitlab omnibus, we enabled mattermost, setup our own push proxy server and compile IOS and Android apps. Android app is getting Push notifications without any issue.

IOS App doesn't get notifications, because the Push Proxy doesn't send them, because there is no IOS Device registered, and this is because the IOS App is not sending the device id on login, it's trying to send it afterwards using the attach_device endpoint of the V3 API, but GitlabMattermost seems to be missing this API, since its just returning a 404 not found.

Found this related issue: https://github.com/mattermost/ios/issues/10 His solution was installing mattermost platform from scratch... but this defeats the purpose of taking advantage of the omnibus package...

Any help with this?

Steps to reproduce

1. Version number
   • Gitlab Omnibus package v9.0
   • Mattermost v3.7.2
   • Mattermost Push Proxy v3.7.1
   • Mattermost IOS app v3.5
2. Steps to reproduce your issue
   1. Compile IOS app
   2. Setup Push Proxy
   3. Send message from GitlabMattermost to IOS User
3. Link to the documentation you're using, noting the step where you encounter the issue.
   • Github readme's for each app.
4. The relevant portion of the Mattermost log file at /var/log/gitlab/mattermost/mattermost.log

Error: statusCode=404 data=Optional({"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/users/attach_device'.  Typo? are you missing a team_id or user_id as part of the url?","status_code":404})
Failed attaching device id to session
Sorry, we could not find the page.

Posts: 1

Participants: 1

Read full topic

@Kilmar wrote:

Summary

Using gitlab as oAuth2 service provider to log into mattermost, deleted user (in gitlab) is still logged in mattermost until auth cookie in browser is valid.

Steps to reproduce

1. Setup oAuth authorization from gitlab to mattermost
2. Login into mattermost
3. Delete logged user from gitlab
4. Deleted user is logged until cookie is valid or logged out by himself

Mattermost: v 3.6.2

Question is: How to handle this ? Is there some check from mattermost to service provider api if user still exist ? What to do when someone deletes user credential on provider system during his session in mattermost ?

Thx.

Posts: 1

Participants: 1

Read full topic

@expatcz wrote:

Hi,

I'm trying to setup gitlab and mattermost behind haproxy.
I'm using the official docker image of gitlab/gitlab-ce , tag 9.2.1-ce.0 .
Both of them should be running in one and the same container, wich mappes the exposed ports 80 and 443 on the host 192.168.10.121:

8080 -> 80
8443 -> 443

gitlab uses the hostname 'git.mydomain.com' ,
mattermost uses 'chat.mydomain.com'

Both are directed to the same haproxy backend:

backend http_gitlab
mode http
option httplog
option forwardfor
option http-server-close
option httpchk
http-request set-header X-Forwarded-Port %[dst_port]
http-request set-header X-Forwarded-Proto https if { ssl_fc }
server gitlab 192.168.10.121:8080 maxconn 50

I've modified the gitlab.rb according the gitlab documentation:

external_url 'https://git.mydomain.com'
nginx['listen_port'] = 80
nginx['listen_https'] = false
nginx['proxy_set_headers'] = {
"X-Forwarded-Proto" => "https",
"X-Forwarded-Ssl" => "on",
}

mattermost_external_url 'https://chat.mydomain.com'
mattermost_nginx['listen_port'] = 80
mattermost_nginx['listen_https'] = false
mattermost_nginx['proxy_set_headers'] = {
"X-Forwarded-Proto" => "https",
"X-Forwarded-Ssl" => "on",
}

gitlab itself is working fine at https://git.mydomain.com .
But mattermost has an issue with SSO: After it redirects me to gitlab for login and I klick 'Authorize', a blank page is displayed. The page source contains:

{"id":"api.user.authorize_oauth_user.token_failed.app_error","message":"Token request failed","detailed_error":"","request_id":"km8x4wu9if817njji1rwb1smjc","status_code":500}

And an error message is raised in the mattermost current log:

2017-05-25_10:30:18.81999 [2017/05/25 10:30:18 UTC] [EROR] /signup/gitlab/complete:AuthorizeOAuthUser code=500 rid=urc7pnxmwpgd5p6xs73botb3gr uid= ip=192.168.10.2, 192.168.10.101 Token request failed [details: Post https://git.mydomain.com/oauth/token: x509: certificate is not valid for any names, but wanted to match git.mydomain.com]

I've no glue, what could cause this error. gitlab is running fine with the certificate on the proxy server. I also copied the git.mydomain.com.crt from the haproxy server to the config/ssl dir of gitlab because it also contains the ca's cert. But the error persists.

Does someone have any hint about the issue?

Thanks a lot.

Posts: 1

Participants: 1

Read full topic

@chhitz wrote:

After the update to Mattermost 3.10 (with the Gtilab 9.3 release) I'm not able to open the Mattermost UI anymore. I get the following JS error:

team_button.jsx:55 Uncaught (in promise) TypeError: Cannot read property 'substring' of undefined
    at t.value (team_button.jsx:55)
    at d._renderValidatedComponentWithoutOwnerOrContext (ReactCompositeComponent.js:803)
    at d._renderValidatedComponent (ReactCompositeComponent.js:826)
    at d.performInitialMount (ReactCompositeComponent.js:366)
    at d.mountComponent (ReactCompositeComponent.js:262)
    at Object.mountComponent (ReactReconciler.js:50)
    at h.mountChildren (ReactMultiChild.js:242)
    at h._createInitialChildren (ReactDOMComponent.js:701)
    at h.mountComponent (ReactDOMComponent.js:520)
    at Object.mountComponent (ReactReconciler.js:50)

I am the admin of the Mattermost server and team. Other users don't see this issue.

Posts: 1

Participants: 1

Read full topic

@Himani wrote:

Hello,
I tried Mattermost loadtest on 4cpu and 7.5GB server for 10000 users and got load test report as below:
--------- Loadtest Report ------------
Route: /channels/members/me/view
Total Hits: 8053
Error Rate: 64.91%
Max Response Time: 196ms
Min Response Time: 2ms
Mean Response Time: 14.20ms
Variance of Response Time: 92.79

Route: /channels/CID/members/me
Total Hits: 8053
Error Rate: 64.90%
Max Response Time: 148ms
Min Response Time: 1ms
Mean Response Time: 10.43ms
Variance of Response Time: 70.16

Route: /channels/CID/members
Total Hits: 62953
Error Rate: 95.51%
Max Response Time: 116ms
Min Response Time: 1ms
Mean Response Time: 5.90ms
Variance of Response Time: 3.01

Route: /channels/CID/stats
Total Hits: 8053
Error Rate: 64.90%
Max Response Time: 95ms
Min Response Time: 0ms
Mean Response Time: 4.41ms
Variance of Response Time: 27.14

Route: /channels/CID/posts
Total Hits: 8053
Error Rate: 64.90%
Max Response Time: 201ms
Min Response Time: 0ms
Mean Response Time: 5.12ms
Variance of Response Time: 37.94

Route: /teams/TID/posts/search
Total Hits: 293
Error Rate: 100.00%
Max Response Time: 0ms
Min Response Time: -1ms
Mean Response Time: 0.00ms
Variance of Response Time: 0.00

Route: /posts
Total Hits: 1160
Error Rate: 67.50%
Max Response Time: 488ms
Min Response Time: 12ms
Mean Response Time: 83.40ms
Variance of Response Time: 1394.27

Route: /files
Total Hits: 9
Error Rate: 0.00%
Max Response Time: 213ms
Min Response Time: 6ms
Mean Response Time: 46.89ms
Variance of Response Time: 4364.86

Route: /posts/PID/files/info
Total Hits: 7
Error Rate: 0.00%
Max Response Time: 14ms
Min Response Time: 1ms
Mean Response Time: 3.00ms
Variance of Response Time: 23.67

Route: /files/PID/thumbnail
Total Hits: 5
Error Rate: 0.00%
Max Response Time: 3ms
Min Response Time: 2ms
Mean Response Time: 2.20ms
Variance of Response Time: 0.20

Route: /users/status/ids
Total Hits: 30
Error Rate: 93.33%
Max Response Time: 9ms
Min Response Time: 1ms
Mean Response Time: 8.50ms
Variance of Response Time: 2.07

Score: 16.73
I got runtime error during loadtest all :invalid memory address or nil pointer dereference: goroutine and report is not saved in directory but it display in console.
I want to know what is 100% error rate mean and why it is giving 100% error rate

Posts: 2

Participants: 2

Read full topic

@swashata wrote:

Summary

When I am trying to add the integration with mattermost slash command, I follow the Add to Mattermost button. But it is returning No session could be set up, is Mattermost configured with Single Sign On?

Steps to reproduce

• Install Mattermost through omnibus. As referred here
• Go to Any Project > Settings > Integration and click on Mattermost Slash Commands.
• Click on Add to Mattermost

2017-08-02_20-21-23.gif1220x612 2.51 MB

Currently running GitLab 9.4.3
with the following /etc/gitlab/gitlab.rb

external_url "https://wpquark.io"
nginx['redirect_http_to_https'] = true
nginx['ssl_certificate'] = "/etc/letsencrypt/live/wpquark.io/fullchain.pem"
nginx['ssl_certificate_key'] = "/etc/letsencrypt/live/wpquark.io/privkey.pem"
nginx['custom_gitlab_server_config'] = "location ^~ /.well-known { root /var/www/letsencrypt; }"

# SMTP Emailing
gitlab_rails['smtp_enable'] = true
gitlab_rails['smtp_address'] = "some.mail.server"
gitlab_rails['smtp_port'] = 465
gitlab_rails['smtp_user_name'] = "no-reply@wpquark.io"
gitlab_rails['smtp_password'] = "supersecretpassword"
gitlab_rails['smtp_domain'] = "wpquark.io"
gitlab_rails['smtp_authentication'] = "login"
gitlab_rails['smtp_enable_starttls_auto'] = true
gitlab_rails['smtp_openssl_verify_mode'] = 'peer'
gitlab_rails['smtp_tls'] = true
gitlab_rails['gitlab_email_from'] = 'no-reply@wpquark.io'
gitlab_rails['gitlab_email_reply_to'] = 'no-reply@wpquark.io'

# MatterMost
mattermost_external_url 'http://chat.wpquark.io'
mattermost_nginx['custom_gitlab_mattermost_server_config'] = "location ^~ /.well-known { root /var/www/mattermost; }"

#mattermost['email_enable_sign_in_with_email'] = true
mattermost['email_enable_sign_up_with_email'] = true
mattermost['email_send_email_notifications'] = true
mattermost['email_smtp_username'] = "no-reply@wpquark.io"
mattermost['email_smtp_password'] = "supersecretpassword"
mattermost['email_smtp_server'] = "some.mail.server"
mattermost['email_smtp_port'] = "465"
mattermost['email_connection_security'] = 'TLS'
mattermost['email_feedback_name'] = "WPQuark Chat"
mattermost['email_feedback_email'] = "no-reply@wpquark.io"
mattermost['service_enable_incoming_webhooks'] = true
mattermost['service_enable_commands'] = true
mattermost['service_enable_only_admin_integrations'] = true

The relevant portion of the Mattermost log file at /var/log/gitlab/mattermost/mattermost.log

2017-08-02_14:17:17.02101 [2017/08/02 19:47:17 IST] [INFO] Server is listening on 127.0.0.1:8065
2017-08-02_14:17:17.02244 [2017/08/02 19:47:17 IST] [INFO] Starting jobs
2017-08-02_14:19:25.44265 [2017/08/02 19:49:25 IST] [EROR] AuthorizeOAuthUser: Invalid state,
2017-08-02_14:22:24.40188 [2017/08/02 19:52:24 IST] [EROR] AuthorizeOAuthUser: Invalid state,
2017-08-02_14:25:13.28750 [2017/08/02 19:55:13 IST] [EROR] AuthorizeOAuthUser: Invalid state,
2017-08-02_14:35:49.50315 [2017/08/02 20:05:49 IST] [INFO] Config file watcher detected a change reloading /var/opt/gitlab/matt$2017-08-02_14:35:49.77653 [2017/08/02 20:05:49 IST] [INFO] Stopped jobs
2017-08-02_14:35:49.77673 [2017/08/02 20:05:49 IST] [INFO] Stopping Server...
2017-08-02_14:35:49.77673 [2017/08/02 20:05:49 IST] [INFO] Closing SqlStore
2017-08-02_14:35:50.05346 [2017/08/02 20:05:50 IST] [INFO] Loaded system translations for 'en' from '/opt/gitlab/embedded/servi$2017-08-02_14:35:51.63763 [2017/08/02 20:05:51 IST] [INFO] Current version is 4.0.0 (4.0.2/Fri Jul 28 19:49:45 UTC 2017/f71cc06$2017-08-02_14:35:51.63766 [2017/08/02 20:05:51 IST] [INFO] Enterprise Enabled: false
2017-08-02_14:35:51.63766 [2017/08/02 20:05:51 IST] [INFO] Current working directory is /opt/gitlab/embedded/service/mattermost 2017-08-02_14:35:51.63766 [2017/08/02 20:05:51 IST] [INFO] Loaded config file from /var/opt/gitlab/mattermost/config.json
2017-08-02_14:35:51.63767 [2017/08/02 20:05:51 IST] [INFO] Server is initializing...
2017-08-02_14:35:51.63767 [2017/08/02 20:05:51 IST] [INFO] Pinging SQL master database
2017-08-02_14:35:51.64092 [2017/08/02 20:05:51 IST] [INFO] Pinging SQL replica-0 database
2017-08-02_14:35:51.67810 [2017/08/02 20:05:51 IST] [INFO] Initializing job API routes
2017-08-02_14:35:51.69171 [2017/08/02 20:05:51 IST] [INFO] API version 3 is scheduled for deprecation. Please see https://api.m$2017-08-02_14:35:51.69172 [2017/08/02 20:05:51 IST] [INFO] Starting 8 websocket hubs
2017-08-02_14:35:51.76472 [2017/08/02 20:05:51 IST] [INFO] Starting Server...
2017-08-02_14:35:51.76474 [2017/08/02 20:05:51 IST] [INFO] Server is listening on 127.0.0.1:8065
2017-08-02_14:35:51.76549 [2017/08/02 20:05:51 IST] [INFO] Starting jobs
2017-08-02_14:36:59.25564 [2017/08/02 20:06:59 IST] [EROR] AuthorizeOAuthUser: Invalid state,
2017-08-02_14:41:28.66887 [2017/08/02 20:11:28 IST] [EROR] AuthorizeOAuthUser: Invalid state,
2017-08-02_14:42:17.68168 [2017/08/02 20:12:17 IST] [EROR] AuthorizeOAuthUser: Invalid state,
2017-08-02_14:45:30.08326 [2017/08/02 20:15:30 IST] [EROR] AuthorizeOAuthUser: Invalid state,

Is is due to the fact that gitlab is using https and mattermost http. I can’t test right now because let’s encrypt is still waiting for DNS propagation.

Posts: 3

Participants: 1

Read full topic

@hassanfarid wrote:

I have installed GitLab CE docker image on a container, using command below. Does it contain MatterMost instance that I can start? OR do I need to installer GitLab Matter Most separately?

docker run -d -p 5080:80 -p 5022:22 -p 5443:443 --name gitlab_ce \
--hostname 10.xx.xx.x \
--restart always \
-v /data/gitlab_ce/etc/gitlab:/etc/gitlab \
-v /data/gitlab_ce/var/opt/gitlab:/var/opt/gitlab \
-v /data/gitlab_ce/var/log/gitlab:/var/log/gitlab \
gitlab/gitlab-ce:9.4.3-ce.0

Posts: 2

Participants: 2

Read full topic

@sborer wrote:

We are using Mattermost with the Gitlab-ce installation.
Emails in Gitlab work using an Exchange server with the following settings:

gitlab_rails[‘smtp_enable’] = true
gitlab_rails[‘smtp_address’] = "mail.***.ch"
gitlab_rails[‘smtp_port’] = 587
gitlab_rails[‘smtp_user_name’] = "git"
gitlab_rails[‘smtp_password’] = "***"
gitlab_rails[‘smtp_domain’] = "mail.***.ch"
gitlab_rails[‘smtp_authentication’] = "login"
gitlab_rails[‘smtp_enable_starttls_auto’] = true
gitlab_rails[‘smtp_openssl_verify_mode’] = ‘none’

Mattermost is configured as close as possible but doesn’t work.
config:

mattermost[‘email_enable_sign_up_with_email’] = false
mattermost[‘email_enable_sign_in_with_email’] = false
mattermost[‘email_enable_sign_in_with_username’] = false
mattermost[‘email_send_email_notifications’] = true
mattermost[‘email_require_email_verification’] = false
mattermost[‘email_smtp_username’] = "git"
mattermost[‘email_smtp_password’] = "***"
mattermost[‘email_smtp_server’] = "mail.***.ch"
mattermost[‘email_smtp_port’] = 587
mattermost[‘email_connection_security’] = “STARTTLS” # tried different things here
mattermost[‘email_feedback_name’] = "***"
mattermost[‘email_feedback_email’] = “***”

Which leads to the following mattermost config.json:

“EnableSignUpWithEmail”: false,
“EnableSignInWithEmail”: false,
“EnableSignInWithUsername”: false,
“SendEmailNotifications”: true,
“RequireEmailVerification”: false,
“FeedbackName”: “***”,
“FeedbackEmail”: “git@***.ch”,
“FeedbackOrganization”: “”,
“SMTPUsername”: “git”,
“SMTPPassword”: “***”,
“SMTPServer”: “mail.***.ch”,
“SMTPPort”: “587”,
“ConnectionSecurity”: “”,
“InviteSalt”: “***”,
“SendPushNotifications”: false,
“PushNotificationServer”: “”,
“PushNotificationContents”: “generic”,
“EnableEmailBatching”: false,
“EmailBatchingBufferSize”: 256,
“EmailBatchingInterval”: 30,
“SkipServerCertificateVerification”: false,
“EnableSMTPAuth”: false,
“EmailNotificationContentType”: “full”

First thing we noticed is that ConnectionSecurity is not set (although set in gitlab.rb -> mattermost['email_connection_security = “STARTTLS”).
Also EnableSMTP false seems wrong, user and password are provided…
In the admin_console, these settings are the same (accoring to config.json, not gitlab.rb).

In the config.json are fields available that might be needed for our setup, but not int the gitlab.rb:

• EnableSMTPAuth (= gitlab_rails[‘smtp_authentication’] ?!)
• SkipServerCertificateVerification (= gitlab_rails[‘smtp_openssl_verify_mode’] ?!)
• ConnectionSecurity ( = STARTTLS, like gitlab_rails[‘smtp_enable_starttls_auto’] ?!)

The mattermost log shows the following error after setting all the correct setting in admin_console:

2017-09-05_13:29:31.55018 [2017/09/05 15:29:31 CEST] [EROR] /api/v4/email/test:SendMail code=500 rid=u31w4bhee7y8df3pm1yffqy9cw uid=4mfjbwy7478xfqd5bw86ngk7ia ip=*** Failed to authenticate on SMTP server [details: 504 5.7.4 Unrecognized authentication type]

What are we doing wrong?!

Posts: 1

Participants: 1

Read full topic

@sdhar wrote:

I am developing a game and I would like to use the buttons to make it a lot easier for my users to play.

Posts: 2

Participants: 2

Read full topic

@GuiGuiSoft wrote:

Hello,

I am using a local storage directory for files and images. Can I safely delete all files in it ?
Of course they won’t be accessible through the Mattermost interface (404-error-like ?).
My question is : are they any other side effects ?

Note that I am not asking for a feature (I already voted for this on uservoice a long time ago). I am looking for a workaround because the feature is not implemented today.
I totally understand that Mattermost developers don’t want to implement the feature (because of a business plan, because of other priorities, lack of time…). But I don’t want to add “unlimited” local storage or pay for amazon service for “old files forgotten by all”

Thank you for your feedbacks.
Regards.

Posts: 1

Participants: 1

Read full topic

@dehalion wrote:

Hi!

Is it possible to allow users to log in with the same user account using different sign in methods, like using GitLab SSO from one device and using Email/Password from somewhere else?

Thanks…

Posts: 3

Participants: 2

Read full topic

@miguemely wrote:

Summary

When setting up GitLab + Mattermost, http works, however, when https is enabled, it just redirects to gitlab, and doesn’t go to Mattermost.

Steps to reproduce

Set up the following lines in gitlab.rb:

mattermost['service_use_ssl'] = true
mattermost_nginx['redirect_http_to_https'] = true
mattermost_nginx['ssl_certificate'] = "/etc/letsencrypt/live/[domain]/fullchain.pem"
mattermost_nginx['ssl_certificate_key'] = "/etc/letsencrypt/live/[domain]/privkey.pem"
mattermost_nginx['custom_gitlab_mattermost_server_config'] = "location ^~ /.well-known {\n alias /var/www/letsencrypt/.well-known;\n}\n"

Expected behavior

SSL should be working on both Gitlab and Mattermost.

Observed behavior

See the summary. Don’t know where to even get an error log for this type of issue. It reconfigured successfully, so I have no idea.

Edit 1/5/2018: Moved to relevant topic section.

Posts: 1

Participants: 1

Read full topic

@SSD wrote:

After configuring SSL on Gitlab Omnibus Mattermost I get an nginx 502 error.

/var/log/gitlab/mattermost/current has this interesting line:

Error: Config.IsValid: Site name must be less than or equal to 30 characters.,

I have two questions:

0. What does it mean by “site name”? Does it mean the external URL? That seems crazy but what else could it be?

1. Does the 30 characters include . ? Because mine is 32 with the .'s

2. Could this cause the error?

Posts: 2

Participants: 1

Read full topic

@SSD wrote:

Please include with your troubleshooting request:

Summary

I want to log into mattermost..com on a GItLab Omnibus install. I can’t log in with gitlab

Steps to reproduce

Install. Navigate to mattermost..com. Click “Log in with Gitlab”

You are taken to gitlab..com and there you see this error:

An error has occurred

The redirect URI included is not valid.

Posts: 4

Participants: 3

Read full topic

@ZombieMisaka wrote:

I set gitlab applications key and login successfully by my gitlab account in chrome,but the ubuntu client show this

system:ubuntu 18.04
client :4.1.2

Posts: 2

Participants: 2

Read full topic

@arnuschky wrote:

We’re thinking about switching to Mattermost Enterprise. However, AFAIK we would need to deploy Mattermost ourselves, migrating from the community version embedded in Gitlab Mattermost. Is that true?

If that’s the case, it seems almost too much work for switching to Enterprise…

Posts: 3

Participants: 2

Read full topic

@Farook wrote:

I had successfully set up mattermost 5.40 in Ubuntu 14.04 by following https://docs.mattermost.com/install/install-ubuntu-1404.html#installing-mattermost-server. I could able to access system console if i access application via IP. But when i access the application via domain name, i could not see the system console for the admin user. Also, am getting "websocket_client.jsx:38 WebSocket connection to ‘ws://mattermost.metagis.se/api/v4/websocket’ failed: Error during WebSocket handshake: ‘Connection’ header value must contain ‘Upgrade’ in the console . I had also configured nginx based on this https://docs.mattermost.com/install/install-ubuntu-1404.html#configuring-nginx-as-a-proxy-for-mattermost-server.Please note that
my nginx and mattermost application are in different server. Not sure it is because of this issue.

Posts: 2

Participants: 2

Read full topic

@oscargoldman wrote:

Has anyone had success exporting slack workspace attachments and successfully importing them all into a gitlab mattermost team?

We had tried suing the advanced exporter some time ago and successfully exported our files, but now the tool doesn’t seem to work - can anyone confirm that? I process our export archive for emails first, then for files, and nothing happens.

Any help and step by step instructions to complete would be very appreciated.

Posts: 3

Participants: 2

Read full topic

@maxxer wrote:

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

Posts: 2

Participants: 1

Read full topic