@173210 wrote:

$ make test
... snip ...
go test  -run=. -test.v -test.timeout=440s -covermode=count -coverprofile=capi.out ./api || exit 1
api/admin.go:16:2: cannot find package "github.com/alecthomas/log4go" in any of:
    /usr/lib/go/src/github.com/alecthomas/log4go (from $GOROOT)
    /home/root3/go/src/github.com/alecthomas/log4go (from $GOPATH)
... snip ...
make: *** [Makefile:160: test-server] Error 1

After installing those dependencies I had this error:

$ make test
... snip ...
go test  -run=. -test.v -test.timeout=440s -covermode=count -coverprofile=capi.out ./api || exit 1
# _/home/root3/mattermost/api
/tmp/go-build470298366/_/home/root3/mattermost/api/_test/_obj_test/context.go:113: cannot assign "github.com/mattermost/platform/vendor/github.com/nicksnyder/go-i18n/i18n".TranslateFunc to c.T (type "github.com/nicksnyder/go-i18n/i18n".TranslateFunc) in multiple assignment
/tmp/go-build470298366/_/home/root3/mattermost/api/_test/_obj_test/context.go:255: cannot use c.T (type "github.com/nicksnyder/go-i18n/i18n".TranslateFunc) as type "github.com/mattermost/platform/vendor/github.com/nicksnyder/go-i18n/i18n".TranslateFunc in argument to c.Err.Translate
/tmp/go-build470298366/_/home/root3/mattermost/api/_test/_obj_test/websocket_handler.go:27: cannot use conn.T (type "github.com/nicksnyder/go-i18n/i18n".TranslateFunc) as type "github.com/mattermost/platform/vendor/github.com/nicksnyder/go-i18n/i18n".TranslateFunc in assignment
FAIL    _/home/root3/mattermost/api [build failed]
make: *** [Makefile:160: test-server] Error 1

Any idea?

$ uname -srvmo
Linux 4.5.4-1-ARCH #1 SMP PREEMPT Wed May 11 22:21:28 CEST 2016 x86_64 GNU/Linux

Posts: 1

Participants: 1

Read full topic

@lochlannach wrote:

This could be a stupid mistake I'm making, but I'm setting up mattermost currently.

Everytime I try to get email working, I keep getting the error:
[2016/07/21 12:12:37 IST] [EROR] /api/v3/admin/test_email:testEmail code=500 rid=qk77pnxid7bqbntk74a1xep17w uid=wp8u63tgf3fbmrtzd6gd6j9eer ip=... SMTP Server is required [details: Invalid SMTPServer parameter]

I'm using the same settings as my jira+confluence instances

I've tried setting the SMTP Server param to an ip and to a hostname but no luck... It always comes up as invalid.

I'm using this version: 3.1.0 3.1.0

Anyone having a similar issue?

Thanks!

Posts: 1

Participants: 1

Read full topic

@ashere wrote:

I installed MatterMost (self-hosted slack-alternative) on an Ubuntu
14.0.4 server on an AWS free Tier box. After installing MatterMost, I
received a 504 Nginx error. The steps used are
listed in the links below to install and setup MatterMost. The first
link was used to install MatterMost on a AWS box running Ubuntu 14.0.4.
The second link was used when indicated in the first link.

After completely going through the tutorial, I received the following error (by using the URL or "curl" command):
504 Gateway Time-out
nginx/1.4.6 (Ubuntu)

https://www.cameronezell.com/hosting-mattermost-on-aws/
https://docs.mattermost.com/install/prod-ubuntu.html

Any suggestions on how to fix it?

Posts: 1

Participants: 1

Read full topic

@abiosoft wrote:

Summary

I followed the development setup installation for Mac. make test and make run executed successfully but I could not create team or users.

Steps to reproduce

Clone mattermost repo. Run make test and make run then try creating team or user.

Expected behavior

User and team gets created and I can login on the frontend.

Observed behavior

I get this output.

❯ go run mattermost.go -create_team -team_name="test_team" -email="test_team@example.com"
[2016/07/22 15:47:04 WAT] [EROR] Team.IsValid: model.team.is_valid.reserved.app_error, id=atdds9t9k7drxbibf1ntcwb34o

Nothing gets created and I can not login on the frontend.

Posts: 2

Participants: 1

Read full topic

@eyecreate wrote:

I decided to try setting up mattermost with my gitlab installation and am not able to get it running. The only info I've been able to get from the logs is this message printed a lot.

panic: Failed to open sql connection pq: role "gitlab_mattermost" does not exist

Any idea why this is a problem? I've only set the mattermost external url.

Posts: 2

Participants: 1

Read full topic

@bill wrote:

When attempting to upload files above a certain size, users get a 403 error from the server.

Previously, users would get a 413 error. I increased the value of SecRequestBodyLimit in modsecurity.conf and that cleared the 413 error.

I have tested this with files of various sizes to try to see where the limit is for this error. A file with size 6825789 bytes does not produce a 403 error, but a file of size 6871913 does. (I did a grep search in the mattermost install directory for 68\d{5}, but didn't find anything where a number of the form 68XXXXX appeared. Also no results in /etc/*)

Same error regardless of using web interface or desktop client.

The response from the POST request that produces the 403 includes:

You don't have permission to access /api/v3/teams/6..e/files/upload
on this server.

The response from a successful upload is a JSON with the filenames and client_ids.

I suspect this is really an issue with how I have apache2 configured, but I can't seem to find the misconfiguration.

Mattermost version 3.2.0 (Just upgraded. The error existed before upgrading as well.)
Apache/2.4.7 (Ubuntu)
mysql Ver 14.14 Distrib 5.6.31

EDIT: I have a mattermost.conf file in /etc/apache2/sites-enabled which has LimitRequestBody 0 in it.

Posts: 2

Participants: 1

Read full topic

@davetidwell wrote:

Summary

When a user posts a LINK with either http or https to a any site external to the domain on which Mattermost is served sees the link opening in a 'new' browser session with some text on the top left of the screen offering a 'Return to Mattermost'. Opening links on the same DOMAIN as the Mattermost instance resides on open in a closed window; with no option to return to Mattermost. The only way to return to the team is to close the application completely and log back in.

Steps to reproduce

Open a URL which is external to the Matterhost domain/host - you see the 'return to mattermost' link top left
Open a URL which is internal to the Matterhost domain/host - you see the site raw with no option to return to 'mattermost'

Expected behavior

I would expect that the option to 'return to Mattermost' is consistent for any URL's be they 'local' or 'remote'

Observed behavior

As described above. This behaviour has been reproduced by multiple users on our Mattermost instance.

Posts: 1

Participants: 1

Read full topic

@BoonHean wrote:

I've just setup ldap and all seems to be working.

This is my ldap configurations:

   "LdapSettings": {
        "Enable": true,
        "LdapServer": "spkmain01.spkanim.com",
        "LdapPort": 389,
        "ConnectionSecurity": "",
        "BaseDN": "dc=spkanim,dc=com",
        "BindUsername": "spkanim\\testusersg",
        "BindPassword": "password",
        "UserFilter": "(objectCategory=Person))",
        "FirstNameAttribute": "givenName",
        "LastNameAttribute": "sn",
        "EmailAttribute": "mail",
        "UsernameAttribute": "sAMAccountName",
        "NicknameAttribute": "nickname",
        "IdAttribute": "objectGUID",
        "SyncIntervalMinutes": 2,
        "SkipCertificateVerification": true,
        "QueryTimeout": 60,
        "MaxPageSize": 500,
        "LoginFieldName": ""
    },

It seems to synchronized successfully:

[2016/07/30 12:38:24 SGT] [INFO] LDAP Synchronization completed

However, when I tried to sign on with a AD user, I've got the these errors:

[2016/07/30 12:38:34 SGT] [EROR] /api/v3/users/login:findUser code=400 rid=nhnj6ji7uj8cddaeh7hwmodmfw uid= ip=10.0.17.5 User not registered on LDAP server [details: username=spkanim\savio]
[2016/07/30 12:38:38 SGT] [EROR] /api/v3/users/login:findUser code=400 rid=57w7xswijpd89crjenkzap6yqy uid= ip=10.0.17.5 User not registered on LDAP server [details: username=savio]

I've tried a few other users and the results are the same. Is there anyway to see how many users are synced to Mattermost from ldap? I've also gone through the troubleshooting section in the docs but none of that helps. Did I miss anything?

Posts: 4

Participants: 2

Read full topic

@zdvx wrote:

Can anyone advise how to get the Docker image of MM to work with Let's Encrypt? I've already got the LE certificates loaded in /etc/letsencrypt/live/my-domain but I don't know how to get these certificates to be read/seen by MM?

I'm installing the docker image of Mattermost on Ubuntu 16.04. I'm following the instructions at https://docs.mattermost.com/install/prod-docker.html. However, step 3 'Setup TLS' leads to this page https://github.com/mattermost/mattermost-docker#install-with-ssl-certificate and from there, the instructions read

Put your SSL certificate as ./volumes/cert/cert.pem and the private key that has no password as ./volumes/cert/key-no-password.pem. If you don't have them you may generate a self-signed SSL certificate.

MM starts fine if environment: - MATTERMOST_ENABLE_SSL=false in docker-compose.yml

Thanks!

Posts: 1

Participants: 1

Read full topic

@mashedkeyboard wrote:

Hi all,

Having trouble building Mattermost on Ubuntu 14.04 Trusty.

ERROR in ./root.jsx
Module build failed: Error: Cannot remove "babel-plugin-transform-es2015-modules-commonjs" from the plugin list.
    at Object.<anonymous> (/root/go/src/github.com/mattermost/platform/webapp/node_modules/babel-preset-es2015-webpack/index.js:35:11)
    at Module._compile (module.js:413:34)
    at Object.Module._extensions..js (module.js:422:10)
    at Module.load (module.js:357:32)
    at Function.Module._load (module.js:314:12)
    at Module.require (module.js:367:17)
    at require (internal/module.js:20:19)
    at /root/go/src/github.com/mattermost/platform/webapp/node_modules/babel-core/lib/transformation/file/options/option-manager.js:391:22
    at Array.map (native)
    at OptionManager.resolvePresets (/root/go/src/github.com/mattermost/platform/webapp/node_modules/babel-core/lib/transformation/file/options/option-manager.js:387:20)
    at OptionManager.mergePresets (/root/go/src/github.com/mattermost/platform/webapp/node_modules/babel-core/lib/transformation/file/options/option-manager.js:370:10)
    at OptionManager.mergeOptions (/root/go/src/github.com/mattermost/platform/webapp/node_modules/babel-core/lib/transformation/file/options/option-manager.js:330:14)
    at OptionManager.init (/root/go/src/github.com/mattermost/platform/webapp/node_modules/babel-core/lib/transformation/file/options/option-manager.js:488:10)
    at File.initOptions (/root/go/src/github.com/mattermost/platform/webapp/node_modules/babel-core/lib/transformation/file/index.js:223:65)
    at new File (/root/go/src/github.com/mattermost/platform/webapp/node_modules/babel-core/lib/transformation/file/index.js:140:24)
    at Pipeline.transform (/root/go/src/github.com/mattermost/platform/webapp/node_modules/babel-core/lib/transformation/pipeline.js:46:16)
    at transpile (/root/go/src/github.com/mattermost/platform/webapp/node_modules/babel-loader/index.js:14:22)
    at Object.module.exports (/root/go/src/github.com/mattermost/platform/webapp/node_modules/babel-loader/index.js:88:12)
 @ multi main
Child html-webpack-plugin for "root.html":
        + 13 hidden modules

npm ERR! Linux 2.6.32-042stab116.2
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "run" "build"
npm ERR! node v5.12.0
npm ERR! npm  v3.8.6
npm ERR! code ELIFECYCLE
npm ERR! mattermost-webapp@0.0.1 build: `NODE_ENV=production webpack`
npm ERR! Exit status 2
npm ERR!
npm ERR! Failed at the mattermost-webapp@0.0.1 build script 'NODE_ENV=production webpack'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the mattermost-webapp package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     NODE_ENV=production webpack
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs mattermost-webapp
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls mattermost-webapp
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /root/go/src/github.com/mattermost/platform/webapp/npm-debug.log
make[1]: *** [build] Error 1
make[1]: Leaving directory `/root/go/src/github.com/mattermost/platform/webapp'
make: *** [build-client] Error 2

My npm-debug.log file is as below:

0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/nodejs', '/usr/bin/npm', 'run', 'build' ]
2 info using npm@3.8.6
3 info using node@v5.12.0
4 verbose run-script [ 'prebuild', 'build', 'postbuild' ]
5 info lifecycle mattermost-webapp@0.0.1~prebuild: mattermost-webapp@0.0.1
6 silly lifecycle mattermost-webapp@0.0.1~prebuild: no script for prebuild, continuing
7 info lifecycle mattermost-webapp@0.0.1~build: mattermost-webapp@0.0.1
8 verbose lifecycle mattermost-webapp@0.0.1~build: unsafe-perm in lifecycle true
9 verbose lifecycle mattermost-webapp@0.0.1~build: PATH: /usr/lib/node_modules/npm/bin/node-gyp-bin:/root/go/src/github.com/mattermost/platform/webapp/node_modules/.bin:/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/usr/local/go/bin:/root/go/bin
10 verbose lifecycle mattermost-webapp@0.0.1~build: CWD: /root/go/src/github.com/mattermost/platform/webapp
11 silly lifecycle mattermost-webapp@0.0.1~build: Args: [ '-c', 'NODE_ENV=production webpack' ]
12 silly lifecycle mattermost-webapp@0.0.1~build: Returned: code: 2  signal: null
13 info lifecycle mattermost-webapp@0.0.1~build: Failed to exec build script
14 verbose stack Error: mattermost-webapp@0.0.1 build: `NODE_ENV=production webpack`
14 verbose stack Exit status 2
14 verbose stack     at EventEmitter.<anonymous> (/usr/lib/node_modules/npm/lib/utils/lifecycle.js:239:16)
14 verbose stack     at emitTwo (events.js:100:13)
14 verbose stack     at EventEmitter.emit (events.js:185:7)
14 verbose stack     at ChildProcess.<anonymous> (/usr/lib/node_modules/npm/lib/utils/spawn.js:24:14)
14 verbose stack     at emitTwo (events.js:100:13)
14 verbose stack     at ChildProcess.emit (events.js:185:7)
14 verbose stack     at maybeClose (internal/child_process.js:850:16)
14 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:215:5)
15 verbose pkgid mattermost-webapp@0.0.1
16 verbose cwd /root/go/src/github.com/mattermost/platform/webapp
17 error Linux 2.6.32-042stab116.2
18 error argv "/usr/bin/nodejs" "/usr/bin/npm" "run" "build"
19 error node v5.12.0
20 error npm  v3.8.6
21 error code ELIFECYCLE
22 error mattermost-webapp@0.0.1 build: `NODE_ENV=production webpack`
22 error Exit status 2
23 error Failed at the mattermost-webapp@0.0.1 build script 'NODE_ENV=production webpack'.
23 error Make sure you have the latest version of node.js and npm installed.
23 error If you do, this is most likely a problem with the mattermost-webapp package,
23 error not with npm itself.
23 error Tell the author that this fails on your system:
23 error     NODE_ENV=production webpack
23 error You can get information on how to open an issue for this project with:
23 error     npm bugs mattermost-webapp
23 error Or if that isn't available, you can get their info via:
23 error     npm owner ls mattermost-webapp
23 error There is likely additional logging output above.
24 verbose exit [ 1, true ]

Anyone have any ideas as to why on earth this is happening (or, for that matter, how to remedy it)?

Ta

Curtis

Posts: 1

Participants: 1

Read full topic

@Flix wrote:

Hi there,

i'm new to mattermost and want to set it up for my company. I already follow the installing guid for Debian jessie, but at the last step of "setting up the nginx server" i got a 502 Error instead of page titles "Mattermost - Signup"
as i say i have follow exactly the guid with one exception: the ip-address.

what can i do?

thanks in advance

sorry for my bad english

Posts: 6

Participants: 2

Read full topic

@nguyenalm wrote:

go version go1.6.3 linux/amd64
Error then run "make test"
[2016/08/10 04:14:51 ICT] [WARN] Finished recycling the database connection
[2016/08/10 04:14:54 ICT] [EROR] /api/v3/admin/test_email:testEmail code=403 rid=epqtfo59ufguze7jy34xfea78o uid=nupyy8ke8pf6jxizutubajca8r ip=::1 You do not have the appropriate permissions (system) [details: userId=nupyy8ke8pf6jxizutubajca8r]
[2016/08/10 04:14:54 ICT] [EROR] /api/v3/admin/test_email:testEmail code=500 rid=pzomwu5dtbbhxyojc9jh7yeajh uid=fpcec4577ibw5ystgi678umyec ip=::1 SMTP Server is required [details: Invalid SMTPServer parameter]
[2016/08/10 04:14:56 ICT] [EROR] /api/v3/admin/analytics/7u6yw8a47ib4bjakficbkkoq1w/standard:getAnalytics code=403 rid=cp9ugax8jirobnfyw7sdzamhko uid=pasrhaajmpfrufyy3rdkbdacye ip=::1 You do not have the appropriate permissions (system) [details: userId=pasrhaajmpfrufyy3rdkbdacye]
[2016/08/10 04:14:58 ICT] [EROR] /api/v3/admin/analytics/5z3ew45s6fnftjswg6tcaiia3h/post_counts_day:getAnalytics code=403 rid=aigu8m3mm3bq3bi678hbqd67er uid=uz75zerg5tn1zy41mpburyzm6a ip=::1 You do not have the appropriate permissions (system) [details: userId=uz75zerg5tn1zy41mpburyzm6a]
[2016/08/10 04:15:00 ICT] [EROR] /api/v3/admin/analytics/ftsa14mpepdjupznir9xpsz3zw/user_counts_with_posts_day:getAnalytics code=403 rid=mtctifm1c3bdd83czkyduxet3e uid=zfj4oh78up8npxsm36s7tpww1e ip=::1 You do not have the appropriate permissions (system) [details: userId=zfj4oh78up8npxsm36s7tpww1e]
[2016/08/10 04:15:02 ICT] [EROR] /api/v3/admin/analytics/extra_counts: code=401 rid=q6eyig1cztgtmb11e8m6caxfro uid= ip=::1 Invalid or expired session, please login again. [details: UserRequired]
[2016/08/10 04:15:04 ICT] [EROR] /api/v3/admin/reset_mfa: code=403 rid=4t7sjqmha3razcymig73117kty uid=bwoytcwcn7n8jn5ka7anqez1re ip=::1 You do not have the appropriate permissions [details: AdminRequired]
[2016/08/10 04:15:04 ICT] [EROR] /api/v3/admin/reset_mfa:adminResetMfa code=400 rid=55dw8o47sjysbc4cm1cp5yc9fh uid=yi17sut4ni81tfty7wp467iuyr ip=::1 Invalid user_id parameter [details: ]
[2016/08/10 04:15:04 ICT] [EROR] /api/v3/admin/reset_mfa:DeactivateMfa code=501 rid=u8r69igwtj87dgnhdh35e1tnqc uid=yi17sut4ni81tfty7wp467iuyr ip=::1 MFA not configured or available on this server [details: ]
[2016/08/10 04:15:04 ICT] [EROR] /api/v3/admin/reset_mfa:DeactivateMfa code=501 rid=k4n4k8x3pi8wd8e1im8feeoado uid=yi17sut4ni81tfty7wp467iuyr ip=::1 MFA not configured or available on this server [details: ]
[2016/08/10 04:15:05 ICT] [EROR] /api/v3/admin/reset_password:adminResetPassword code=400 rid=3b5cj3u1dtybbnyaqse8c435ro uid=3wt8o1c7upbzdnec3ehcoxuadr ip=::1 Invalid user_id parameter [details: ]
[2016/08/10 04:15:05 ICT] [EROR] /api/v3/admin/reset_password:adminResetPassword code=400 rid=kp7rjecbzfr43dfb5j3ak3wj8a uid=3wt8o1c7upbzdnec3ehcoxuadr ip=::1 Invalid user_id parameter [details: ]
[2016/08/10 04:15:05 ICT] [EROR] /api/v3/admin/reset_password:SqlUserStore.Get code=500 rid=ex8iqgkwbbb7idd3yrz37do86o uid=3wt8o1c7upbzdnec3ehcoxuadr ip=::1 We couldn't find an existing account matching your email address for this team. This team may require an invite from the team owner to join. [details: user_id=12345678901234567890123456]
[2016/08/10 04:15:05 ICT] [EROR] /api/v3/admin/reset_password:User.IsValid code=500 rid=hx8txrbrt7rd3pydtk661aiydr uid=3wt8o1c7upbzdnec3ehcoxuadr ip=::1 Your password must contain at least 5 characters. [details: ]
[2016/08/10 04:15:05 ICT] [EROR] /api/v3/admin/reset_password: code=403 rid=cjmtsnnegfna7y49qewwwwchzc uid=pokocc95ffyc7k8bzphojbh5ho ip=::1 You do not have the appropriate permissions [details: AdminRequired]
[2016/08/10 04:15:08 ICT] [EROR] /api/v3/teams/nfedycn35bf8pc19bhzd1jyuwa/channels/create:SqlChannelStore.Save code=500 rid=7jgs7akcsf8j3j7zwhnn8mz9ey uid=ajtcsf4r4jnkjmeyzyc11mumac ip=::1 Must call update for exisiting channel [details: id=dbhbpu5aafb78fwo7rwmczartw]
[2016/08/10 04:15:08 ICT] [EROR] /api/v3/teams/nfedycn35bf8pc19bhzd1jyuwa/channels/create:SqlChannelStore.Save code=500 rid=nqx65rg8mpd43qguwuwanmqjrc uid=ajtcsf4r4jnkjmeyzyc11mumac ip=::1 A channel with that URL already exists [details: id=w3zgwkpitbrq8bii6my7gb9xme, Error 1062: Duplicate entry 'adfpkwknyfjnwdeycmmtt3cnpjra-nfedycn35bf8pc19bhzd1jyuwa' for key 'Name']
[2016/08/10 04:15:08 ICT] [EROR] /api/v3/teams/nfedycn35bf8pc19bhzd1jyuwa/channels/create:createChannel code=400 rid=iwyaedzdx7npdkhgybgjofk86h uid=ajtcsf4r4jnkjmeyzyc11mumac ip=::1 Invalid channel parameter [details: ]
[2016/08/10 04:15:08 ICT] [EROR] Failed to post archive message Post.IsValid: model.post.is_valid.type.app_error, id=system_channel_deleted
[2016/08/10 04:15:08 ICT] [EROR] /api/v3/teams/nfedycn35bf8pc19bhzd1jyuwa/channels/create:SqlChannelStore.Save code=500 rid=suowowx1gjgcpeia8qh995hkpo uid=ajtcsf4r4jnkjmeyzyc11mumac ip=::1 A channel with that URL was previously created [details: id=7pswm5kiq3f7f8cgcyqx8kwx8c, Error 1062: Duplicate entry 'adfpkwknyfjnwdeycmmtt3cnpjra-nfedycn35bf8pc19bhzd1jyuwa' for key 'Name']
[2016/08/10 04:15:09 ICT] [EROR] /api/v3/teams/nfedycn35bf8pc19bhzd1jyuwa/channels/create:createChannel code=403 rid=djoorpdtkjyq3jei75rugdeg7w uid=ajtcsf4r4jnkjmeyzyc11mumac ip=::1 You do not have the appropriate permissions [details: userId=ajtcsf4r4jnkjmeyzyc11mumac, teamId=3kdtuefg638kdgpw7kmqy4qjae]
[2016/08/10 04:15:09 ICT] [EROR] /api/v3/teams/nfedycn35bf8pc19bhzd1jyuwa/channels/create:createDirectChannel code=500 rid=hupb9ur79jd1bbsepfrqi3y16w uid=ajtcsf4r4jnkjmeyzyc11mumac ip=::1 Invalid character '__' in channel name for non-direct channel [details: ]
[2016/08/10 04:15:09 ICT] [EROR] /api/v3/teams/nfedycn35bf8pc19bhzd1jyuwa/channels/create:createDirectChannel code=500 rid=zqicuejhhj8pprkouegxp14npo uid=ajtcsf4r4jnkjmeyzyc11mumac ip=::1 Must use createDirectChannel api service for direct message channel creation [details: ]
[2016/08/10 04:15:09 ICT] [EROR] /api/v3/teams/nfedycn35bf8pc19bhzd1jyuwa/channels/create:CanManageChannel code=500 rid=g8i5doaestgypyi79ckrk4nq4r uid=ajtcsf4r4jnkjmeyzyc11mumac ip=::1 Public Channel management and creation is restricted to Team and System Administrators. [details: ]
[2016/08/10 04:15:09 ICT] [EROR] /api/v3/teams/nfedycn35bf8pc19bhzd1jyuwa/channels/create:CanManageChannel code=500 rid=kw7i39tg73n93ysxacwwiqunee uid=ajtcsf4r4jnkjmeyzyc11mumac ip=::1 Private Group management and creation is restricted to Team and System Administrators. [details: ]
[2016/08
...
...

Please help me !
Thanks !

Posts: 1

Participants: 1

Read full topic

@ovizii wrote:

Summary

New mattermost 3.2 team edition gives this error when a user validates his email by clicking the provided link.

Steps to reproduce

mattermost 3.2.0

Google didn't help. Not exactly sure what this HID parameter is.

Posts: 1

Participants: 1

Read full topic

@dmills wrote:

Summary

I think I found a bug, I'd like to help report it. Not sure where to do so.

Steps to reproduce

In the System Console - Email Notifications, test a connection with gmail smtp but make sure the password is in plaintext in the field. The connection test will work.

Save the config, return to team messaging, then enter system console again. The same test, with the password hid behind asterisks, no longer works.

Expected behavior

A config that is set up correctly should always test successfully. Need to pull the password correctly before testing.

Observed behavior

The page test led me to believe I was failing whenever I came back to the test page. So I kept resetting the config and trying again. I chased a non-existent problem for a long time. My config was correct. The test was not.

Posts: 1

Participants: 1

Read full topic

@dav wrote:

Hi,

First, i have to say. Very happy and grateful of your product. I never had any issue of what so ever with it.
But after upgrading to team edition v3.3.0 i get errors in mattermost.log every seconds.

[EROR] /api/v3/users/status: code=404 ip=10.126.1.16
[EROR] /api/v3/users/status: code=404 ip=10.126.1.5
[EROR] /api/v3/users/status: code=404 ip=10.126.1.8

One for each client connected to mattermost.
I'm running RHEL7 + mattermost v3.3 + postgres + Nginx with sll mode.

Can it be the new API update 3.3 with my basic nginx configuration?
Here my nginx config. for mattermost:

server {
listen 80;
server_name mattermost.sll.se;
return 301 https://$server_name$request_uri;
}

server {
listen 443 ssl;
server_name mattermost.sll.se;

ssl on;
ssl_certificate /etc/nginx/conf.d/mattermost.pem;
ssl_certificate_key /etc/nginx/conf.d/mattermost.key;
ssl_session_timeout 5m;
ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
ssl_ciphers 'EECDH+AESGCM:EDH+AESGCM:AES256+EECDH:AES256+EDH';
ssl_prefer_server_ciphers on;
ssl_session_cache shared:SSL:10m;

location / {
gzip off;
proxy_set_header X-Forwarded-Ssl on;
client_max_body_size 50M;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
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_pass http://127.0.0.1:8065;
}
}

Posts: 3

Participants: 1

Read full topic

@riemers wrote:

Mattermost doesn't show the full name of people in the chat

I installed the docker package, hooked it up to gitlab via oauth. Everything works just fine, except for the full name

I would have expected to see the full name if the settings of the "PrivacySettings" where set to "True" for "ShowFullName".

No matter what i do, i still get to see the userid of the person, and not the full name. As an admin, when i am in the system console and check out a team i can see the full name above the email in the list. Which i would expect to see in the team channels too.

Also note, that when i am in the team channel, i only see the userid and email. I don't see the full name at all. (Neither does it show a nickname, if i set one)

Any help would be appreciated.

Update: In Account settings -> Display -> Teammate Name display i can find the setting to update it, but i want to set this to another value for all new members. Otherwise its an extra thing they need to do.

Posts: 1

Participants: 1

Read full topic

@akitaonrails wrote:

Summary

We have several messages of "/api/v3/users/status" 404 being logged and I am not sure it's related to 404 messages showing up in the users' web interfaces.

Steps to reproduce

Not sure how to reproduce, it just started happening in a new v3.3.0 installation. Just followed the available production documentation for Ubuntu 14.04 with PG and NGINX/Let's Encrypt. Absolutely nothing out of the ordinary.

Expected behaviour

From the System Console, I see several messages like this:

[2016/08/15 13:50:53 UTC] [INFO] Stopping Server...
[2016/08/15 13:50:53 UTC] [INFO] Closing SqlStore
[2016/08/15 13:50:53 UTC] [INFO] Loaded system translations for 'en' from '/home/mattermost/mattermost-dev/i18n/en.json'
[2016/08/15 13:50:54 UTC] [INFO] Current version is 3.3.0 (3.3.0/Fri Aug 12 20:27:37 UTC 2016/20735470185e0b0ac1d15b975041ed9a2e0e43bc/none)
[2016/08/15 13:50:54 UTC] [INFO] Enterprise Enabled: false
[2016/08/15 13:50:54 UTC] [INFO] Current working directory is /home/mattermost/mattermost-dev
[2016/08/15 13:50:54 UTC] [INFO] Loaded config file from /home/mattermost/mattermost-dev/config/config.json
[2016/08/15 13:50:54 UTC] [INFO] Server is initializing...
[2016/08/15 13:50:54 UTC] [INFO] Pinging sql master database
[2016/08/15 13:50:54 UTC] [INFO] Pinging sql replica-0 database
[2016/08/15 13:50:54 UTC] [INFO] Starting Server...
[2016/08/15 13:50:54 UTC] [INFO] Server is listening on :8065
[2016/08/15 13:50:54 UTC] [INFO] RateLimiter is enabled
[2016/08/15 13:51:17 UTC] [EROR] /api/v3/users/status: code=404 ip=177.64.214.185
[2016/08/15 13:51:24 UTC] [EROR] websocket routing error: seq=0 uid=3cmaz6xznfddfdbqa4y6ebxp4w api.web_socket_router.bad_seq.app_error [details: ]
[2016/08/15 13:51:47 UTC] [EROR] /api/v3/users/status: code=404 ip=177.64.214.185
[2016/08/15 13:51:55 UTC] [EROR] /api/v3/users/profiles/: code=404 ip=186.203.7.150
[2016/08/15 13:52:17 UTC] [EROR] /api/v3/users/status: code=404 ip=177.64.214.185
[2016/08/15 13:52:26 UTC] [EROR] websocket routing error: seq=0 uid=3cmaz6xznfddfdbqa4y6ebxp4w api.web_socket_router.bad_seq.app_error [details: ]
[2016/08/15 13:52:47 UTC] [EROR] /api/v3/users/status: code=404 ip=177.64.214.185
[2016/08/15 13:53:17 UTC] [EROR] /api/v3/users/status: code=404 ip=177.64.214.185
[2016/08/15 13:53:27 UTC] [EROR] websocket routing error: seq=0 uid=3cmaz6xznfddfdbqa4y6ebxp4w api.web_socket_router.bad_seq.app_error [details: ]
[2016/08/15 13:53:47 UTC] [EROR] /api/v3/users/status: code=404 ip=177.64.214.185
[2016/08/15 13:54:17 UTC] [EROR] /api/v3/users/status: code=404 ip=177.64.214.185
[2016/08/15 13:54:29 UTC] [EROR] websocket routing error: seq=0 uid=3cmaz6xznfddfdbqa4y6ebxp4w api.web_socket_router.bad_seq.app_error [details: ]
[2016/08/15 13:54:47 UTC] [EROR] /api/v3/users/status: code=404 ip=177.64.214.185
[2016/08/15 13:55:17 UTC] [EROR] /api/v3/users/status: code=404 ip=177.64.214.185
[2016/08/15 13:55:30 UTC] [EROR] websocket routing error: seq=0 uid=3cmaz6xznfddfdbqa4y6ebxp4w api.web_socket_router.bad_seq.app_error [details: ]
[2016/08/15 13:55:47 UTC] [EROR] /api/v3/users/status: code=404 ip=177.64.214.185
[2016/08/15 13:56:07 UTC] [EROR] /api/v3/teams/channels/eybad1jzufbt7e3b3gfknxbgah/: code=404 ip=186.203.7.150
[2016/08/15 13:56:17 UTC] [EROR] /api/v3/users/status: code=404 ip=177.64.214.185
[2016/08/15 13:56:31 UTC] [EROR] websocket routing error: seq=0 uid=3cmaz6xznfddfdbqa4y6ebxp4w api.web_socket_router.bad_seq.app_error [details: ]
[2016/08/15 13:56:47 UTC] [EROR] /api/v3/users/status: code=404 ip=177.64.214.185
[2016/08/15 13:57:17 UTC] [EROR] /api/v3/users/status: code=404 ip=177.64.214.185
[2016/08/15 13:57:33 UTC] [EROR] websocket routing error: seq=0 uid=3cmaz6xznfddfdbqa4y6ebxp4w api.web_socket_router.bad_seq.app_error [details: ]

Observed behaviour

I would ignore this but sometimes the users receive a message bar saying that something went wrong and that a 404 occurred. But it is not 1 to 1 to the logs in the server, so I am not sure it's correlated.

Posts: 4

Participants: 3

Read full topic

@Wintrmte wrote:

For feature requests, please see: http://www.mattermost.org/feature-requests/.

For troubleshooting questions, please post in the following format:

Summary

After creating an Incoming Webhook, when accessing the link - Mattermost is returning a 404 error. This was happening with Mattermost 3.2.0 and now 3.3.0

Steps to reproduce

Go into a Team, create an Incoming Webhook. Cut and paste the URL into another browser and you get a 404 page not found from the Mattermost web services.

Expected behavior

Should return something different other than 404

Observed behavior

Returns a 404 error - also with debugging turned on in the logs, all I get is this:
[2016/08/16 17:25:40 MDT] [DEBG] /hooks/pdec6db6n3yf3m93ux6hn4uzue
[2016/08/16 17:25:40 MDT] [DEBG] /api/v3/users/initial_load

Posts: 1

Participants: 1

Read full topic

@tejasbubane wrote:

Summary

I am getting websockets error when upgraded to mattermost v3.3.0

Steps to reproduce

Installed mattermost 3.1.0 via docker. Upgraded to 3.3.0 using these steps:
Fetch the repo again (https://github.com/mattermost/mattermost-docker.git)
and set HEAD to 3.3.0 tag.

$ docker-compose build
$ docker-compose up

Expected behavior

Should boot up the containers and run properly

Observed behavior

See this error in the logs (host URL changed):

db_1  | LOG:  database system is ready to accept connections
db_1  | LOG:  autovacuum launcher started
db_1  | LOG:  incomplete startup packet
app_1 | Configure database connection...SKIP
app_1 | Wait until database db:5432 is ready...
web_1 | Starting Nginx
web_1 | ln: failed to create symbolic link '/etc/nginx/sites-enabled/mattermost': File exists
web_1 | 2016/08/20 06:34:53 [error] 11#0: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 106.51.15.26, server: , request: "GET /api/v3/users/websocket HTTP/1.1", upstream: "http://172.17.0.3:80/api/v3/users/websocket", host: "example.com"
web_1 | 106.51.15.26 - - [20/Aug/2016:06:34:53 -0400] "GET /api/v3/users/websocket HTTP/1.1" 502 583 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_5) AppleWebKit/537.36 (KHTML, like Gecko) Mattermost/1.3.0 Chrome/51.0.2704.84 Electron/1.2.2 Safari/537.36"
app_1 | Starting platform
web_1 | 2016/08/20 06:34:53 [error] 11#0: *3 connect() failed (111: Connection refused) while connecting to upstream, client: 106.206.147.201, server: , request: "GET /api/v3/users/websocket HTTP/1.1", upstream: "http://172.17.0.3:80/api/v3/users/websocket", host: "example.com"
web_1 | 106.206.147.201 - - [20/Aug/2016:06:34:53 -0400] "GET /api/v3/users/websocket HTTP/1.1" 502 583 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_1) AppleWebKit/537.36 (KHTML, like Gecko) Mattermost/1.2.1 Chrome/49.0.2623.75 Electron/0.37.8 Safari/537.36"
web_1 | 2016/08/20 06:34:53 [error] 11#0: *5 connect() failed (111: Connection refused) while connecting to upstream, client: 106.51.15.230, server: , request: "GET /api/v3/users/websocket HTTP/1.1", upstream: "http://172.17.0.3:80/api/v3/users/websocket", host: "example.com"
web_1 | 106.51.15.230 - - [20/Aug/2016:06:34:53 -0400] "GET /api/v3/users/websocket HTTP/1.1" 502 583 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_0) AppleWebKit/537.36 (KHTML, like Gecko) Mattermost/1.3.0 Chrome/51.0.2704.84 Electron/1.2.2 Safari/537.36"
web_1 | 2016/08/20 06:34:53 [error] 11#0: *7 connect() failed (111: Connection refused) while connecting to upstream, client: 103.252.24.109, server: , request: "GET /api/v3/users/websocket HTTP/1.1", upstream: "http://172.17.0.3:80/api/v3/users/websocket", host: "example.com"
web_1 | 103.252.24.109 - - [20/Aug/2016:06:34:53 -0400] "GET /api/v3/users/websocket HTTP/1.1" 502 583 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_3) AppleWebKit/537.36 (KHTML, like Gecko) Mattermost/1.3.0 Chrome/51.0.2704.84 Electron/1.2.2 Safari/537.36"

On the client mac app v1.3.0, getting some 404 error. Cannot see any online users (even though they are online) Tried restarting the client-app and containers.
PS: There is no error if I view the website via browser.

Am I missing something in the upgrade?

Posts: 5

Participants: 3

Read full topic

@akitaonrails wrote:

Summary

After the 3.3.0 upgrade every single direct message is being pushed to the mobile application. All participants are already online through the web desktop interface, typing direct messages between each other and for each message sent, the mobile application receives a notification.

Steps to reproduce

We were using 3.2, upgraded to 3.3. All of us using the official Android app.

Expected behavior

Open direct message between members and start sending messages, the smartphone should start receiving push notifications.

Observed behavior

If should not be sending messages when the participants are all online in the web desktop interface already, so this must be a bug introduced in 3.3.0

Posts: 2

Participants: 2

Read full topic