Oh…, adblock…
I completely forgot that existence. Thank you!
↧
I can't display statistics
↧
Possible to show all unread message in the iOS badge?
Hi Amy,
Thank you for the reply. As I see, this is currently early stage. Will it cover our user need, with the badge for the iOS app showing all unread messages and not only messages?
Is it possible to prioritise this work if we sponsor this change?
BR
Vlad
↧
↧
Desktop Application Notification sound not working
↧
Push notifications when mattermost tab is closed
(post withdrawn by author, will be automatically deleted in 24 hours unless flagged)
↧
Push notifications when mattermost tab is closed (Chrome, Firefox)
Hi I would like to know if Mattermost send notifications in web browser (Firefox and Chrome) when the tab is closed and the user still logged in.
Cos I don’t receive notification in this case and I would not like to know it’s normal behavior or no
Thanks in advance for your answer
↧
↧
Push notifications when mattermost tab is closed (Chrome, Firefox)
Hi @sylflo, I believe you wouldn’t get notifications if the browser tab is closed.
↧
Desktop Application Notification sound not working
@amy.blais Thanks for the ping. Please note that for the future, you may also ping Dean Whillier (when he will have an account on this Discourse instance). He has pretty strong knowledge in the app and may answer better than me.
@LuckyLuke192 I cannot reproduce from my side. On Windows, could you please remove the cache in %AppData%/Mattermost and let us know if this works.
Otherwise, we are only testing the desktop app with the latest Windows 10 version. The current one is 1809. The one you have is a bit outdated (except if you are on the Long-term Servicing channel - formerly LTSB -).
↧
Web UI displays nothing (other than 3 dots)
I was having lower version of node and that seems to be the probelm. Resolved by reinstalling node 11.
↧
Messages stuck on send
I’m adding a screenshot at the main post.
↧
↧
Chain notifications issue
Group feature doesn’t happen because there is just one message in notification.
↧
Interactive Dialog Dropdowns not working properly on web
What’s the endpoint URL do you sent, I even cannot open interactive dialog， it always complains:
{“id”:“api.context.invalid_body_param.app_error”,“message”:“Invalid or missing dialog in request body”,“detailed_error”:"",“request_id”:“p7furam6m3b43fgcuit5b1ng7a”,“status_code”:400}
↧
Cannot open interactive dialog
Follow: https://docs.mattermost.com/developer/interactive-dialogs.html
When I post a json to URL: http://<mattermost_server>/api/v4/actions/dialogs/open
A dialog cannot open, it get response:
{“id”:“api.context.invalid_body_param.app_error”,“message”:“Invalid or missing dialog in request body”,“detailed_error”:"",“request_id”:“p7furam6m3b43fgcuit5b1ng7a”,“status_code”:400}
The json I post is:
{ "trigger_id": "cjRraGRhaG1tdHI4NXA0aHNvcWdpazk0bmg6ZnltZ3Joa2Zwam54M2tnbjl0dGE5ZDh4Z3k6MTU1NDU0MDY3NTUzMTpNRVlDSVFDcW1hdG0rSVZlc3hkcER5NkZzSmh5VWxLQk9RWEhycFRTUVNiU1JvQ3BzZ0loQUx4eTREc3hYUWx4TE82Rk1yL3g5bjA0YlJjRC9GQnY1Szd5VVFRVm9SYmk=", "url": "", "dialog": { "callback_id": "callid", "title": "dialog title", "elements": [ { "display_name": "Email", "name": "email", "type": "text" } ] } }
↧
Unable to connect to MiniO Server by using v4 signature
For feature requests, please see: http://www.mattermost.org/feature-requests/.
For troubleshooting questions, please post in the following format:
Summary
Unable to connect to MiniO, S3 compatible storage, by using AWS v4 signature
Steps to reproduce
- set AmazonS3SignV2 to false (of course, I know it is default).
- change storage to Amazon S3 and set endpoint and credentials.
- Click ‘Test Connection’
- show ‘Connection unsuccessful: Error checking if bucket exists. - undefined’
- If set AmazonS3SignV2 to true, the connection will establish successfully.
Expected behavior
Successful.
Observed behavior
What did you see happen? Please include relevant error messages and/or screenshots.
Log
Apr 14 04:12:39 v13 mattermost[2497]: HEAD /chatter/ HTTP/1.1
Apr 14 04:12:39 v13 mattermost[2497]: Host: s3.leafia.org
Apr 14 04:12:39 v13 mattermost[2497]: User-Agent: Minio (linux; amd64) minio-go/v6.0.14
Apr 14 04:12:39 v13 mattermost[2497]: Authorization: AWS4-HMAC-SHA256 Credential=**REDACTED**/20190414/us-east-1/s3/aws4_request, SignedHeaders=host;x-amz-content-sha256;x-amz-date, Signature=**REDACTED**
Apr 14 04:12:39 v13 mattermost[2497]: X-Amz-Content-Sha256: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
Apr 14 04:12:39 v13 mattermost[2497]: X-Amz-Date: 20190414T111239Z
Apr 14 04:12:39 v13 mattermost[2497]: #015
Apr 14 04:12:39 v13 mattermost[2497]: HTTP/1.1 403 Forbidden
Apr 14 04:12:39 v13 mattermost[2497]: Connection: close
Apr 14 04:12:39 v13 mattermost[2497]: Accept-Ranges: bytes
Apr 14 04:12:39 v13 mattermost[2497]: Content-Security-Policy: block-all-mixed-content
Apr 14 04:12:39 v13 mattermost[2497]: Date: Sun, 14 Apr 2019 11:12:39 GMT
Apr 14 04:12:39 v13 mattermost[2497]: Server: Minio/RELEASE.2019-04-09T01-22-30Z
Apr 14 04:12:39 v13 mattermost[2497]: Strict-Transport-Security: max-age=15552000; includeSubdomains;
Apr 14 04:12:39 v13 mattermost[2497]: Vary: Origin
Apr 14 04:12:39 v13 mattermost[2497]: X-Amz-Request-Id: 159552DE08BEF9DE
Apr 14 04:12:39 v13 mattermost[2497]: X-Content-Type-Options: nosniff
Apr 14 04:12:39 v13 mattermost[2497]: X-Frame-Options: SAMEORIGIN
Apr 14 04:12:39 v13 mattermost[2497]: X-Minio-Deployment-Id: 71e60e4f-556c-4858-bdc6-6cda5d5801fb
Apr 14 04:12:39 v13 mattermost[2497]: X-Xss-Protection: 1; mode=block
Apr 14 04:12:39 v13 mattermost[2497]: ---------END-HTTP---------
Apr 14 04:12:39 v13 mattermost[2497]: {"level":"error","ts":1555240359.9427152,"caller":"web/context.go:52","msg":"Error checking if bucket exists.","path":"/api/v4/file/s3_test","request_id":"o4h5e76anbyzznanmnwkwc4n1h","ip_addr":"203.141.134.112","user_id":"hjgxkhqkjpn3pmouoakjjfsqww","method":"POST","err_where":"TestFileConnection","http_code":500,"err_details":"Access Denied."}
Versions
Minio
Version: 2019-04-09T01:22:30Z
Release-Tag: RELEASE.2019-04-09T01-22-30Z
Commit-ID: a2e344bf30c7750c0a152f046a70d327f2f5ccf5
Mattermost : mattermost-5.9.0-linux-amd64
p.s.
The MiniO developer says Minio with v4 signature needs path-style access. Is this configurable?
↧
↧
Team Edition vs Enterprise
Found the table comparing the different editions at
https://mattermost.com/pricing-feature-comparison/
↧
Docker Compose Mattermost with nginx Proxy dont work
Summary
Mattermost docker image with nginx proxy dont work
Expected behavior
i install mattermost with docker-compose with this config =
version: “2”
services:
db:
build: db
restart: unless-stopped
volumes:
- ./volumes/db/var/lib/postgresql/data:/var/lib/postgresql/data
- /etc/localtime:/etc/localtime:ro
environment:
- POSTGRES_USER=user
- POSTGRES_PASSWORD=pw
- POSTGRES_DB=mattermost
# 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
# comment out 2 following lines for team edition
# args:
# - edition=team
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
- /etc/localtime:/etc/localtime:ro
environment:
# set same as db credentials and dbname
- MM_USERNAME=user
- MM_PASSWORD=pw
- MM_DBNAME=mattermost
# in case your config is not in default location
#- MM_CONFIG=/mattermost/config/config.json
ports:
- “8000:443”
links:
- db:db
i bring it up wit docker-compuse up -d
my nginx proxy config file =
upstream mattermost {
server 127.0.0.1:8000;
}
proxy_cache_path /var/cache/nginx levels=1:2 keys_zone=mattermost_cache:10m max_size=3g inactive=120m use_temp_path=off;
server {
server_name mydomain;
location ~ /api/v[0-9]+/(users/)?websocket$ {
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection “upgrade”;
client_max_body_size 50M;
proxy_set_header Host $http_host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_set_header X-Frame-Options SAMEORIGIN;
proxy_buffers 256 16k;
proxy_buffer_size 16k;
proxy_read_timeout 600s;
proxy_pass http://mattermost;
}
location / {
client_max_body_size 50M;
proxy_set_header Connection “”;
proxy_set_header Host $http_host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_set_header X-Frame-Options SAMEORIGIN;
proxy_buffers 256 16k;
proxy_buffer_size 16k;
proxy_read_timeout 600s;
proxy_cache mattermost_cache;
proxy_cache_revalidate on;
proxy_cache_min_uses 2;
proxy_cache_use_stale timeout;
proxy_cache_lock on;
proxy_pass http://mattermost;
}
when i go to the site its come nginx bad gateway. i read many instruction but i dont know where is my failure.
in the nginx log file =
connect() failed (111: Connection refused) while connecting to upstream, client:
Thanks Felix
↧
Server worked until I enabled TLS and LetsEncrypt
Server was working until I enabled TLS and LetsEncrypt. Whether using mobile app or web to access I can no longer connect to a working server. I could just edit the config.json back to 8065, but that would defeat the purpose of encrypted communication. I was wodnering if maybe the Dynamic DNS name was black listed so I ran: $ sudo certbot certonly --standalone -d example.com per the following thread Issues with HTTPS/TLS
Currently at a loss as DNS and certificates are not my strong suit hence why I clicked use letsencrypt to handle it lol. I have allowed both 80, 8065 and 443 through the firewall so I know its not LAN issue as the server was working perfectly fine before TLS. Any insight would be grateful!
↧
Desktop Application Notification sound not working
↧
↧
Desktop Application Notification sound not working
+1 good catch. Didn’t know 1709 wasn’t LTSB 
↧
Web Layer for security
Dear All,
I have installed app and db on same server (db is mysql). We are not exposing it to internet but now security team has raised concerns.
If mattermost or any application which is hosted on same server without any extra layer (in my case its only app and db) it will be an risk to all other server which is on same vlan.
Security team says it will be better if we can add web layer which will give some security to the application.
How can we resolve this?
Also, mattermost is hosted on any web server? from my understanding No there is no web server as such, mattemost server install as a single compiled binary file and entire mattermost server is accessible through RESTful web service API.
Thanks in advance
Bharat
↧
Jitsi (Plugin) within Mattermost
@CGonzalo Hello,
We’re still waiting for your solution 
↧