Quantcast
Channel: Mattermost Discussion Forums - Latest topics
Viewing all 6544 articles
Browse latest View live
↧

About AGPL License

March 18, 2019, 10:54 pm
$
0
0

@Judy wrote:

Hi. I am writing because I am curious about mattermost server license
I am considering using the matermost open source.
But I saw the policy that if I modify the mattermost server source, I have to make public the source because of AGPL.

Here’s what I’d like to revise.

  • When user sign in, I’m going to add my company’s groupware api to mattermost sign in source.
  • And when user sign up, I’m going to authenticate with groupware API.

In this case, it’s inevitable to modify the mattermost server source.
if so, does the AGPL license apply? Or is a MIT license enough?

Posts: 1

Participants: 1

Read full topic

↧
Search

Use Mattermost as separate controls in own app

March 19, 2019, 3:24 am
$
0
0

@mogadanez wrote:

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

Posts: 2

Participants: 2

Read full topic

↧
↧

Calling REST api directly from interactive button

March 19, 2019, 4:01 am
$
0
0

@xlorken wrote:

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.

Posts: 1

Participants: 1

Read full topic

↧

Page Preview Not Loading Pictures

March 19, 2019, 7:20 pm
$
0
0

@RbDev wrote:

Hi all,

I just installed server 5.9.0.

I got few issues picture related.

In this post I will be talking about page preview.

The pictures are not loading.

Cheers

Posts: 1

Participants: 1

Read full topic

↧

Invalid signup link after upgrade

March 20, 2019, 2:18 am
$
0
0

@kavi wrote:

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&amp;s=MEUCIGWdlYOZdClVDJ02bi6BVm8CBLItuwJypk_MRD67lG18AiEA_g7EVrUy_lJ5tzMI5AGCmRGroKL0isGsg2SbgyRCkLM='">
<noscript><meta http-equiv="refresh" content="0; url=/error?message=The+signup+link+does+not+appear+to+be+valid&amp;s=MEUCIGWdlYOZdClVDJ02bi6BVm8CBLItuwJypk_MRD67lG18AiEA_g7EVrUy_lJ5tzMI5AGCmRGroKL0isGsg2SbgyRCkLM="></noscript>
<a href="/error?message=The+signup+link+does+not+appear+to+be+valid&amp;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.

Posts: 2

Participants: 2

Read full topic

↧
↧

[solved] Javascript error in the Chrome when the site url is defined as ip address

March 20, 2019, 2:14 pm
$
0
0

@januzi wrote:

Summary

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.

Steps to reproduce

  1. Cofigure Mattermost to work on ip address
  2. Hide it behind the proxy and set it to work as /directory (I can’t tell if that’s necessary)
  3. Use Chrome

Expected behavior

Chrome should display normal login window and then allow people to send messages, jump from room to room, etc.

Observed behavior

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.

Posts: 1

Participants: 1

Read full topic

↧

Mattermost does not work on 443 (https) - Docker - Error: CONNECTION_REFUSED

March 20, 2019, 4:40 pm
$
0
0

@TatzyXY wrote:

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

Posts: 1

Participants: 1

Read full topic

↧

Is Mattermost suitable for public groups?

March 21, 2019, 7:54 am
$
0
0

@tao wrote:

Hi everyone! I’m considering using Mattermost for an open-source project I work on. Is the free, self-hosted edition of Mattermost suitable for public instances?

I’m asking because I’ve heard that any user can archive channels. This seemed to be the case two years ago. Has it changed since then? Is restricting channel deletion still an enterprise-only feature?

Thank you!

Posts: 2

Participants: 2

Read full topic

↧
Search

Issue with Rollbar (Matterbar) plugin

March 22, 2019, 1:14 am
$
0
0

@Sergiy wrote:

Hi were,

I’m trying to set up the interaction between the Rollbar and the Mattemost (own server) using the plugin Matterbar (https://github.com/Affirm/matterbar)

But after configuring the webhook on Rollbar side and plugin in Mattermost I get aerror message time:

i2019-03-22T09:49:44.154+0200 error plugin/client_rpc.go:326 Plugin failed to ServeHTTP, RPC call failed {"plugin_id": "matterbar", "error": "unexpected EOF"} 2019-03-22T09:49:44.154+0200 debug go-plugin/client.go:844 panic: runtime error: invalid memory address or nil pointer dereference {"plugin_id": "matterbar"} 2019-03-22T09:49:44.154+0200 debug go-plugin/client.go:844 [signal SIGSEGV: segmentation violation code=0x1 addr=0x40 pc=0x98d497] {"plugin_id": "matterbar"} 2019-03-22T09:49:44.154+0200 debug go-plugin/client.go:844 {"plugin_id": "matterbar"} 2019-03-22T09:49:44.154+0200 debug go-plugin/client.go:844 goroutine 26 [running]: {"plugin_id": "matterbar"} 2019-03-22T09:49:44.154+0200 debug go-plugin/client.go:844 main.(Rollbar).eventNameToTitle(0xc000210480, 0xa37aa0, 0xc000210480) {"plugin_id": "matterbar"} 2019-03-22T09:49:44.154+0200 debug go-plugin/client.go:844 /Users/dliu/.go/src/github.com/mattermost/matterbar/server/rollbar.go:120 +0x57 {"plugin_id": "matterbar"} 2019-03-22T09:49:44.154+0200 debug go-plugin/client.go:844 main.(RollbarPlugin).handleWebhook(0xc0001850c0, 0xbd8e80, 0xc0001fdc00, 0xc0000e8800) {"plugin_id": "matterbar"} 2019-03-22T09:49:44.154+0200 debug go-plugin/client.go:844 /Users/dliu/.go/src/github.com/mattermost/matterbar/server/http.go:105 +0x319 {"plugin_id": "matterbar"} 2019-03-22T09:49:44.154+0200 debug go-plugin/client.go:844 main.(RollbarPlugin).ServeHTTP(0xc0001850c0, 0xc0001fdb70, 0xbd8e80, 0xc0001fdc00, 0xc0000e8800) {"plugin_id": "matterbar"} 2019-03-22T09:49:44.154+0200 debug go-plugin/client.go:844 /Users/dliu/.go/src/github.com/mattermost/matterbar/server/http.go:26 +0x99 {"plugin_id": "matterbar"} 2019-03-22T09:49:44.154+0200 debug go-plugin/client.go:844 github.com/mattermost/matterbar/vendor/github.com/mattermost/mattermost-server/plugin.(hooksRPCServer).ServeHTTP(0xc00000bac0, 0xc00020e240, 0x10b3988, 0x0, 0x0) {"plugin_id": "matterbar"} 2019-03-22T09:49:44.154+0200 debug go-plugin/client.go:844 /Users/dliu/.go/src/github.com/mattermost/matterbar/vendor/github.com/mattermost/mattermost-server/plugin/client_rpc.go:352 +0x254 {"plugin_id": "matterbar"} 2019-03-22T09:49:44.154+0200 debug go-plugin/client.go:844 reflect.Value.call(0xc0001e4660, 0xc00000cb38, 0x13, 0xb05cdc, 0x4, 0xc000079f18, 0x3, 0x3, 0xc0001857c0, 0x413167, ...) {"plugin_id": "matterbar"} 2019-03-22T09:49:44.154+0200 debug go-plugin/client.go:844 /usr/local/opt/go/libexec/src/reflect/value.go:447 +0x449 {"plugin_id": "matterbar"} 2019-03-22T09:49:44.154+0200 debug go-plugin/client.go:844 reflect.Value.Call(0xc0001e4660, 0xc00000cb38, 0x13, 0xc000037f18, 0x3, 0x3, 0x12a05f200, 0xc000037f10, 0xc000037fb8) {"plugin_id": "matterbar"} 2019-03-22T09:49:44.154+0200 debug go-plugin/client.go:844 /usr/local/opt/go/libexec/src/reflect/value.go:308 +0xa4 {"plugin_id": "matterbar"} 2019-03-22T09:49:44.154+0200 debug go-plugin/client.go:844 net/rpc.(service).call(0xc000185a00, 0xc00007d130, 0xc000021708, 0xc000021730, 0xc0000d9200, 0xc0001e8220, 0x9dd7a0, 0xc00020e240, 0x16, 0x9ebee0, ...) {"plugin_id": "matterbar"} 2019-03-22T09:49:44.155+0200 debug go-plugin/client.go:844 /usr/local/opt/go/libexec/src/net/rpc/server.go:384 +0x14e {"plugin_id": "matterbar"} 2019-03-22T09:49:44.155+0200 debug go-plugin/client.go:844 created by net/rpc.(Server).ServeCodec {"plugin_id": "matterbar"} 2019-03-22T09:49:44.155+0200 debug go-plugin/client.go:844 /usr/local/opt/go/libexec/src/net/rpc/server.go:481 +0x47e {"plugin_id": "matterbar"} 2019-03-22T09:49:44.155+0200 debug go-plugin/client.go:595 plugin process exited {"plugin_id": "matterbar", "wrapped_extras": "pathplugins/matterbar/server/plugin-linux-amd64pid30284errorexit status 2"} #second try after server restart 2019-03-22T09:49:52.947+0200 error plugin/client_rpc.go:326 Plugin failed to ServeHTTP, RPC call failed {"plugin_id": "matterbar", "error": "connection is shut down"} 2019-03-22T09:49:57.947+0200 error plugin/client_rpc.go:300 Plugin failed to ServeHTTP, muxBroker couldn't Accept request body connection {"plugin_id": "matterbar", "error": "timeout waiting for accept"} 2019-03-22T09:49:57.947+0200 error plugin/client_rpc.go:281 Plugin failed to ServeHTTP, muxBroker couldn't accept connection {"plugin_id": "matterbar", "serve_http_stream_id": 4, "error": "timeout waiting for accept"}

Please help me resolve this issue.
Sergiy

Posts: 1

Participants: 1

Read full topic

↧
↧

Best way to get Slack-only integrations

March 22, 2019, 5:49 am
$
0
0

@mytamhuyet wrote:

We recently migrated from Slack to Mattermost. We are now facing the problem that a bunch of apps that we use (and have no control over) integrate exclusively with Slack. For example, Invision.

What is the best way to get these integrations onto Mattermost? I tried setting up a Slack relay, using Matterbridge to forward everything posted by Invision. However, formatting is mostly lost and the resulting messages are fairly useless.

Is there any generic way to get the messages of integrations and bots posting onto Slack verbatim into Mattermost? Or some other way to handle the Slack integration problem?

Posts: 1

Participants: 1

Read full topic

↧

Unable to ping database during installation

March 22, 2019, 9:28 am
$
0
0

@shea_bb9 wrote:

I’m doing a new installation on a RHEL 7.4 server, I’ve had to manually install postgres-9.2.24 because of company procedures and when I’m testing whether the mattermost server works properly, I get the error that it is unable to ping the db :

{“level”:“info”,“ts”:1553271398.8555436,“caller”:“utils/i18n.go:83”,“msg”:“Loaded system translations for ‘en’ from ‘/opt/mattermost/i18n/en.json’”}
{“level”:“info”,“ts”:1553271398.8557446,“caller”:“app/server_app_adapters.go:58”,“msg”:“Server is initial izing…”}
{“level”:“info”,“ts”:1553271398.8631089,“caller”:“sqlstore/supplier.go:215”,“msg”:“Pinging SQL master dat abase”}
{“level”:“error”,“ts”:1553271398.8687565,“caller”:“sqlstore/supplier.go:227”,“msg”:“Failed to ping DB ret rying in 10 seconds err=pq: Ident authentication failed for user “mmuser””}

Now, I’ve checked whether I can connect to the db with psql and I can, but it completely disregards the password I’ve created for mmuser. I can connect to it by typing anything when it prompts me for the pw… I’ve followed every step and modified the json config file and everything.

Thanks for your help.

Posts: 1

Participants: 1

Read full topic

↧

Mattermost server doesn't work after instalation.Failed to create index Error 1071

March 24, 2019, 4:30 am
$
0
0

@francocool wrote:

After the instalation mattermost can’t start and shows me this errors:

./mattermost
{“level”:“info”,“ts”:1553426325.7105906,“caller”:“utils/i18n.go:83”,“msg”:“Loaded system translations for ‘en’ from ‘/opt/mattermost/i18n/en.json’”}
{“level”:“info”,“ts”:1553426325.71098,“caller”:“app/server_app_adapters.go:58”,“msg”:“Server is initializing…”}
{“level”:“info”,“ts”:1553426325.7225804,“caller”:“sqlstore/supplier.go:215”,“msg”:“Pinging SQL master database”}
{“level”:“error”,“ts”:1553426325.7914166,“caller”:“sqlstore/supplier.go:807”,“msg”:“Failed to create index Error 1071: Specified key was too long; max key length is 1000 bytes”}

Is there any solution?
Thanx.
CentOS 7.0, MariaDB 10.4, apache. PHPMyAdmin

Posts: 1

Participants: 1

Read full topic

↧

Encryption used by mattermost

March 24, 2019, 11:28 am
$
0
0

@vibhi wrote:

What type of encryption is used by mattermost?
if there are encryption is it enabled by default?

Posts: 1

Participants: 1

Read full topic

↧
↧

Unable to get notifications

March 25, 2019, 12:50 am
$
0
0

@sai wrote:

I have installed mattermost-desktop4.2.1 for ubuntu 14.04.
I am unable to get mattermost-desktop notifications and getting errors like this

(mattermost-desktop:4864): libnotify-WARNING **: Failed to connect to proxy

(mattermost-desktop:4864): libnotify-WARNING **: Failed to connect to proxy

(mattermost-desktop:4864): libnotify-WARNING **: Failed to connect to proxy

Posts: 1

Participants: 1

Read full topic

↧

Jira plugin 400 Bad Request

March 25, 2019, 2:45 pm
↧
Search

How to connect Mattermost to GSuite SAML?

March 25, 2019, 3:18 pm
$
0
0

@paulrothrock wrote:

I’m trying to figure out how (or if) Mattermost can be set up with Google’s GSuite SAML system, and it’s asking for two things I’m not sure of.

When I try to log in via SAML I get the app_not_configured_for_user error, which Google says means this:

If an SP sends a NAMEID parameter in the SAMLRequest, then this parameter must be the same as the one configured on the IdP side. Otherwise the SAMLRequest fails with this error.

My questions:

  • Is there a way to capture the SAML request to see what Mattermost is generating?
  • Has anyone gotten Google SAML working?

Thanks!

Posts: 1

Participants: 1

Read full topic

↧

Desktop notification: hide text

March 26, 2019, 8:13 am
$
0
0

@maxxer wrote:

Hi.

In desktop notifications (from website, not apps) I’d like to remove the message text, for privacy reasons: say I’m working at my desk with someone and I don’t want them to read my messages which appear in notifications.

I did some search, here and on github, but I didn’t find a way to disable (like you do for mobile notifications!). Is it correct? If true, where should I raise the problem? Is Github issue ok?

thanks

Posts: 3

Participants: 2

Read full topic

↧
↧

Issue with TLS connectivity

March 26, 2019, 9:27 am
$
0
0

@Miguel wrote:

Hi

I am able to connect to my mattermost server no problem when connecting to port 8065. I have then changed the config as the document says using the system console.

This is my config.

{
“ServiceSettings”: {
“SiteURL”: “https://myserver.com”,
“WebsocketURL”: “”,
“LicenseFileLocation”: “”,
“ListenAddress”: “:443”,
“ConnectionSecurity”: “TLS”,
“TLSCertFile”: “”,
“TLSKeyFile”: “”,
“UseLetsEncrypt”: true,
“LetsEncryptCertificateCacheFile”: “./config/letsencrypt.cache”,
“Forward80To443”: true,

I then restart the server but I can’t connect to port 443. I have looked at the mattermost.log file and this is what I find:

{“level”:“info”,“ts”:1553614868.050396,“caller”:“http/server.go:1763”,“msg”:“http: TLS handshake error from 172.16.1.40:2745: acme/autocert: missing server name”,“source”:“httpserver”}
{“level”:“info”,“ts”:1553614868.0865338,“caller”:“http/server.go:1763”,“msg”:“http: TLS handshake error from 172.16.1.40:24791: acme/autocert: missing server name”,“source”:“httpserver”}
{“level”:“info”,“ts”:1553614869.8381982,“caller”:“http/server.go:1763”,“msg”:“http: TLS handshake error from 172.16.1.40:14260: acme/autocert: missing server name”,“source”:“httpserver”}

I have checked and there is no ./config/letsencrypt.cache file, but it doesn’t say anywhere that I should create it.

Also, I have not signed up with Let’s encrypt, but I don’t think I need to either…

Any help would be appreciated.

Thank you.

Posts: 1

Participants: 1

Read full topic

↧

Build your own Mattermost apps? Push proxy update is required

March 26, 2019, 12:15 pm
$
0
0

@eric wrote:

To continue receiving push notifications on Android devices, organizations building their own Mattermost apps must update their push proxy and migrate to Firebase Cloud Messaging (FCM) before April 11, 2019.

Google has deprecated the Google Cloud Messaging (GCM) service, and the GCM server and client APIs will be removed.

Details and instructions can be found here.

Posts: 1

Participants: 1

Read full topic

↧

The website freezes

March 27, 2019, 7:00 am
$
0
0

@osamaesmail wrote:

the website freeze when the user is joined to 2k channels.
and I want to embed each channel to a separate html page
How I can solve that ?

Posts: 1

Participants: 1

Read full topic

↧
Viewing all 6544 articles
Browse latest View live
Search