Hi @amy.blais ,
Thanks for reply, I have instructions to install NGNIX.
But I am not sure it will act as proxy server or web server if I will install this.
Our security team says the I have installed app and db for mattermost on same server and its not secure architecture, need to add one web layer into that.
So if I configure NGNIX will it act as web server?
Thanks in advance
Bharat
Thanks, it works now when i bind the nginx proxy to the docker ip from the mattermost app with port 8000.
But i have one question, when i uncomment the arg line with the edition or i wrote the port line, docker-compose write a failure:
ERROR: yaml.parser.ParserError: while parsing a block mapping
in “./docker-compose.yml”, line 24, column 7
expected , but found ‘’
in “./docker-compose.yml”, line 26, column 8
args:
- edition=team
or when i set the ports as in your example.
Steps done:
Tests done:
1 Have another user on another PC send test user a direct message.
2 Have another user on the same PC but on the web app send test user a direct message.
3 Have the test user send another user on the same PC but on the web app. (not related just to experiment)
Only case number 3 produces a notification sound from the browser (Chrome). Both case 1 and 2 did produce pop up banner notification but NO sound.
Edit: I tried to explore the sound settings of my PC and in the Volume Mixer, I see that Mattermost didn’t show up. I think in this case it is the OS fault and I will try to Google the fix for this. What I’ve tried:
I think it’s just because I made a bad copy paste. I wrote ” instead of ".
If you write
ports:
- "80:80"
I think it will works better 
I’ve still got the wrong one.
my docker.yml
version: “2”
services:
db:
build: db
read_only: true
restart: unless-stopped
volumes:
- ./volumes/db/var/lib/postgresql/data:/var/lib/postgresql/data
- /etc/localtime:/etc/localtime:ro
environment:
- POSTGRES_USER=xxx
- POSTGRES_PASSWORD=xxx
- POSTGRES_DB=xxx
# uncomment the following to enable backup
# - AWS_ACCESS_KEY_ID=XXXX
# - AWS_SECRET_ACCESS_KEY=XXXX
# - WALE_S3_PREFIX=s3://BUCKET_NAME/PATH
# - AWS_REGION=us-east-1
app:
build:
context: app
# uncomment following lines for team edition or change UID/GID
args:
- edition=team
# - PUID=1000
# - PGID=1000
restart: unless-stopped
volumes:
- ./volumes/app/mattermost/config:/mattermost/config:rw
- ./volumes/app/mattermost/data:/mattermost/data:rw
- ./volumes/app/mattermost/logs:/mattermost/logs:rw
- ./volumes/app/mattermost/plugins:/mattermost/plugins:rw
- ./volumes/app/mattermost/client-plugins:/mattermost/client/plugins:rw
- /etc/localtime:/etc/localtime:ro
environment:
# set same as db credentials and dbname
- MM_USERNAME=xxx
- MM_PASSWORD=xxx
- MM_DBNAME=xxx
ports:
- “8000:8000”
# in case your config is not in default location
#- MM_CONFIG=/mattermost/config/config.json
I become the same issues by the edition and the port parameter:
expected , but found ‘?’
its run now :). thanks for all your support.
Extended Support Releases or ESRs are intended for organizations who value stability over having the newest features and improvements, or for organizations who have a long internal testing and certification process to undergo when upgrading.
We have been maintaining 4.10 as our current ESR. This version is coming to the end of its lifecycle and we will be implementing version 5.9 as a new ESR. Starting 7/15/2019 we will no longer be backporting fixes to 4.10. Please upgrade your systems to 5.9 l as soon as possible to continue to receive important bug and security updates.
To receive future updates about Extended Support Releases, sign up for our mailing list here.
@WJ.CAI Can you help share the HTTP POST request you send to the API? (you can sanitize sensitive parameters)
We currently have a built-in Gfycat integration, but hope to migrate it to a plugin to more easily support new use cases with a more flexible framework.
Some of the work is partially completed, but we need someone’s help to finish it: https://github.com/mattermost/mattermost-server/issues/10412
Anyone open to helping with this migration? You have an opportunity to work with Go, ReactJS and the Mattermost plugin framework.
Hey everyone,
I’m here because I can’t reach my server after following process https://docs.mattermost.com/install/config-tls-mattermost.html :
Listen Address setting to :443 .
Connection Security setting to TLS .
Forward port 80 to 443 setting to true .
sudo setcap cap_net_bind_service=+ep /opt/mattermost/bin/mattermost done
Use Let’s Encrypt setting to true .
Restart the Mattermost server for these changes to take effect.
My config.json :
“SiteURL”: “mattermost.mydomainname:443”,
“WebsocketURL”: “”,
“LicenseFileLocation”: “”,
“ListenAddress”: “:443”,
“ConnectionSecurity”: “TLS”,
“TLSCertFile”: “”,
“TLSKeyFile”: “”,
“TLSMinVer”: “1.2”,
“TLSStrictTransport”: false,
“TLSStrictTransportMaxAge”: 63072000,
“TLSOverwriteCiphers”: [],
“UseLetsEncrypt”: true,
“LetsEncryptCertificateCacheFile”: “./config/letsencrypt.cache”,
“Forward80To443”: true,
It’s ok when i’m restarting my mattermost service, but on a web browser, nothing works.
In fact, it’s the same problem as the following topic : [SOLVED] Unable to connect to Matermost server when secure connection is Enabled
But in my situation my “Forward80To443” is set to “true”.
Did i miss something ?
Many thanks in advance.
Hello everyone,
We are experiencing an issue on both iOS and Android: only images and pdf files are opened correctly. Other filetypes, such as videos, txt, doc, xmlx just give us an icon (like a regular image) instead of its’ actual content. On the web version however video files and txt are opened correctly. If downloaded from web, doc files can be opened by Word, meaning they are not corrupted. Any thoughts on how to fix it for mobile?
Mobile version 1.15 on both iOS and Android. Server version 5.7.0
I created an SES IAM for SMTP in AWS so MatterMost can use for Email. It has the correct permissions for SES and etc.
When i go to the Admin Matter Most Console and Test the credentials i get Connection Unsuccessful SendMail Failed to Open TLS connection tls first record does not like a TLS handshake.
I am using Port 587
Enabled SMTP Auth is set to true
SMTP username mattermost@testtest.com
SMTP Password (the SES secret)
Connection is TLS
SMTP server is email-smtp.us.east-1.amazonaws.com
What is Wrong here ?
Hi @neposo,
Would you be open to upgrading your mobile app version to the latest? The latest version is v1.17 and we’ll release v1.18 in the next few days.
Hello everyone, Websoket “posted” event not contains “file_ids”
Mattermost 5.9
headers = new Headers();
headers.append(‘Content-Type’, ‘application/json’);
headers.append(‘Authorization’, token`)
fetch(${apiUrl}/posts", {
method: ‘POST’,
headers,
body: JSON.stringify({
“channel_id”: channel_id,
“message”: “message”
“file_ids”: […some array of string]
})
expected something like this (from demo.mattermost.com)
in posted.data.post:
post: “{
“id”:“4oxzetjye7bp9xpafe89uuydsa”,
“create_at”:1555514416955,
“update_at”:1555514416955,
“edit_at”:0,
“delete_at”:0,
“is_pinned”:false,
“user_id”:“er4tfd5877y9u8pxdpput5b9qy”,
“channel_id”:“9eyxmiurx78kirkaz7epg64coc”,
“root_id”:”"
,“parent_id”:"",
“original_id”:"",
“message”:"",
“type”:"",
“props”:{},
“hashtags”:"",
“file_ids[“t8d9wwcs3tdp3gmt7qz3zia8dc”],
“pending_post_id”:“er4tfd5877y9u8pxdpput5b9qy:1555514416850”}”
but get
post: “{
“id”:“eqp7wne44ibdxkf41s85t4hknc”,
“create_at”:1555514666584,
“update_at”:1555514666593,
“edit_at”:0,
“delete_at”:0,
“is_pinned”:false,
“user_id”:“repsxkurspb19fubnf4osu9uyr”,
“channel_id”:“6odgcqrpybgtf8x8y1gk59pt7h”,
“root_id”:”",
“parent_id”:"",
“original_id”:"",
“message”:"",
“type”:"",
“props”:{},
“hashtags”:"",
“pending_post_id”:"",
“metadata”:{}
}"
NO FILE_IDS!
Same in fetch response, no file_ids:
channel_id: “6odgcqrpybg7879y1gk59pt7h”
create_at: 1555514666584
delete_at: 0
edit_at: 0
hashtags: “”
id: “eqp7wne44890xkf41s85t4hknc”
is_pinned: false
message: “”
metadata: {}
original_id: “”
parent_id: “”
pending_post_id: “”
props: {}
root_id: “”
type: “”
update_at: 1555514666593
user_id: “repsxkurs7899fubnf4osu9uyr”
Hi @drj,
Have you tried with port 465 as in the documentation: https://docs.mattermost.com/install/smtp-email-setup.html#amazon-ses?
Hi @bharat8657,
Yes, I asked our security team about this and they recommended looking at installing Nginx for this.
Hi @Sveta,
Do you see issues with uploading files in channels?
Hi @kuryaki,
Here’s our official OAuth documentation: https://docs.mattermost.com/developer/oauth-2-0-applications.html.
Here’s our documentation on access tokens: https://docs.mattermost.com/developer/personal-access-tokens.html.
Our API documentation is here: https://api.mattermost.com/#tag/drivers.
Let us know if any of these docs help clarify what you’re looking for.
Hi @Hindrik-H,
What error messages are you seeing? Are you using Nginx?
I resolved it - what i did, was my AWS SES IAM (smpt) code was written in Terraform. The issue was, it was the wrong credentials because terraform had another set of credentials but i manually deleted the Access Key in AWS and manually added it and kept testing with wrong credentials.
Solved it by removing the Access Key manually from the IAM user i created for mattermost, re-ran Terraform Plan and Apply (gave me a new Access Key and Secret). Then ran terraform output to get the new access key and secret - used those creds and placed it in the mattermost config, kept port 587 by the way and changed it from TLS to STARTTLS - and tested the connection and all came through and worked ( emails were sent).
Thanks Again!