This is driving me nuts.
I have a mattermost instance behind nginx on /mattermost.
A lot works, but when chainging the role of a user to admin the client performs a put and nginx returns a 405. I have no clue where to check next. I think I looked everywhere.
Anybody a clue?
Kind regards,
Jeroen Baten
Hi Amy
Thanks for the reply
We already have an API workflow that takes from a production database and updates the MM user database.
This is more so to restrict users ability to change these names via the settings page. Ideally a system setting to disable these fields for non-admin users.
Hi Paul,
thank you for your answer. The mattermost server is running on the same machine as the nginx webserver.
This did not cause the nginx error messages.
But I thought once more about the posted error messages, and figured that it has to do something with the following mattermost config entry:
"ListenAddress": "127.0.0.1:8065"
I removed 127.0.0.1 and the error messages stopped. Thus, my problem is solved.
But unfortunately, I am not very happy with changing this config entry, because it reopens the mattermost server for direct access to the public, i.e. it opened the port 8065 again. But I would like that all requests have to pass the nginx.
I am wondering if anyone knows how to configure nginx and mattermost in a way that all trafic has to pass the nginx server and that only the ports 80 and 443 need to be open?
Can it be that the regular expression in the nginx config file
location ~ /api/v[0-9]+/(users/)?websocket$
needs to be adapted? ( cf. with the above nginx error logs /api/v4/users/status/ids)
I don’t know. Does anyone have an idea?
Thank you very much,
Nils
hmm so what is the whole use of this most people use apps on mobile device it should be added as a default feature.
They do added webrtc but removed in favor of these useless Plugin
Hi @kwoot,
Thanks for reaching out. Would you be open to reviewing this web page and sending us the relevant environment details and logs so we can diagnose this issue?
Hi @Ruflex,
Would you be open to sharing your Jira settings in JIRA > Webhooks, as well as your Mattermost Jira plugin settings in the System Console?
Yes, having the plugin framework also for mobile devices would be nice as well.
Even better would be if the web UI would be a progressive web app so it would be one codebase and not multiple ones.
I have an issue with a slash command.When I try my custom command I have this error:
Command with a trigger of ‘post’ failed
My mattermost server is running on windows in a docker and is configured on http://127.0.0.1:8065
I set the site url to: http://127.0.0.1:8065
I added a slash command with this config:
Request URL : http://127.0.0.1:5000/post
Request Method: POST
I also have a flask server running on http://127.0.0.1:5000/ which has one route
@app.route('/post', methods=['POST', 'GET'])
def post():
data = request.form
print(data)
I added
"EnableInsecureOutgoingConnections": true,
"AllowedUntrustedInternalConnections": "localhost",
to config.json, default.json and config-docker.json
When I try /post in the defaukt Town Square channel I get Command with a trigger of ‘post’ failed
detailed_error: ""
id: "api.command.execute_command.failed.app_error"
message: "Command with a trigger of 'post' failed"
request_id: "a5n1xkch77g9zb9u6a61456age"
status_code: 500
Do you have an idea to solve this ?
Please let me know. I’m nginx.
ex)
a.mydomain.com > nextcloud site
b.mydomain.com > mattermost site
add_header X-Frame-Options "ARROW-FROM http://a.mydomain.com";
add_header Content-Security-Policy "default-src 'self' a.mycomain.com";
Even if I add the above to Mattermost’s nginx, it will be rejected.
It is blank if it is Chrome.
Below is Firefox.
Blocked by content security policy
An error occurred while connecting to b.mydomain.com.
This page has been canceled because it contains content that is prohibited to be read by the security policy.
Regards,
What OS and version is the Mattermost server installed: CentOS Linux release 7.6.1810 (Core)
What is your Mattermost server version: 5.9.0
Are you experiencing the issues with the browser webapp, if so which one: Firefox and Chrome
Are you experiencing the issues with the Mattermost Desktop App, if so what version and OS: Unknown
Are you experiencing the issues with the Mattermost Mobile App, if so what version and OS: Unknown
Can you send a snippet of the Mattermost server logs around the time of the incident:
{“level”:“debug”,“ts”:1554196581.201783,“caller”:“scheduler/scheduler.go:40”,“msg”:“Scheduling Job”,“scheduler”:“PluginsScheduler”}
{“level”:“debug”,“ts”:1554196581.2205625,“caller”:“jobs/schedulers.go:167”,“msg”:“Next run time for scheduler PluginsScheduler: 2019-04-02 11:17:21.220542478 +0200 CEST m=+421.792463082”}
{“level”:“debug”,“ts”:1554196584.432202,“caller”:“scheduler/worker.go:49”,“msg”:“Worker received a new candidate job.”,“worker”:“Plugins”}
{“level”:“info”,“ts”:1554196584.4463892,“caller”:“scheduler/worker.go:78”,“msg”:“Worker: Job is complete”,“worker”:“Plugins”,“job_id”:“uff38xh3uig39nkbbkaht4d6jr”}
{“level”:“debug”,“ts”:1554196608.4991677,“caller”:“web/handlers.go:58”,“msg”:“GET - /mattermost/api/v4/users”}
{“level”:“debug”,“ts”:1554196608.4999979,“caller”:“web/handlers.go:58”,“msg”:“GET - /mattermost/api/v4/analytics/old”}
{“level”:“debug”,“ts”:1554196608.5013506,“caller”:“web/handlers.go:58”,“msg”:“GET - /mattermost/api/v4/teams”}
{“level”:“debug”,“ts”:1554196612.3551257,“caller”:“web/handlers.go:58”,“msg”:“GET - /mattermost/api/v4/users/f963u6rd9trg7jrcfmk563orwh/teams”}
{“level”:“debug”,“ts”:1554196612.355118,“caller”:“web/handlers.go:58”,“msg”:“GET - /mattermost/api/v4/users/f963u6rd9trg7jrcfmk563orwh/teams/members”}
{“level”:“debug”,“ts”:1554196612.4309273,“caller”:“web/handlers.go:58”,“msg”:“GET - /mattermost/api/v4/users/f963u6rd9trg7jrcfmk563orwh/tokens”}
Are you running Mattermost in a container and/or using container orchestration: No
Find out which database they are using. We only support PostgreSQL and MySQL currently: Postgres
WebSocket Issues
Can you send us the following Mattermost server configuration settings:
ServiceSettings.SiteURL:“SiteURL”: “https://dlt.purmerend.nl/mattermost”,
“WebsocketURL”: “wss://dlt.purmerend.nl/mattermost”,
ServiceSettings.ListenAddress: 8065
ServiceSettings.AllowCorsFrom: “dlt.purmerend.nl”
ServiceSettings.WebsocketSecurePort: 443
ServiceSettings.WebsocketPort: 80
Can you send us your Nginx configuration files: yes, But preferable by email.
Can you send us a snippet of your Nginx error logs around the time of the incident:
83.162.200.97 - - [02/Apr/2019:11:10:50 +0200] “PUT /mattermost/api/v4/users/xj1brin847njxnjqxz14wqjcko/preferences HTTP/2.0” 405 166 “-” “Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:66.0) Gecko/20100101 Firefox/66.0” “-”
Would somebody please help me with this? I need some guidance on how to proceed.
Thank you.
Hi @Miguel,
I’ve reached out to our team earlier to look at this but haven’t heard feedback yet, I’ll let you know as soon as I have more details.
I’m not experimented with Gitlab auth setup, but I think you can solve this in 2 different ways.
If your Gitlab server is inside the same Swarm cluster, maybe you could reach Gitlab using an internal Docker network, allowing you to use http instead of https. IIRC you can create an encrypted network in your Swarm, so http would not be insecure inside this internal network.
If you want to stay with https, or if Gitlab is not inside your Swarm cluster, then you need to add your CA’s root cert to the Mattermost container store (not Traefik), as you said.
Hi @Miguel,
Your client does not use SNI. However, without it Mattermost does not know which certificate it should use. (Somewhat related.) Did you try with different browsers?
Hi @rgrubin75,
To add, Mattermost / go uses /etc/ssl/certs/ . You could prepare such a folder to contain your certificates, and then mount the prepared folder using Docker volumes (i.e. hiding /etc/ssl/certs/ contained in the official image).
Hi @kwoot,
Would you be open to sharing your Nginx configuration? You can remove any parts you don’t feel comfortable to share.
Hi @nils-schween,
Using your configuration Mattermost only listens on IPv4 ( 127.0.0.1 ), but nginx’s upstream is localhost , which also resolves to an IPv6 address ( [::1] ). Did you try to use 127.0.0.1 as nginx upstream IP address?
Hi @gloupmer,
Is that flask app running inside the Mattermost Docker container? (If that’s not the case, then Mattermost’s 127.0.0.1 != flask’s 127.0.0.1 . In other words, Mattermost won’t be able to reach the flask app.)
Hi @Ruflex,
Your request body could be missing a required key - webhookEvent .
Hi @desertanwar,
Since this is a third party project, the best option might be to directly contact the maintainer of the plugin (Sean Sackowitz) - maybe you could join our community server and you can DM him there or ask him in a public channel such as Peer-to-peer Help or Developer Toolkit. Other community members and our engineers might be able to help as well in the channels!