Try to check the board share permission. I had the same issue, but resolved it by giving the correct permission to access the board
↧
Jira plugin 400 Bad Request WebhookEvent missing
↧
Error 405 only in nginx server when trying put of new role
This should cover the Mattermost related part:
location ~ /mattermost/api/v[0-9]+/(users/)?websocket$ {
allow all;
add_header Allow “GET, POST, PUT, HEAD” always;
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;
client_body_timeout 60;
send_timeout 300;
lingering_timeout 5;
proxy_connect_timeout 90;
proxy_send_timeout 300;
proxy_read_timeout 90s;
proxy_pass http://127.0.0.1:8065;
}
location /mattermost/ {
allow all;
add_header Allow "GET, POST, PUT, HEAD" always;
proxy_set_header X-Frame-Options SAMEORIGIN;
proxy_pass http://127.0.0.1:8065;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
}↧
↧
Nginx Error Log: Connection refused
Hi @amy.blais,
thank you very much Amy. This solved my problem! I did not know that localhost also resolves to the IPv6 [::1] address. With this knowledge at hand, the nginx error logs make way more sense to me, since they tell me that a request containing the IPv6 address is refused:
http://[::1]:8065/api/v4/users/status/ids
Once more thank you,
Nils
↧
Slash command failed
When I try with the flask server in the container, I can’t access the server on 127.0.0.1:5000
I added the port 5000 to the container
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
1379bc206848 mattermost/mattermost-preview "/bin/sh -c ./docker…" 17 minutes ago Up About a minute 0.0.0.0:5000->5000/tcp, 0.0.0.0:8065->8065/tcp, 3306/tcp, 33060/tcp, 0.0.0.0:8069->8069/tcp preview↧
Slash command failed
I fixed that issue but still have the command failed
↧
↧
Jira plugin 400 Bad Request WebhookEvent missing
Yes, everything is set up as in the instructions. Even more, integration has partially earned. This is manifested in that in the mattermost began to appear posts on the creation of tasks and subtasks:
https://drive.google.com/file/d/1ZLEvpy-lKV5XAH5hDgC8a0eYeroqyh1l/view?usp=drivesdk
But the changes and comments are still not working, for the same reason. The same error in the log:
{“level”:“debug”,“ts”:1553279684.0300117,“caller”:“app/plugin_api.go:650”,“msg”:“Failed to serve HTTP request”,“plugin_id”:“jira”,“Error message”:“WebhookEvent missing”}
↧
Jitsi mattermost plugin installation error
Hello @amy.blais,
Thanks for your feedback. I was able to get an answer from Sean Sackowitz with DM in mattermost. I did also post it in peer-to-peer Help channel.
Kind regards
Mohammad
↧
Issue with TLS connectivity
Hi Amy, I just tried with Chrome and I get the error ERR_SSL_PROTOCOL_ERROR, and when I try with Firefox I get the error SSL_ERROR_INTERNAL_ERROR_ALERT.
I am not even sure if the server is picking up a certificate from LetsEncrypt. Could that be the error?
Thanks for all the help.
↧
How to disable animated gif
NOt sure if that was the original intent, but in my case, I would like to disable a gif after I saw it.
The problem (annoyance) is once I saw and giggle about it, it always catch my attention until enough messages are done to push it “off the screen”.
The best, I think, would be to have an option to collapse it so it is out of sight.
↧
↧
Announce: deb & rpm packages for Mattermost
Since
Careful: it makes the reader think that Puppet and Chef don’t play well with Deb or RPM packages. Such an idea would be wrong, as installable artefacts and config management are important parts of proper verifiable, repeatable, consistent software management.
↧
High Availability
Same issue here, and yes I’ve already read the guide. Does anyone know how the nodes communicate with each other?
↧
HAProxy High Availability issues
I’m trying to deploy E20 HA cluster of mattermost. I have 2 nodes connected to an HAProxy load balancer but neither of them are communicating. When I go into the High Availability settings to view the cluster, I only see a single node. Can someone help me troubleshoot this? Thanks.
↧
HAProxy High Availability issues
Hi @tuan-anh.le,
Thank you for reaching out.
Would you be open to creating an Enterprise support ticket via: https://mattermost.zendesk.com/hc/en-us/requests/new?
As you do so, please also include any additional relevant information from here.
I’m also happy to help create the support ticket on your behalf if you are open to sharing your email address via a private message.
More information about Enterprise support is here: https://mattermost.com/support/.
Let me know any questions or concerns,
↧
↧
How to disable animated gif
Hi @biohazarus,
Depending on your server version, you should be able to see a collapse button on all images and gifs that you can use to collapse those gifs when you want to.
You could go to Main Menu > Account Settings > Display > Default appearance of image previews > Collapsed, and that way those gifs will be visible only if you click the expand button to display them.
↧
Log files not rotating
Summary
mattermost log file has reached 115,470 lines, and still has not been rotated.
Steps to reproduce
I’m using mattermost v5.8.0, hosting is on aws ec2, in an amazon linux ami.
Expected behavior
mattermost log file is rotated after either 10k lines, or 50k lines. This bug talks about the issue, and quotes old documentation that talked about automatic log rotation, but I can’t seem to find any mention of it in the latest docs.
Observed behavior
I first realised there was a problem when I wanted to check the mattermost version from the linux console:
(tldr is that after every log line output, there is a warning message saying that the log file could not be renamed/rotated)
ec2-user $ /opt/mattermost/bin/mattermost version
{"level":"info","ts":1554364338.4573255,"caller":"utils/i18n.go:79","msg":"Loaded system translations for 'en' from '/opt/mattermost/i18n/en.json'"}
2019-04-04 07:52:18.457732853 +0000 UTC m=+0.243608902 write error: can't rename log file: rename /opt/mattermost/logs/mattermost.log /opt/mattermost/logs/mattermost-2019-04-04T07-52-18.457.log: permission denied
{"level":"info","ts":1554364338.4578655,"caller":"app/server_app_adapters.go:58","msg":"Server is initializing..."}
2019-04-04 07:52:18.457957197 +0000 UTC m=+0.243833226 write error: can't rename log file: rename /opt/mattermost/logs/mattermost.log /opt/mattermost/logs/mattermost-2019-04-04T07-52-18.457.log: permission denied
{"level":"info","ts":1554364338.4646955,"caller":"sqlstore/supplier.go:215","msg":"Pinging SQL master database"}
2019-04-04 07:52:18.464804317 +0000 UTC m=+0.250680347 write error: can't rename log file: rename /opt/mattermost/logs/mattermost.log /opt/mattermost/logs/mattermost-2019-04-04T07-52-18.464.log: permission denied
{"level":"info","ts":1554364338.90649,"caller":"filesstore/s3store.go:82","msg":"Connection to S3 or minio is good. Bucket exists."}
2019-04-04 07:52:18.906661758 +0000 UTC m=+0.692537875 write error: can't rename log file: rename /opt/mattermost/logs/mattermost.log /opt/mattermost/logs/mattermost-2019-04-04T07-52-18.906.log: permission denied
{"level":"info","ts":1554364338.9103534,"caller":"app/license.go:42","msg":"License key valid unlocking enterprise features."}
2019-04-04 07:52:18.910471057 +0000 UTC m=+0.696347115 write error: can't rename log file: rename /opt/mattermost/logs/mattermost.log /opt/mattermost/logs/mattermost-2019-04-04T07-52-18.910.log: permission denied
{"level":"info","ts":1554364338.9135077,"caller":"app/plugin.go:130","msg":"Starting up plugins"}
2019-04-04 07:52:18.9136039 +0000 UTC m=+0.699479944 write error: can't rename log file: rename /opt/mattermost/logs/mattermost.log /opt/mattermost/logs/mattermost-2019-04-04T07-52-18.913.log: permission denied
{"level":"error","ts":1554364339.5401752,"caller":"app/plugin.go:159","msg":"Failed to unpack prepackaged plugin","error":"installPlugin: Unable to install plugin., lstat ./plugins/plugins~: permission denied","path":"/opt/mattermost/prepackaged_plugins/jira-1.1.1.tar.gz"}
2019-04-04 07:52:19.540338592 +0000 UTC m=+1.326214628 write error: can't rename log file: rename /opt/mattermost/logs/mattermost.log /opt/mattermost/logs/mattermost-2019-04-04T07-52-19.540.log: permission denied
{"level":"error","ts":1554364340.1098795,"caller":"app/plugin.go:159","msg":"Failed to unpack prepackaged plugin","error":"installPlugin: Unable to install plugin., lstat ./plugins/plugins~: permission denied","path":"/opt/mattermost/prepackaged_plugins/zoom-1.0.4.tar.gz"}
2019-04-04 07:52:20.110033301 +0000 UTC m=+1.895909377 write error: can't rename log file: rename /opt/mattermost/logs/mattermost.log /opt/mattermost/logs/mattermost-2019-04-04T07-52-20.110.log: permission denied
{"level":"error","ts":1554364340.1101313,"caller":"app/plugin.go:55","msg":"Unable to get available plugins","error":"lstat ./plugins/plugins~: permission denied"}
2019-04-04 07:52:20.110221695 +0000 UTC m=+1.896097777 write error: can't rename log file: rename /opt/mattermost/logs/mattermost.log /opt/mattermost/logs/mattermost-2019-04-04T07-52-20.110.log: permission denied
{"level":"info","ts":1554364340.110705,"caller":"app/server.go:194","msg":"Current version is 5.8.0 (5.8.0/Fri Feb 15 23:00:08 UTC 2019/24f11a12758fe75ce06269be7f9fb7bb790aec43/2af5b29934977d279f119b8237e9f775ff4ca692)"}
2019-04-04 07:52:20.110791798 +0000 UTC m=+1.896667879 write error: can't rename log file: rename /opt/mattermost/logs/mattermost.log /opt/mattermost/logs/mattermost-2019-04-04T07-52-20.110.log: permission denied
{"level":"info","ts":1554364340.1108313,"caller":"app/server.go:195","msg":"Enterprise Enabled: true"}
2019-04-04 07:52:20.110905644 +0000 UTC m=+1.896781683 write error: can't rename log file: rename /opt/mattermost/logs/mattermost.log /opt/mattermost/logs/mattermost-2019-04-04T07-52-20.110.log: permission denied
{"level":"info","ts":1554364340.1109612,"caller":"app/server.go:197","msg":"Current working directory is /opt/mattermost"}
2019-04-04 07:52:20.111037295 +0000 UTC m=+1.896913393 write error: can't rename log file: rename /opt/mattermost/logs/mattermost.log /opt/mattermost/logs/mattermost-2019-04-04T07-52-20.111.log: permission denied
{"level":"info","ts":1554364340.1111264,"caller":"app/server.go:198","msg":"Loaded config file from /opt/mattermost/config/config.json"}
2019-04-04 07:52:20.111198862 +0000 UTC m=+1.897074947 write error: can't rename log file: rename /opt/mattermost/logs/mattermost.log /opt/mattermost/logs/mattermost-2019-04-04T07-52-20.111.log: permission denied
{"level":"info","ts":1554364340.1611774,"caller":"sqlstore/post_store.go:1287","msg":"Post.Message supports at most 16383 characters (65535 bytes)"}
2019-04-04 07:52:20.161294415 +0000 UTC m=+1.947170443 write error: can't rename log file: rename /opt/mattermost/logs/mattermost.log /opt/mattermost/logs/mattermost-2019-04-04T07-52-20.161.log: permission denied
{"level":"error","ts":1554364340.162959,"caller":"app/plugin.go:55","msg":"Unable to get available plugins","error":"lstat ./plugins/plugins~: permission denied"}
2019-04-04 07:52:20.163067928 +0000 UTC m=+1.948943905 write error: can't rename log file: rename /opt/mattermost/logs/mattermost.log /opt/mattermost/logs/mattermost-2019-04-04T07-52-20.163.log: permission denied
{"level":"error","ts":1554364340.1631424,"caller":"app/plugin.go:55","msg":"Unable to get available plugins","error":"lstat ./plugins/plugins~: permission denied"}
2019-04-04 07:52:20.163241854 +0000 UTC m=+1.949117822 write error: can't rename log file: rename /opt/mattermost/logs/mattermost.log /opt/mattermost/logs/mattermost-2019-04-04T07-52-20.163.log: permission denied
{"level":"info","ts":1554364340.1696565,"caller":"app/license.go:42","msg":"License key valid unlocking enterprise features."}
2019-04-04 07:52:20.169704857 +0000 UTC m=+1.955580911 write error: can't rename log file: rename /opt/mattermost/logs/mattermost.log /opt/mattermost/logs/mattermost-2019-04-04T07-52-20.169.log: permission denied
{"level":"error","ts":1554364340.169738,"caller":"app/plugin.go:55","msg":"Unable to get available plugins","error":"lstat ./plugins/plugins~: permission denied"}
2019-04-04 07:52:20.169768402 +0000 UTC m=+1.955644415 write error: can't rename log file: rename /opt/mattermost/logs/mattermost.log /opt/mattermost/logs/mattermost-2019-04-04T07-52-20.169.log: permission denied
This command was run by the ec2-user user. If I run it using the mattermost user, then no errors are shown. However, the log file is still not rotated.
↧
HipChat import of channel did not import into channel
I just tried to import a room from my old HipChat server into my eval-instance of MM.
Something very strange happened though.
All messages written to that room ended up as private messages to/from each user and not in the indicated room in MM…
Example: Message from me to room in HipChat shows as a private message to/from myself in MM.
The room/channel I try to import from HipChat - must that be non-existing in MM? Or have I done something else wrong in my conversion with hipmost followed by a bulk import using the CLI??
Help!!
↧
HipChat import of channel did not import into channel
I’ve now tried it with a different name on the channel to be created in MM, but still no channel created with the imported history…
↧
↧
HipChat import of channel did not import into channel
Hi @jby,
There seem to be some similar bug reports on the Hipmost’s repository:
- https://github.com/orbitalimpact/hipmost/issues/12
- https://github.com/orbitalimpact/hipmost/issues/13
Here are other tools that you could try out:
Would you be able to share any log errors you see, as well as the first couple lines of your Hipchat data file?
↧
HipChat import of channel did not import into channel
@amy.blais:
Regarding the Hipmost bugs: I started out with the recommended gem, but that made me run into a couple of other bugs, so now I’m using the master branch from github, which seems to work (it doesn’t fail at least), but ends up with the described problem…
I started looking at HC2MM, but that requires ssh-access to the MM server, which I have in a docker container, using the https://github.com/mattermost/mattermost-docker which doesn’t have the possibility to enable SSH inside the container… 
I haven’t looked at varna, will do
Anonymized first 4 lines of my HipChat datafile created by Hipmost (Or should it have been the before-Hipmost-conversion-file instead?):
{ "type": "team", "team": { "display_name": "TeamName", "teamname": "", "type": "I", "description": "Description", "allow_open_invite": false } }
{ "type": "channel", "channel": { "team": "teamname", "name": "new_channel_name", "display_name": "DisplayName", "type": "P", "header": "Header" } }
{ "type": "user", "user": { "username": "hipchatadministrator", "email": "admin@company.com", "teams": [] } }```↧
Mobile App(Android) TLS handshake error
I’ve got Mattermost server version 5.9 with configured SSL(my own certificate, issued by rapidssl).
Windows application works fine, IOS application also works fine. But android application cannot connect to server, on the server side in log messages I see:
{“level”:“info”,“ts”:1554454773.874336,“caller”:“http/server.go:1763”,“msg”:“http: TLS handshake error from 176.59.64.125:29159: remote error: tls: unknown certificate”,“source”:“httpserver”}
{“level”:“info”,“ts”:1554454774.1127157,“caller”:“http/server.go:1763”,“msg”:“http: TLS handshake error from 176.59.64.125:39251: remote error: tls: unknown certificate”,“source”:“httpserver”}
{“level”:“info”,“ts”:1554454774.7795985,“caller”:“http/server.go:1763”,“msg”:“http: TLS handshake error from 176.59.64.125:57096: remote error: tls: unknown certificate”,“source”:“httpserver”}
{“level”:“info”,“ts”:1554454775.319641,“caller”:“http/server.go:1763”,“msg”:“http: TLS handshake error from 176.59.64.125:4419: remote error: tls: unknown certificate”,“source”:“httpserver”}
Although thru browser chat works(on Android). This problem affects all Android devices(I’ve tried at least 5).
Here is server configuration:
"ServiceSettings": {
"SiteURL": "https://chat.mydomain.com",
"WebsocketURL": "",
"LicenseFileLocation": "",
"ListenAddress": "XXX.XXX.XXX.XXX:443",
"ConnectionSecurity": "TLS",
"TLSCertFile": "/opt/mattermost/cert/public.crt",
"TLSKeyFile": "/opt/mattermost/cert/private.key",
"TLSMinVer": "1.2",
"TLSStrictTransport": false,
"TLSStrictTransportMaxAge": 63072000,
"TLSOverwriteCiphers": [],
"UseLetsEncrypt": false,
"LetsEncryptCertificateCacheFile": "./config/letsencrypt.cache",
"Forward80To443": true,
The server works directly without proxy.
↧