Hello,
Hope you are doing good. We are looking to develop a interactive dialog which would provide the user the dropdown options to select from, as per the Mattermost documentation we are trying to open dialog using the json from plugin(mmpy_bot), but nothing seems to be happening. Basically trying to understand how can we get the trigger id and url as mentioned below. is URL is call back url of web hook id we create for the channel.? Could you please help understand the complete steps to open and submit the user dialog? Do we need to write server side integration , if so what are the steps to create a Mattermost development server instance for this to work… As I said we just started using mmpy_bot python libraries present in the Mattermost site to develop the BOT ,so any help would greatly help us?

{
“trigger_id”:“nbt1dxzqwpn6by14sfs66ganhc”,
“url”:“http://localhost:5000/dialog_submit”,
“dialog”:{
“callback_id”:“somecallbackid”,
“title”:“Test Title”,
“icon_url”:“http://www.mattermost.org/wp-content/uploads/2016/04/icon.png”,
“elements”:[
{
“display_name”:“Display Name”,
“name”:“realname”,
“type”:“text”,
“subtype”:"",
“default”:“default text”,
“placeholder”:“placeholder”,
“help_text”:“This a regng up the server instanc ular input in an interactive dialog triggered by a test integration.”,
“optional”:false,
“min_length”:0,
“max_length”:0,
“data_source”:"",
“options”:null
},

1 post - 1 participant

Read full topic

Hi, I have the gyazo plugin installed but I don’t know how to use it.

1 post - 1 participant

Read full topic

Hi,

I want to integrate/install mattermost community version on the cpannel and then want to use for my application, I tried it on the ubuntu 18.04 it works absolutely fine but when I came to the cpannel it does not shows any reference document regarding it, so pls can you help me out in that.

Thanks
Abhishek

1 post - 1 participant

Read full topic

Hello,
Is there a plugin to get client-side gif picker in the web app ?
My mattermost instance has no access to internet, so I was wondering if there was some way to get gif searching client-side, maybe with a bundled javascript that the server would provide to the browser.
I think this would be interesting for all those with a server behind a corporate proxy.
Thanks

1 post - 1 participant

Read full topic

What is the Salt value of passwords on mattermost?

1 post - 1 participant

Read full topic

Helo.
After upgrade from 5.25 to 5.27 users cant view channels bar on left. How can i fix this issue?

Screenshot 2020-09-17 201547256×724 6.38 KB

2 posts - 2 participants

Read full topic

bonjour,
j’aimerais savoir combien de personnes peuvent être connectées en même temps pour une vidéoconférence avec mattermost.
je ne trouve cette info nulle part malgré mes recherches.
merci de votre réponse et à bientôt

1 post - 1 participant

Read full topic

Is it possible to run Mattermost from a sub-folder / context?

I want to run Mattermost behind a Apache2 reverse proxy server and I cannot create sub-domains. So for example I want to access Mattermost as https://example.com/mattermost. I cannot use a sub-domain for example https://mattermost.example.com

Is this supported? Are there configuration examples for Apache2 that shows this?

1 post - 1 participant

Read full topic

I am new to Mattermost. Installing it for the first time on CentOS 7. As per installation guide I am editing config.json. I put in SiteURL and database credentials.

  "ServiceSettings": {
    "SiteURL": "https://mattermost.1.1.1.3.nip.io",
    "WebsocketURL": "",

And database settings

  "SqlSettings": {
    "DriverName": "postgres",
    "DataSource": "postgres://mattermost:secret@db:5432/mattermost?sslmode=disable&connect_timeout=10",
    "DataSourceReplicas": [],

When I run mattermost, I get an error message that the config file is not valid

[mattermost@mattermost mattermost]$ ./bin/mattermost 
Error: failed to load configuration: failed to load: invalid config: Config.IsValid: model.config.is_valid.file_driver.app_error, 
Usage:
  mattermost [flags]
  mattermost [command]

The file is pretty large with many options. There is no log file. Is there a way to know what part of the file is not valid? Is there an editor / IDE of some sort to compile the file?

1 post - 1 participant

Read full topic

Summary

Themed button colors in Mattermost’s default dark theme are mismatched.
Mattermost Version: 5.27.0

Steps to reproduce

Use a mattermost client with the default dark theme active. Submit a post containing a button in an attachment, setting “style” to “danger” or “primary” in the button’s configuration (like Slack).

Expected behavior

Button is unstyled (like previous versions), or button is styled according to the Mattermost theme

Observed behavior

The mattermost dark theme has the buttons styled rather brightly!

Primary:

(Can’t post danger example - new users can only post one attachment)

1 post - 1 participant

Read full topic

Hello,
I like the fact that an ordered list (numbered list) is automatically created and numbers are growing automatically (https://docs.mattermost.com/help/messaging/formatting-text.html#lists). If I write:
1. text
1. text

We’ll see

1. text
2. text

Our use case is that we use these ordered lists to answer every single points in a specific thread. For example:

1. What’s the day today?
2. What is the colour of Mars?
3. What’s your name?

Somebody could reply:

1. Monday
2. Red
3. Tom

The problem is that somebody might want to reply only to 1. and 3. , not on 2.:
1. Monday
3. Tom

Currently, it’s not possible, we’ll see:

1. Monday
2. Tom

Our workaround is either to write 2 messages:

1. Monday

and then:
3. Tom

Or to include an empty line:

1. Monday
3. Tom

Is there an easier/cleaner solution? Maybe an option to disable the force the manual numbering for example? Like:

/force-order
1. Monday
3. Tom

2 posts - 1 participant

Read full topic

I’ve posted about this in the past but that post is no longer getting any responses.

This problem is driving me to insanity and I don’t get what’s going on.

Setup:
Mattermost Host: CentOS 7 running MM 5.16.0
MySQL: Separate host
Proxy: CentOS 7 running nginx as the proxy

Problem:
As soon as I upgrade it breaks the notifications. Usually it’ll still send the banner notifications and the notifications to the lock screen but the badge indicator only works maybe 10% of the time.

Troubleshooting:
I’ve done everything in the aforementioned link. In addition, i’ve built an entirely new proxy that was originally an Apache proxy and replaced it with an nginx proxy.

I built a whole new VM for mattermost running Ubuntu 20.04 (just today). As soon as I point the proxy at the new server, the badge icon indicator breaks. All users but 1 are iOS. Problem persists regardless of OS. Every once in a while it’ll work, but there is seemingly no consistency. The banner notifications are also hit or miss - they’ll work and then just not work.

What am I missing here? I want to love Mattermost, i really do. And, other than this stupid issue, I love this platform. But … i’ve been chasing this for i think 2 years now and nothing. The absolute moment I switch over, it breaks.

Any additional ideas?

3 posts - 2 participants

Read full topic

Problem

You’re ready to upgrade to Mattermost Enterprise Edition but are running Mattermost with Gitlab Omnibus

Solution

1. Prepare your Gitlab Server

First, get your Gitlab server ready by making a backup. Then, configure PostgreSQL to listen on the right IP address.

1.1 Make a Backup

First thing to do is backup your Gitlab instance using the instructions here. If you haven’t already, set up automated backups as well.

1.2a Configure PostgreSQL for remote connections

If want to continue using the Gitlab Omnibus internal PostgreSQL server you’ll need to edit these lines of your gitlab.rb file to allow connections from outside IP addresses.

postgresql['listen_address'] = '*'
postgresql['trust_auth_cidr_addresses'] = ['127.0.0.1/32', '10.0.2.2/32']

Replace 10.0.2.2 with the IP address of the server that will be hosting the Mattermost

1.2b Export Mattermost Database

If you want to move the Mattermost database to another server as well, export your data from the mattermost_production database using pg_dump, then import it using psql, e.g.:

# on the Gitlab server
pg_dump -U gitlab_mattermost -h 127.0.0.1 mattermost_production > mattermost_production.sql

# on the new Mattermost PostgreSQL server
psql -U mmuser -h 127.0.0.1 -f mattermost_production.sql

1.3 Disable Mattermost in Gitlab

In your gitlab.rb set these values to false:

• mattermost['enable']
• mattermost_nginx['enable']

Then run gitlab-ctl reconfigure

2. Install Mattermost EE on the other server

Next, install Mattermost Enterprise edition on the other server by following our instructions including setting up Nginx with TLS. Make sure that you install the enterprise edition so that you can install your license later.

3. Migrate Configuration and Data

These steps are for moving the data and configuration to a Mattermost instance on the same server. If Mattermost is going to be on another server the fastest way to do this is to first set up SSH key-based authentication between the Mattermost server and the Gitlab server .

3.1 Copy and Modify Config

First, make a copy of the Mattermost configuration file to make your edits:

sudo cp /var/opt/gitlab/mattermost/config.json /tmp/mattermost-config.json

Since Gitlab configures its Mattermost instance with environment variables, you’ll need to get those from the Mattermost process itself. To do that, first run ps ax | grep mattermost on the Gitlab server. Look for the line that ends with config.json to find the process ID:

12696 ?        SLsl   0:02 /opt/gitlab/embedded/bin/mattermost --config /var/opt/gitlab/mattermost/config.json

In this case, it’s 12696. Next, run this command - replacing 12696 with the process ID you found - to find the environment variables:

sudo strings /proc/12696/environ

Which will output something like this:

OLDPWD=/opt/gitlab/sv/mattermost
PATH=/opt/gitlab/bin:/opt/gitlab/embedded/bin:/usr/local/bin:/usr/local/sbin:/bin:/sbin:/usr/bin:/usr/sbin
PWD=/opt/gitlab/embedded/service/mattermost
SSL_CERT_DIR=/opt/gitlab/embedded/ssl/certs/
MM_GITLABSETTINGS_SECRET=012c377d42f77a30231807939d02dffb9266c3be82c0fb97d052fa4f60aba86b
MM_SERVICESETTINGS_SITEURL=http://mattermost.example.com
MM_PLUGINSETTINGS_DIRECTORY=/var/opt/gitlab/mattermost/plugins
MM_GITLABSETTINGS_TOKENENDPOINT=http://localhost/oauth/token
MM_SERVICESETTINGS_LISTENADDRESS=127.0.0.1:8065
MM_GITLABSETTINGS_ENABLE=true
MM_TEAMSETTINGS_SITENAME=GitLab Mattermost
MM_LOGSETTINGS_FILELOCATION=/var/log/gitlab/mattermost
MM_FILESETTINGS_DIRECTORY=/var/opt/gitlab/mattermost/data
MM_GITLABSETTINGS_AUTHENDPOINT=http://localhost/oauth/authorize
MM_PLUGINSETTINGS_CLIENTDIRECTORY=/var/opt/gitlab/mattermost/client-plugins
MM_SQLSETTINGS_DATASOURCE=user=gitlab_mattermost host=/var/opt/gitlab/postgresql port=5432 dbname=mattermost_production
MM_SERVICESETTINGS_ALLOWEDUNTRUSTEDINTERNALCONNECTIONS= localhost
MM_GITLABSETTINGS_USERAPIENDPOINT=http://localhost/api/v4/user
MM_GITLABSETTINGS_ID=fa11f0173e2ee56852d002fd7a5afed813fcc694caa968c5c2c2c752380b472d
MM_SQLSETTINGS_ATRESTENCRYPTKEY=2d1de20e681b0c5eec0842663b75c703
MM_SERVICESETTINGS_ENABLEAPITEAMDELETION=true
MM_SQLSETTINGS_DRIVERNAME=postgres
GID=992
UID=992

Use the environment variable naming convention described under Environment Variables here to merge these with the config.json file.

3.2 Sync Data

If you’ve got Mattermost configured to use S3 or Minio, skip this step. If you’re using a network share you can skip it but make sure to configure the right path in the Mattermost configuration under FileSettings.Directory

sudo mkdir /opt/mattermost/data/
sudo rsync -aP /var/opt/gitlab/mattermost/data/ /opt/mattermost/data/

3.3 Sync Plugins

Plugins are synced using the same procedure as the data:

# First, empty the existing plugins directories
sudo rm /opt/mattermost/plugins/*
sudo rm /opt/mattermost/client/plugins/*

# Then, rsync both directories
sudo rsync -aP /var/opt/gitlab/mattermost/plugins/ /opt/mattermost/plugins/
sudo rsync -aP /var/opt/gitlab/mattermost/client-plugins/ /opt/mattermost/client/plugins/

4 Finish up

4.1 Test Mattermost

On your new server, run sudo systemctl start mattermost to enable it, then run curl http://127.0.0.1:8065 to verify it’s working.

To test your Nginx configuration, use your hosts file to specify the hostname for your Mattermost server and connect to it in the browser. If you run into problems check your logs for relevant error messages.

Once you can log in, also try uploading files and using plugins to verify that everything is working.

4.1 Adjust DNS

Adjust your DNS records to set the A record for your Mattermost domain to the IP address of your new server Mattermost server, and your new Mattermost server is ready to go

Discussion

Mattermost 5.27.0 allows those running Mattermost Team Edition, which comes with the Gitlab Omnibus, to upgrade to Enterprise Edition with just one click. While you can use this to upgrade to Mattermost EE, the enterprise binary will be overwritten when Gitlab Omnibus is upgraded, so you’ll have to upgrade again.

By following this procedure you have more control over the version of Mattermost server you’re running. Also, by extracting your Mattermost server you make it a lot easier to take advantage of High Availability to provide redundancy to your Mattermost instance. And you eliminate a single point of failure for your infrastructure. (How hard would it be to coordinate getting your Gitlab server back up without Mattermost?)

If you have specific questions about how to migrate your Mattermost Gitlab installation to another server in your application architecture leave a comment and we’ll be happy to help.

1 post - 1 participant

Read full topic

Summary

(Apologies if this is a configuration setting, a duplicate, or expected - have only started seeing this since the update)

It appears that webhooks respond with a 401 if the webhook owner does not have an active session.

Checking for token expiry / generating a new token before a webhook seems to work so far as a fix (even though webhooks don’t use tokens. It also seems that using the login API does not give a token expiry time, and hasn’t for a while)

Steps to reproduce

Mattermost: 5.27.0
Create a new account
Create a new incoming webhook on the account
Use the API to obtain a mattermost token, use the webhook (this should work)
Wait until the token session expires, use the webhook

Expected behavior

Webhook should still work

Observed behavior

Webhook fails with HTTP 401:

{“id”:“api.context.session_expired.app_error”,“message”:“Invalid or expired session, please login again.”,“detailed_error”:"",“request_id”:"…",“status_code”:401}

1 post - 1 participant

Read full topic

Dear Team,

Please let me know how I could prevent download of files from Mattermost Mobile App to Mobile Devices local storage . Is there any setting / configuration on the server side to do so .
Regards ,
Rohan

3 posts - 2 participants

Read full topic

PostgreSQL ended long-term support for version 9.4 in February 2020. Mattermost is officially supporting PostgreSQL version 10 with v5.26 release as PostgreSQL 9.4 is no longer supported. New installs will require PostgreSQL 10+. Previous Mattermost versions, including our current ESR, will continue to be compatible with PostgreSQL 9.4. We plan on fully deprecating PostgreSQL 9.4 In our v5.30 release (December 16th). Please follow the instructions under the Upgrading Section within the PostgreSQL documentation https://www.postgresql.org/support/versioning/.

Questions or concerns?

Let us know by replying to this forum post.

1 post - 1 participant

Read full topic

Problem

You want to set up Prometheus and Grafana monitoring of your Mattermost cluster, but you don’t have more than fifteen minutes.

Solution

1. Configure Mattermost

In the System Console, go to Performance Monitoring and turn it on. Then, install prometheus-node-exporter on your Mattermost server to get hardware performance metrics.

2. Install the Monitoring Docker Compose

Install Docker on a system that can access the Mattermost servers on port 8067, as well as docker-compose and docker swarm. Then, run docker swarm init to initialize the swarm. The current host is added to the swarm automatically.

Then, use git to clone this great docker stack setup

git clone https://github.com/vegasbrianc/prometheus.git

Then edit the file grafana/config.monitoring to set the Grafana administrator password. The default is foobar.

Next, edit prometheus/prometheus.yml to add your Mattermost servers to the node-exporter job and a new job named mattermost Here’s an example for a four node server, plus monitoring for the system running the docker-compose container. I split them into separate jobs for clarity:

  - job_name: 'node-exporter'

    # Install prometheus-node-exporter on your Mattermost app servers as well
    scrape_interval: 5s
    static_configs:
         - targets: ['node-exporter:9100', '172.31.45.9:9100','172.31.45.244:9100','172.31.44.249:9100','172.31.32.51:9100']
  # Mattermost servers have their metrics on port 8067
  - job_name: 'mattermost'
    static_configs:
    - targets: ['172.31.45.9:8067','172.31.45.244:8067','172.31.44.249:8067','172.31.32.51:8067']                                                                                                 

3. Start Monitoring

Run this command to start the containers:

HOSTNAME="<hostname>" docker stack deploy -c ~docker-stack.yml~ prom

Replace <hostname> with the hostname you’d like to use.

Once the services are started, going to http://<hostname>:3000 and log into Grafana with the username admin and the password you set earlier.

Once you’re there, go to Dashboards > Manage. You’ll see there’s already a dashboard that is monitoring the Docker. To import another dashboard, click the Import button, then enter the ID for the dashboard in the text box and click “Import”. On the next screen, select the Prometheus data source. Here are four dashboards to get started:

• Mattermost Performance Monitoring - 2542
• Mattermost Performance Monitoring (Bonus Metrics) - 2545
• Node Exporter Full - 1860
• Node Exporter Server Metrics - 405

When viewing the Node Exporter dashboards, make sure to only select the nodes that end with :9100, and for the Mattermost dashboards select the nodes with :8067.

Discussion

Thanks to containerization and orchestartion that was a lot easier than doing it by hand. As for performance, it’s been running all day on a t2.medium (2vCPU, 4GB RAM) for most of today but the load hasn’t gone above 0.01 even though I’ve been watching it all day.

Also, if you know how to show hostnames instead of IP addresses in Grafana leave me a tip in the comments!

1 post - 1 participant

Read full topic

Hello,
I am currently trying to set up the Jira plugin for Mattermost and I have been running into an issue with trying to create a Jira Issue or attach a comment to a Jira Issue.
I was able to successfully connect my Mattermost account to my Jira account and I am able to receive notifications from Jira. The error that pops up when I try to create an issue is the following message:

method GET is not allowed, must be POST

I understand what the error is, but I’m not sure quite how to fix it. I tried searching online to see if someone ran into a similar issue, but no luck. If you need more info please let me know.

1 post - 1 participant

Read full topic

Summary

When running Ubuntu 18.04 on Raspberry Pi 3B+ and using the command make package to create the package for the mattermost web app (To allow for full customization), it gives an error in the code and aborts.

Steps to reproduce

1: cd /mattermost-webapp/
2: make package (Note: I am running all commands as the root account, from the command line)

Expected behavior

I was expecting that the build would have run and gone through and created the package as the mattermost wiki said that it should, but instead it errored out and failed, even after I completely updated and re-installed everything.

Observed behavior (that appears unintentional)

0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node', '/usr/local/bin/npm', 'run', 'build' ]
2 info using npm@6.14.8
3 info using node@v8.10.0
4 verbose run-script [ 'prebuild', 'build', 'postbuild' ]
5 info lifecycle mattermost-webapp@0.0.1~prebuild: mattermost-webapp@0.0.1
6 info lifecycle mattermost-webapp@0.0.1~build: mattermost-webapp@0.0.1
7 verbose lifecycle mattermost-webapp@0.0.1~build: unsafe-perm in lifecycle true
8 verbose lifecycle mattermost-webapp@0.0.1~build: PATH: /usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/root/mattermost-webapp/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
9 verbose lifecycle mattermost-webapp@0.0.1~build: CWD: /root/mattermost-webapp
10 silly lifecycle mattermost-webapp@0.0.1~build: Args: [ '-c',
10 silly lifecycle   'cross-env NODE_ENV=production webpack --display-error-details --verbose' ]
11 info lifecycle mattermost-webapp@0.0.1~build: Failed to exec build script
12 verbose stack Error: mattermost-webapp@0.0.1 build: `cross-env NODE_ENV=production webpack --display-error-details --verbose`
12 verbose stack spawn ENOENT
12 verbose stack     at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:48:18)
12 verbose stack     at emitTwo (events.js:126:13)
12 verbose stack     at ChildProcess.emit (events.js:214:7)
12 verbose stack     at maybeClose (internal/child_process.js:925:16)
12 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)
13 verbose pkgid mattermost-webapp@0.0.1
14 verbose cwd /root/mattermost-webapp
15 verbose Linux 5.4.0-1018-raspi
16 verbose argv "/usr/bin/node" "/usr/local/bin/npm" "run" "build"
17 verbose node v8.10.0
18 verbose npm  v6.14.8
19 error code ELIFECYCLE
20 error syscall spawn
21 error file sh
22 error errno ENOENT
23 error mattermost-webapp@0.0.1 build: `cross-env NODE_ENV=production webpack --display-error-details --verbose`
23 error spawn ENOENT
24 error Failed at the mattermost-webapp@0.0.1 build script.
24 error This is probably not a problem with npm. There is likely additional logging output above.
25 verbose exit [ 1, true ]```

1 post - 1 participant

Read full topic

Hi All,

I have just started learning the great mattermost chat and I LOVE it.
I have a problem with invitations.

I have set the email correctly and I am able to send emails successfully.
But, When I try to invite a member using email - I am getting a confirmation that the email was successfully sent - BUT when I see the email, There is no invitation link inside it.

That is how I thought it should work - sending a link to join the chat room via email.
I am sure that I have a problem with my settings and I don’t know what I should do?

Please assist me so I will be able to send the invitations from the server with the link inside the email itself.

Thank You!

1 post - 1 participant

Read full topic