Quantcast
Channel: Mattermost Discussion Forums - Latest topics
Viewing all 6408 articles
Browse latest View live

Slack vs Discord Vs Mattemorst

$
0
0

@Issa2019 wrote:

Hello there,

i m looking for tab with all différence features for the 3 tools.

For me now i think the best Discord.

but the big problem is the hosting, we can 't host u own server that not cool.

Thanks all

Posts: 1

Participants: 1

Read full topic


[Issue] Can't send emails

$
0
0

@Zeukat wrote:

Hello,

I’ve just installed and configured Mattermost on a ubuntu Vps and I got an issue with sending emails.

Summary

After installing, configuring, and testing Mattermost on my VPS, I have one major issue. Mattermost can’t send emails.
I configured the smtp parameters, I don’t have any errors when testing it, even have the confirmation message that is works “No errors were reported while sending an email. Please check your inbox to make sure.”, but it doesn’t send any mails.

Steps to reproduce

Mattermost Version: 5.13.2
Database Schema Version: 5.13.0
Database: mysql

Smtp parameters :
SMTP Server: mail.infomaniak.com
SMTP Server Port: 587
SMTP Server Username: [my email address]
SMTP Server Password: [my password]
Connection Security: TLS

Test connection result :
No errors were reported while sending an email. Please check your inbox to make sure.

Expected behavior

The emails should be send when testing the connection, or using “forgot my password”.

Observed behavior

Despite the connection test being successful, the application is not sending anything. I already checked the log with my smtp provider, the emails or not rejected, there is just nothing send through the address.

Posts: 1

Participants: 1

Read full topic

Configure stand-alone mattermost with gitlab sign-on

$
0
0

@vinci wrote:

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.

Posts: 1

Participants: 1

Read full topic

Failed to initialize config when running mattermost load-test locally

$
0
0

@sourabkumarkeshri wrote:

Hello All,

I am trying to run mattermost load test locally.I am done with the setup.

When running loadtest all,I get the following error.

{“level”:“error”,“msg”:“Failed to initialize config”,“fields”:[{“Key”:“error”,“Type”:25,“Integer”:0,“String”:"",“Interface”:{}}]}

If someone can share their “loadtestconfig.json” . file . or help me with the issue,it would be great.

Posts: 1

Participants: 1

Read full topic

Docker Container lose settings after Update

$
0
0

@kaiehlig wrote:

Hey Folks,

we are having a strange issue
If we update our Mattermost-Dockercontainer we lose all our settings and Usercontent.
We followed the Documentation and mapped the required path out of the Container to persist them.

We did the last 2-3 Updates with these issue and it persist, so it is not a Version issue it looks like a general issue.

These are our volumes:
volumes:
- /data/app/mattermost/config:/mattermost/config:rw
- /data/app/mattermost/data:/mattermost/data:rw
- /data/app/mattermost/logs:/mattermost/logs:rw
- /data/app/mattermost/plugins:/mattermost/plugins:rw
- /data/app/mattermost/client-plugins:/mattermost/client/plugins:rw
- /etc/localtime:/etc/localtime:ro

We are using Dockerimage from https://hub.docker.com/r/mattermost/mattermost-team-edition

Any hints?

Best regards
Kai

Posts: 1

Participants: 1

Read full topic

Jira plugin can't create issues

$
0
0

@netgineer wrote:

Summary

The Jira plugin works OK when posting events to channel but hangs up while trying to create or attach to the issue.

Steps to reproduce

Mattermost Version: 5.13.1 with preinstalled Jira plugin
JIRA cloud instance
Configure plugin and Jira according to the guide

Expected behavior

Successful creation of issues.

Observed behavior

I’ve successfully configured the plugin to post events from Jira Cloud to Mattermost channel, but after installing it as an application I can’t configure it to create tasks in Jira.

When I enter /jira connect command and click on the link bot gives me link with the url https://<MM-URL>/plugins/jira/user/connect. I successfully connect my jira account and everything looks good. But when I want to create an issue from any message, ruight-click on it and select “create jira issue” I receive a pop-up window with endless “Loading…” message.
In the mattermost logs i see the following error:

{"level":"error","ts":1564400037.2892468,"caller":"mlog/sugar.go:23","msg":"ERROR: ","plugin_id":"jira","Status":"500","Error":"user not found","Host”:”<MM-URL>”,”RequestURI":"/plugins/jira/api/v2/get-create-issue-metadata","Method":"GET","query":""}

Posts: 4

Participants: 2

Read full topic

Impossible to update a post through API with bot account?

$
0
0

@alex_enyway wrote:

Do I get it right that bot accounts can only create posts, but not update them?

I can only assign the rights for post:all and post:channel. When I try to make a PUT request with a bot account, I get status 403 with message You do not have the appropriate permissions.

So when I want to update a post following a click on an interactive button, I would have to use a regular user with appropriate permissions for the API request?

Posts: 1

Participants: 1

Read full topic

Create JIRA Ticket integration hangs forever

$
0
0

@gubbins wrote:

Summary

After apparently successful /jira connect, I tried the “Create JIRA Ticket” action on a post. It opens a dialog box which displays “Loading…” and never finishes Loading.

Steps to reproduce

  • Mattermost 5.13.2
  • JIRA plugin enabled and installed with JIRA server (not cloud) version v7.8.4
  • /jira connect, log in, apparently all successful
  • select “Create JIRA Ticket”

Expected behavior

Dialog box with JIRA issue fields

Observed behavior

I waited about 15 minutes but the dialog was still “Loading…”.

There is nothing in the mattermost logs at INFO level. There is almost no CPU usage on the mattermost server.

I wonder if it is trying to enumerate all JIRA projects or other metadata. That could take a while (we have a lot of JIRA projects).

Posts: 3

Participants: 2

Read full topic


Native support for voice, video or screen sharing?

$
0
0

@steveharman wrote:

Hi,
Could someone clarify for me whether Mattermost has “its own” voice, video & screen sharing features, or are these functions purely integrations with other services such as Zoom to handle the calls?

Thanks,

Steve

Posts: 1

Participants: 1

Read full topic

Non minified plugin development

$
0
0

@lsenseney3 wrote:

Hi!

I am working on a plugin for Mattermost, and would like to be able to debug it in Chrome. However, the file is minified, and very unreadable.

I tried to set webpack to development mode, and it still isn’t readable and gives me the message: "Uncaught EvalError: Refused to evaluate a string as JavaScript because ‘unsafe-eval’ is not an allowed source of script in the following Content Security Policy directive: "script-src ‘self’ cdn.segment.com/analytics.js/"."

Posts: 1

Participants: 1

Read full topic

JIRA plugin no longer posts for closed tickets (but does for assigned tickets)

$
0
0

@gubbins wrote:

Summary

The JIRA plugin integration allows JIRA to post to mattermost if a ticket is “updated”. This would previously include a post if a ticket is closed, but this no longer happens.

Steps to reproduce

  • Mattermost 5.13.2
  • JIRA plugin enabled
  • A working webhook configured in JIRA server (not cloud) v7.8.4, with only “Issue: updated” selected under the events (all other checkboxes in the events section unselected)
  • Create a ticket covered by the webhook’s query, assign it to someone, and close it

Expected behavior

  • No post when the ticket is assigned
  • Expected a post when the ticket is closed or “resolved”

Observed behavior

  • A post when the ticket is assigned. This seems to be new, but the docs do mention this as an “update”, so it also seems valid.
  • No post when the ticket is closed. Confirmed with numerous tickets on different projects and webhooks.

The important thing for us is to restore the post for closed tickets. Ideally we’d be able to filter out the posts for assigned tickets if we choose to, but that’s less important.

Posts: 1

Participants: 1

Read full topic

Cannot connect to the postgresql database using mattermost cli

$
0
0

@vinci wrote:

Summary

Unable to connect to postgresql database lying on a different container than the database

Steps to reproduce

I’m using the mattermost command.
mattermost user create --email test2@email.com --username testatene --password Password

Observed behavior

{“level”:“error”,“ts”:1564644335.8744648,“caller”:“sqlstore/supplier.go:236”,“msg”:“Failed to ping DB retrying in 10 seconds err=dial tcp 127.0.0.1:5432: connect: connection refused”}

Is there any way I can change the postgresql path? The container is reacheable through the “db” name set in docker-compose, but I haven’t found a way to set that path.

Thanks in advance!

Posts: 1

Participants: 1

Read full topic

Keine Verbindung unter Android

$
0
0

@fbfm wrote:

Hallo zusammen,

ich habe die aktuelle Mattermostversion 5.13.2 installiert. Es ist ein SSL Zertifikat im Einsatz.
Der Zugriff über Browser Win/Mac und der iOS App funktioniert fehlerfrei. Aber die Android App zeigt
“Cannot connect to the server.”. Das Problem besteht nur bei Android Geräten!!

Hat jemand eine Idee was hier gemacht werden kann?

Posts: 1

Participants: 1

Read full topic

Hello everybody. Push Notification iOS Exemple

$
0
0

@dangquan09 wrote:

Hello,

While having some problem to run the self-hosted push notifications service. I wanted to know what the Mattermost’s JSON payload for an iOS push notification looked like, but unfortunately, I found nothing on the Internet.

So I was just wondering what the JSON payload send by the Mattermost push notifications service looked like for a new post and an edited one.

Also, I want to know if the “content-available” attribute is already present, and if not, if we could add it.

Thanks.

Posts: 1

Participants: 1

Read full topic

Not able to install Mattermost Jenkins integration plugin

$
0
0

@sandeepsasikumar15 wrote:

Hello @amy.blais,

I am trying to install the Jenkins plugin in mattermost so that the Mattermost channel receives updates from Jenkins when a build is successful. When trying to install the plugin in mattermost I am getting the following error. Could you please let me know why is it so?

"Encountered an error when extracting the plugin. Review your plugin file content and try again. "

Thanks in advance.

Posts: 2

Participants: 2

Read full topic


Mattermost webhook plugin post error - dail tcp i/o error

$
0
0

@tejas.designer07 wrote:

Summary

I am unable to make any post request from a plugin. dail tcp IP i/o error

Steps to reproduce

I have installed Mattermost 5.13.2 on a DMZ (192.168.x.x:8067) behind a Firewall using NAT. I am able to use Mattermost as expected from internet using my public IP/hostname as well as internal.
I installed a plugin(RemindBot) but none of the buttons work after a reminder is sent.

I changed the config file to reflect the following:

"EnableInsecureOutgoingConnections": true,
"AllowedUntrustedInternalConnections": “192.168.x.x”,

I still am unable to make it work.

Observed behavior

Following is the error that is generated:

{“level”:“error”,“ts”:1564767183.8125181,“caller”:“mlog/log.go:172”,“msg”:“Action integration error”,“path”:"/api/v4/posts/nrct1bbkdpyqtm41jdfyanhmaa/actions/feqngh9b1jyetpqianhwwcmkmo",“request_id”:“4ypkej9zdpgmpmpcrq96jfxkuw”,“ip_addr”:“10.190.x.x”,“user_id”:“c859kpm4e38odqttj7y9cz367r”,“method”:“POST”,“err_where”:“DoActionRequest”,“http_code”:400,“err_details”:“err=Post https://{hostname}:8067/plugins/com.github.scottleedavis.mattermost-plugin-remind/delete: dial tcp PUBLIC_IP:8067: i/o timeout”}

Posts: 1

Participants: 1

Read full topic

More Granular Session lengths for SSO authentication

Sort Unread Messages According to Recency

$
0
0

@ahmaddanial wrote:

Problem Definition

  • The current behavior of the Unread Message Indicator shows the unread messages in an alphabetical order by default regardless of the timing when the messages are received
  • This can potentially cause an issue when a user is communicating with multiple users / channels at a time, not knowing which 1-1 / channel has the most recent unread message and which one to respond to first

Suggested Solution

Propose a new unread message indicator feature that allow users to configure it to be sorted alphabetically or based on recency

Posts: 1

Participants: 1

Read full topic

Admin locked out with no email enabled

$
0
0

@McMa wrote:

Hello everybody,
I am running Mattermost (5.0.0.7) on a QNAP NAS with no email communication enabled and I locked my admin account out.

I connected via ssh to the folder where (I believe) the server is installed to try and use the CLI tools but the command “mattermost” is not recognized.

The folder where I’m looking for the installation has the following contents:

docker-compose.yml images/ log/ mattermost.sh* NOTICE.txt volumes/ flags/ LICENSE.txt mattermost.conf nginx/ utils/

Is there a way to reset my admin’s password?

PS: I am not very familiar with docker (or with qnap and .qpkg), does the .yml file mean mattermost is running on a container? If so, could I access said container like this?

Posts: 1

Participants: 1

Read full topic

Cannot open dialog

$
0
0

@securisec wrote:

I am not sure what I am doing wrong, but I cant seem to open the dialog, but I am getting a {status: 'OK'} response…

Mattermost Version: 5.13.2

The post from the slash command is ephemeral

My slash command is working fine, and so is the interactive button (this is what should trigger the dialog to open).

Here is my code for the dialog to trigger. This req param is being passed from the action from clicking a button.

module.exports.addEmail = (req) => {
	let body = req.body;
	let data = JSON.stringify({
		trigger_id : body.trigger_id,
		url        : resolve(config.MM_ACTION_URL, '/mattermost/dialog'),
		dialog     : {
			title       : 'Email',
			callback_id : 'add_email',
			elements    : [
				{
					display_name : 'Email',
					name         : 'email',
					type         : 'text',
					subtype      : 'email',
					placeholder  : 'placeholder@example.com'
				}
			]
		}
	});
	mmRequest('post', 'actions/dialogs/open', data)
		.then((res) => {
			console.log(res);
		})
		.catch((error) => console.log(error));
};

On the server side, this is my code to add a little more context to my workflow.

app.post('/mattermost/actions', (req, res) => {
	// console.log(req.body);
	let action = req.body.context.action;
	if (action === 'add_email') {
		dialog.addEmail(req);
	}
});

app.post('/mattermost/dialog', (req, res) => {
	console.log(req.body);
	res.sendStatus(200);
});

And the function that is making the API call to the mattermost server is

module.exports.mmRequest = (method, url, data = {}) => {
	let c = {
		method  : method,
		baseURL : resolve(config.MATTERMOST_URL, 'api/v4/'),
		url     : url,
		data    : data,
		headers : {
			Authorization : `Bearer ${config.MM_ACCESS_TOKEN}`
		}
	};
	return new Promise((resolve, reject) => {
		Axios(c)
			.then((res) => {
				resolve(res.data);
			})
			.catch((error) => reject(error.response));
	});
};

In the console.log(res), I get a status OK message, but the dialog doesnt open… What am I doing wrong?

Posts: 1

Participants: 1

Read full topic

Viewing all 6408 articles
Browse latest View live