Is it any way ( even if require l lot of work ) to use mattermost as controls in existing app?
strongly say I need only channel control maybe even without headers, since my app will handle it own
I want to show chat panel for some context with dynamic channels
iframe integration is not good decision since it allow navigating inside
Is there any possibility to call REST API interface directly from interactive button? What is the right way to do it?
Right now I’m trying to call an incoming webhook from mattermost message to the same mattermost with little to no success:
Mar 19 06:29:19 Mattermost platform[24988]: {“level”:“error”,“ts”:1552991359.004765,“caller”:“web/context.go:52”,“msg”:“No text specified”,“path”:"/hooks/some_webhook_here",“request_id”:“ihn68c5x9tgjxmesi5ieioi65e”,“ip_addr”:“mm_url”,“user_id”:"",“method”:“POST”,“err_where”:“HandleIncomingWebhook”,“http_code”:400,“err_details”:""}
Mar 19 06:29:19 Mattermost platform[24988]: {“level”:“error”,“ts”:1552991359.0051658,“caller”:“web/context.go:52”,“msg”:“Action integration error”,“path”:"/api/v4/posts/qrebwzy4p7rnzdw4y6egubhgia/actions/pzfip7qwfbge7ba68cgpjy6yae",“request_id”:“nhsa451ad3yzmgm93g8u6u8d3r”,“ip_addr”:“10.239.2.92”,“user_id”:“aiegjz7sjidcjy6j93huedtohc”,“method”:“POST”,“err_where”:“DoActionRequest”,“http_code”:400,“err_details”:“status=400”}
The button in question looks like that:
{ "attachments": [{ "text": "Test", "actions": [{ "name": "button", "integration": { "url": "http://10.239.5.200/hooks/owo7z39xw7rm3f6hs6cowdnnc", "context": ["action": "do_something","text":"zzzzzzzzzzz","username":"myusernamehere"] } } ] } ] }
I’m absolutely not sure about the things I wrote in context and whether this construction should work at all.
Thank you for your question. There are a few FAQ items here, would they be helpful answering your questions?
https://docs.mattermost.com/overview/faq.html#business-questions
Hi @mogadanez,
Would you be open to taking a look at this documentation if it helps: https://docs.mattermost.com/integrations/embedding.html?
I think you didnt understand me what i wanted so I wanted that only known user can dm each other For example in Whatsapp You can only chat with person that has your number or you have that persons number.
Right now in mattermost when you click on + DM it basically shows you all the registered user on the server.is there something can be doen on that side.
I am dying to use mattermost as its just so smooth and I love the UI . It connect faster its just perfect.
I got it, the structure of JSON is
{ "user_id": "", "channel_id": "", "team_id": "", "post_id": "", "trigger_id": "", "type": "", "data_source": "", "context": { "Content-Type": "application/json", "text": "zzzzzzzzzzz" } }
Since context content is on the second layer of JSON I cannot use it as is in incoming webhooks.
I seen it, and options suggested there is not what I’m looking for.
Iframe is closest, but not works for me,
I not want to use fully functional mattermost UI, stronly say i need just chat panel and own routing
for example imagine that I have some own hierarchy structure in My product ( for example Customer, Project etc. ) I want to show only relative chat panel per each entity without full mattermost UI
Hello, @vibhi
Allow me to understand the requirement that you have a little better. In this case, you would like to have a functionality similar to WhatsApp, which will only allow users to chat with users that are added to their contact list (in this case, email). I hope I get this right.
Sample use case:
Can you please confirm if this is what you would like to achieve with Mattermost?
Yes, You are right that is what i want.
After upgrading to 5.6 - using the Gitlab Mattermost installer on Ubuntu 16.04 - we’ve been unable to invite new users.
They are first taken to a normal looking page, with a button labelled “GitLab Single Sign-on”. This button links to:
http://mattermost.mysite.com/oauth/gitlab/signup?d={%22display_name%22%3A%22R+Kal%C3%B8%22%2C%22email%22%3A%22mail%40gmail.com%22%2C%22name%22%3A%22group%22}&t=a4zbfwfjwtip4gukqryz9zsp8ao6bpwoj6894zss9tym5yqaq5e9w5ug9pcbb6nf
curl "http://mattermost.mysite.com/oauth/gitlab/signup?d={"%"22display_name"%"22"%"3A"%"22R+Kal"%"C3"%"B8"%"22"%"2C"%"22email"%"22"%"3A"%"22mail"%"40gmail.com"%"22"%"2C"%"22name"%"22"%"3A"%"22group"%"22}&t=a4zbfwfjwtip4gukqryz9zsp8ao6bpwoj6894zss9tym5yqaq5e9w5ug9pcbb6nf" -H "User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:65.0) Gecko/20100101 Firefox/65.0" -H "Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8" -H "Accept-Language: en-US,en;q=0.5" --compressed -H "Connection: keep-alive" -H "Cookie: ajs_user_id="%"22s5fhdx65mfggde184uhd4zqima"%"22; ajs_group_id=null; ajs_anonymous_id="%"2200000000000000000000000000"%"22" -H "Upgrade-Insecure-Requests: 1"
<!DOCTYPE html><html><head></head>
<body onload="window.location = '/error?message=The+signup+link+does+not+appear+to+be+valid&s=MEUCIGWdlYOZdClVDJ02bi6BVm8CBLItuwJypk_MRD67lG18AiEA_g7EVrUy_lJ5tzMI5AGCmRGroKL0isGsg2SbgyRCkLM='">
<noscript><meta http-equiv="refresh" content="0; url=/error?message=The+signup+link+does+not+appear+to+be+valid&s=MEUCIGWdlYOZdClVDJ02bi6BVm8CBLItuwJypk_MRD67lG18AiEA_g7EVrUy_lJ5tzMI5AGCmRGroKL0isGsg2SbgyRCkLM="></noscript>
<a href="/error?message=The+signup+link+does+not+appear+to+be+valid&s=MEUCIGWdlYOZdClVDJ02bi6BVm8CBLItuwJypk_MRD67lG18AiEA_g7EVrUy_lJ5tzMI5AGCmRGroKL0isGsg2SbgyRCkLM=" style="color: #c0c0c0;">...</a>
</body></html>
From the mattermost.log:
{"level":"error","ts":1553072509.95022,"caller":"web/context.go:60","msg":"The signup link does not appear to be valid","path":"/oauth/gitlab/signup","request_id":"xye65ygdw3fwpj9xd7eo16x6br","ip_addr":"****","user_id":"","method":"GET","err_where":"GetTeamIdFromQuery","http_code":400,"err_details":""}
I’m new to Mattermost, so any explanations or suggestions of what might be going on is much appreciated.
I would like to add my +1 to this idea.
Hi @vibhi,
This is currently not a feature that we support. Would you be open to sharing this idea on our feature request forum here: No it’s not possible, this would be a feature request for https://mattermost.uservoice.com/forums/306457-general?
Now it is 2019. Any progress since 2016? How long does it take to paste 5 SQL statements into Go code?
I know that is why i am here. is there any way that i can achieve something like this its very important by the way
I will create a post on provided link
Hi @kavi,
What Mattermost server version did you upgrade from?
Can you help share your config settings with any confidential details redacted?
On the Chrome Mattermost refuses to load, because there is: “Uncaught TypeError: Failed to construct ‘URL’: Invalid URL”. The problematic line is in the main.js: if(t.SiteURL)return new URL(t.SiteURL).pathname; The Mattermost is hidden behind the Apache proxy. After changing the main.js, so there would be alpha chars in the SiteURL that’s passed into the URL() Mattermost started to work as intended.
Chrome should display normal login window and then allow people to send messages, jump from room to room, etc.
In the Chrome there is only gray screen and in the js console there is as error: “Uncaught TypeError: Failed to construct ‘URL’: Invalid URL” pointing out to the main.js file.
Edit:
Never mind, I’ve found the problem. The guy that was setting the system missed the dot in the ip address. Looks like that Chrome is more strict with the urls than Firefox.
Hello community,
my Mattermost installation (Docker) does not work on 443 (https). I get always “CONNECTION_REFUSED”. Can someone please tell me what I did wrong?
docker-compose.yml
web:
build: web
ports:
- "80:80"
- "443:443"
read_only: true
restart: unless-stopped
volumes:
# This directory must have cert files if you want to enable SSL
- ./volumes/web/cert:/cert:ro
- /etc/localtime:/etc/localtime:ro
environment:
- MATTERMOST_ENABLE_SSL=true
ls -la ./volumes/web/cert
-rwxr-xr-x 1 root root 1911 Mär 20 23:14 cert.pem
-rwxr-xr-x 1 root root 3558 Mär 20 23:14 fullchain.pem
-rwxr-xr-x 1 root root 1704 Mär 20 23:14 key-no-password.pem
docker-compose up
db_1 | AWS_ACCESS_KEY_ID is required for Wal-E but not set. Skipping Wal-E setup.
db_1 | AWS_SECRET_ACCESS_KEY is required for Wal-E but not set. Skipping Wal-E setup.
db_1 | WALE_S3_PREFIX is required for Wal-E but not set. Skipping Wal-E setup.
db_1 | AWS_REGION is required for Wal-E but not set. Skipping Wal-E setup.
db_1 | LOG: database system was shut down at 2019-03-20 23:33:49 UTC
db_1 | LOG: MultiXact member wraparound protections are now enabled
db_1 | LOG: autovacuum launcher started
db_1 | LOG: database system is ready to accept connections
app_1 | Using existing config file /mattermost/config/config.json
web_1 | found certificate and key, linking ssl config
web_1 | ln: /etc/nginx/conf.d/mattermost.conf: File exists
app_1 | Configure database connection...OK
app_1 | Starting mattermost
curl -I https://chat.mychat.de
Failed to connect to chat.mychat.de port 443: Connection refused