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
2 posts - 2 participants
↧
He redirect URI included is not valid.
↧
Mattermost Enterprise with Gitlab Omnibus
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…
4 posts - 2 participants
↧
↧
System console not enabled for admin user in mattermost 5.4.0
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.
2 posts - 2 participants
↧
Slack advanced exporter and attachments
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.
7 posts - 2 participants
↧
[solved] Not listening to IPv6 connections
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
2 posts - 1 participant
↧
↧
[solved] How do you restore the mattermost database?
I was looking at the migration documents https://docs.mattermost.com/administration/migrating.html#migrating-the-mattermost-server.
In particular, step 4. And step 4 says:
Backup the database from the SOURCE Mattermost server and restore it in place of the database to which the DESTINATION server is connected.
And I’m like, duh. But what are the commands to do it?
I searched around and found the commands to export the database, but trying to restore it, not so lucky. There is this command:
sudo -u mattermost /opt/gitlab/embedded/bin/psql -U gitlab_mattermost -h /var/opt/gitlab/postgresql -d mattermost_production -f ./mattermost_production
But all I get is a bunch of relation exists errors. Is that normal?
2 posts - 1 participant
↧
OAuth single instance?
hi all, i am a GitLab employee and have a customer who may need multiple instances of GitLab. however, they feel their Mattermost integration prevents multiple GitLab instances due to Mattermost only supporting OAuth through a single instance. first, is this true? second, is this something that can be “fixed” or worked around? thanks in advance.
5 posts - 2 participants
↧
How to start the server without pinging the DB
Can I start the mattermost server without pinging the DB first?
I am using the latest version of mattermost server installed in an Amazon Linux EC2 instance and an AWS Aurora (MySQL 5.6) Database.
I start the server using the command:
sudo -u mattermost ./bin/mattermost
Mattermost first pings the IP indicated in the "datasource"section of file /opt/mattermost/config/config.json.
Is there an easy way to configure Mattermost server to NOT ping the DB first (maybe use telnet or something else to check that it is alive), connect to the DB and start the server?
Thank you.
10 posts - 4 participants
↧
List All Teams On Select Teams Page
Version number: 5.6.2
Summary
I’d like to know how to list all Teams on the select_team page.
Steps to reproduce
Once logged into Mattermost click the hamburger menu option ‘Join Another Team’.
I have determined that this only applies to System Admin users.
9 posts - 2 participants
↧
↧
Gitlab 7.8.1 webhook to Mattermost 5.5.1: No text specified
Summary
Our partner has an old gitlab 7.8.1 server. Webhooks coming from this server throws an error into the logfile of Mattermost. If we try the same on gitlab.com it works without an error as expected. Is there anything I can try but upgrade the old gitlab?
Steps to reproduce
- Generate a webhook url in Mattermost 5.5.1
- Setup a new webhook in Gitlab 7.8.1
- Test the webhook
Gitlab says that the webhook has been successfully requested but Mattermost log contains the following messages:
{"level":"error","ts":1559652194.857403,"caller":"web/context.go:60","msg":"No text specified","path":"/hooks/whp8gofrgpfgbbjqgozzpgf1tw","request_id":"fap3tc4ye7yq98wdcjrge6uqqo","
ip_addr":"*************","user_id":"","method":"POST","err_where":"HandleIncomingWebhook","http_code":400,"err_details":""}5 posts - 2 participants
↧
Imports from slack set all emails to domain "example.com"
Hello there, I have the latest version from github and just did a migration from the CLI. All of the users created have emails at domain “example.com” instead of their real email addresses
Any way to fix this? Happy to redo the import
2 posts - 2 participants
↧
Image / file attachments all fail - Slack import
I have mattermost 5.9.0
I get a million messages like this when importing from Slack – and no image attachments in the channels:
{“level”:“warn”,“ts”:1560283469.4840775,“caller”:“app/slackimport.go:404”,“msg”:“Slack Import: Unable to attach the file to the post as the latter has no file section present in Slack export.”}
3 posts - 2 participants
↧
Mattermost Gitlab oauth problem
Hey there,
our Gitlab Omnibus setup started having problems with the Mattermost OAuth workflow a few days ago. I’m including some info below. I’d appreciate any pointers, am happy to add any more info you might need.
Summary
Users logged in to Mattermost can use the application.
However, the OAuth workflow doesn’t work any more. After re-direction from the Mattermost to the Gitlab login page, logging in with correct credentials, users receive the message:
Error
Bad Response from token request.
Well, this would be the English version - actually, since our setup is localized, the message is in German: “Fehlerhafte Rückmeldung bei Tokenanfrage”.
Steps to reproduce
-
Version number
Gitlab omnibus 11.8.10 -
Steps to reproduce your issue
Docker install of Gitlab omnibus. Setup Mattermost OAuth workflow.
Trying to log in to Mattermost correctly redirects to the Gitlab login page. Login with correct credentials yields the message “Bad Response from token request.” Login with wrong credentials yields "Could not authenticate you from Ldapmain because "Invalid credentials for “.”, so contacting our LDAP is not the problem.
-
Link to the documentation you’re using, noting the step where you encounter the issue.
n/a -
The relevant portion of the Mattermost log file at /var/log/gitlab/mattermost/mattermost.log
tail -f /var/log/gitlab/mattermost/mattermost.log
[…]
{“level”:“error”,“ts”:1561383629.897077,“caller”:“api4/oauth.go:492”,“msg”:“AuthorizeOAuthUser: Fehlerhafte Rückmeldung bei Tokenanfrage, response_body={“error”:“invalid_grant”,“error_description”:“The provided authorization grant is invalid, expired, revoked, does not match the redirection URI used in the authorization request, or was issued to another client.”}”}
[…]
Thank you.
3 posts - 2 participants
↧
↧
Configure stand-alone mattermost with gitlab sign-on
Hello,
I have installed mattermost as a separate server on its own virtual machine on docker on Ubuntu 18.04. I’m running nginx 1.17 alpine, mattermost database (postgresql) and the mattermost application itself.
On another virtual machine I have gitlab installed. The point is the configure SSO with gitlab, so that I can use LDAP with mattermost Team Edition. I haven’t been able to do so, though, because I keep getting this error:
{"level":"error","ts":1564185931.9620516,"caller":"api4/oauth.go:493","msg":"AuthorizeOAuthUser: Token request failed, Post https://gitlab.example.com/oauth/token: dial tcp: i/o timeout"}
I’m configured gitlab with https, I’ve added a new application in gitlab, copied all the necessary information in the Gitlab section under System Control in mattermost, but I still get this.
Under special circumstances which I haven’t really been able to determine, it sometimes does work after refreshing the mattermost page, despite the “Token request failed” error.
I think it might have worked when I configured gitlab with http only. But the error was still there nonetheless, so the problem sticks, so I doubt it’s actually related to TLS.
Any ideas what is happening? The gitlab server is reachable, I can ping, curl etc., but the POST request seems problematic.
This is my gitlab configuration:
external_url 'https://repos.example.com'
gitlab_rails['ldap_enabled'] = true
gitlab_rails['ldap_servers'] = YAML.load <<-EOS
main: # 'main' is the GitLab 'provider ID' of this LDAP server
label: 'LDAP'
host: 'atene-dc01.atene.local'
port: 636
uid: 'sAMAccountName'
bind_dn: 'cn=gitlab-user,ou=Company-Dienstkonten,dc=domaincontroller,dc=local'
password: '5}#HSZ,7kq-DQI4Ms23?'
encryption: 'simple_tls' # "start_tls" or "simple_tls" or "plain"
verify_certificates: true
active_directory: true
lowercase_usernames: true
base: 'ou=Aktive User,ou=atene,dc=domaincontroller,dc=local'
user_filter: ''
EOS
unicorn['enable'] = true
unicorn['worker_timeout'] = 60
unicorn['worker_processes'] = 2
nginx['redirect_http_to_https'] = true
nginx['ssl_certificate'] = "/etc/gitlab/ssl/#{node['fqdn']}.crt"
nginx['ssl_certificate_key'] = "/etc/gitlab/ssl/#{node['fqdn']}.key"
nginx['ssl_ciphers'] = "ECDHE-RSA-AES256-GCM-SHA384:ECDHE-RSA-AES128-GCM-SHA256"
nginx['ssl_prefer_server_ciphers'] = "on"
nginx['ssl_protocols'] = "TLSv1.2"
nginx['gzip_enabled'] = false
letsencrypt['enable'] = false
As you can see, I haven’t configured anything related to mattermost here, because, as I understand, this is related only to the omnibus gitlab mattermost that comes preinstalled with gitlab, as far as I understand.
17 posts - 3 participants
↧
Not redirected to gitlab SSO on IIS reverse proxy
hi.
using iis as a reverse proxy
using gitlab SSO (not omnibus)
mattermost domain : mm2.XX.co.kr
gitlab domain : gittest.XX.co.kr
Reverse rewrite host in response headers “check config”
not redirected to gitlab login page
packet capture on iis server
No connection attempt from GitLab server packet capture
What is the problem?
1 post - 1 participant
↧
Whitelist accounts when using Gitlab SSO
Hi,
I set up GitLab SSO on my self hosted mattermost running in docker.
I have it working, but I am wondering how to choose who gets to access the server.
There is no inviting to the server, and it seems that anyone with a GitLab account can log on and create a team. I only intended for it to be used by a small hobby project group. Is there any way I to whitelist gitlab accounts?
2 posts - 2 participants
↧
Sending Notication Emails
Hi,
I’m trying to configure Mattermost to send out notification emails via SMTP. The notifications are triggered when a Gitlab pipeline is triggered - this is working correctly. The SMTP connection is set up correcly - test email went through. I’d like to be able to send any notification message that gets posted to the channel out via email as well - is there a way to do that?
3 posts - 3 participants
↧
↧
Change GitLab instance used for authentication
Hello everyone,
We are currently using the Mattermost Team edition and are using our own Enterprise GitLab instance as authentication.
We want to set up a Community GitLab instance to use as authentication instead, since otherwise everyone who wants to use Mattermost has to have a Enterprise GitLab Account.
Is it possible to just switch the authentication on Mattermost to a different GitLab instance while maintaining user history and teams for already registered users?
Would be glad if anyone knew anything before we tried it for nothing.
Thanks!
~ onno_ole ~
1 post - 1 participant
↧
Selectively delete chat
Hi everyone,
Is there any way to delete log chats between users, possibly only messages sent between selected dates? I have some users who have exchanged critical / confidential information at some point in past and would like it to be removed.
2 posts - 2 participants
↧
Disk space utilization
Hello,
I am using Gitlab Mattermost Team Edition and have around 20 users.
Mattermost Version: 5.13.2
Database Schema Version: 5.13.0
Database: postgres
Since few months i experience Mattermost is taking lots of disk space, in last 20 days it consumed around 1.3 GB space. Below directory is taking lots of space which has many files inside.
/var/opt/gitlab/postgresql/data/base/16401
I am not sure what to do to make it consume less space or how to delete old chat from channels. Kindly suggest to resolve this issue.
Thank You,
Ravi K.
8 posts - 2 participants
↧