@markamber wrote:
I am using an iis Application Request Routing setup. Everything works very well except when I send emails from the server they link to the internal IP instead of the external host URL. Many other applications these days have an option to override this. Is there any option here for this?
Posts: 1
Participants: 1
@balleyne wrote:
I've followed the Debian installation guide to install Mattermost on a single VPS (1GB RAM, 30GB SSD), but I can't get Mattermost to start.
http://docs.mattermost.com/install/prod-debian.html
I'm using Mattermost v3.1.0. When I get to the step to test the Mattermost server, it fails to run as follows:
root@mattermost:/opt/mattermost/bin# ./platform panic: runtime error: invalid memory address or nil pointer dereference [recovered] panic: interface conversion: interface is runtime.errorString, not string [signal 0xb code=0x1 addr=0x0 pc=0x776cb2] goroutine 1 [running]: panic(0xcd1aa0, 0xc820015a00) /usr/local/go/src/runtime/panic.go:481 +0x3e6 main.doLoadConfig.func1(0xc820149d48) /var/lib/jenkins/jobs/mattermost-platform-release/workspace/src/github.com/mattermost/platform/mattermost.go:73 +0x6f panic(0xccbec0, 0xc82000a0e0) /usr/local/go/src/runtime/panic.go:443 +0x4e9 github.com/mattermost/platform/utils.LoadConfig(0xc82012dad0, 0x22) /var/lib/jenkins/jobs/mattermost-platform-release/workspace/src/github.com/mattermost/platform/utils/config.go:172 +0xd12 main.doLoadConfig(0xdce990, 0xb, 0x0, 0x0) /var/lib/jenkins/jobs/mattermost-platform-release/workspace/src/github.com/mattermost/platform/mattermost.go:76 +0x6a main.main() /var/lib/jenkins/jobs/mattermost-platform-release/workspace/src/github.com/mattermost/platform/mattermost.go:84 +0x43I've tried searching the web on the error message, but all the results I've found have slightly different errors -- I've checked the formatting of my JSON file, testing the PostgreSQL credentials... not sure what the problem could be. Any help would be appreciated.
Posts: 1
Participants: 1
@kinshuk wrote:
Hi Folks
I recently discovered Gitlab CE and Mattermost and wanted to give it a try within my organisation. All my servers run on Windows Azure right now and so I went ahead and started a new virtual machine with a ready-made Gitlab CE image.
The new machine runs absolutely fine and I was able to add users, create groups and projects. Worked like a charm. For Gitlab I was using:
external_url 'http://dev.mydomain.com'(Edit: this was actually a long random url created by Azure and I had to change it to this value for everything to work)
Next step for me was to setup Mattermost. I read the documentation and went ahead to edit
/etc/gitlab/gitlab.rbI only set:
mattermost_external_url 'http://chatter.mydomain.com'These are the only two active lines in my gitlab.rb
Now when I run
sudo gitlab-ctl reconfigure, after a huge block of text, I see the following success message:
Running handlers:
Running handlers complete
Chef Client finished, 5/292 resources updated in 08 seconds
gitlab Reconfigured!Now, when I try to access both my sites: dev.mydomain.com and chatter.mydomain.com, I get a 521 error.
I get the following status for Gitlab on the server:
devlab:~$ sudo gitlab-ctl status
run: gitlab-workhorse: (pid 33034) 1424s; run: log: (pid 1253) 18293s
run: logrotate: (pid 33043) 1423s; run: log: (pid 1255) 18293s
run: mattermost: (pid 33049) 1423s; run: log: (pid 29284) 2434s
down: nginx: 0s, normally up, want up; run: log: (pid 1278) 18293s
run: postgresql: (pid 33163) 1389s; run: log: (pid 1282) 18293s
run: redis: (pid 33137) 1392s; run: log: (pid 1251) 18293s
run: sidekiq: (pid 33146) 1390s; run: log: (pid 1284) 18293s
run: unicorn: (pid 33172) 1389s; run: log: (pid 1261) 18293sI can see that nginx is down, and I am completely clueless how to get it up.
What am I doing wrong?
Posts: 2
Participants: 1
@Sousapro wrote:
Hello all,
I've been working on trying to deploy mattermost 3.1 and I've been unable to import from slack. I have followed http://docs.mattermost.com/install/prod-ubuntu.html to a T, other than substituting IP addresses and my home directory name. Every time I export from Slack, I get an import failure. The Mattermost Import Summary is here: http://pastebin.com/c7mQRFmW
Posts: 2
Participants: 1
@tradecraft1 wrote:
I am installing Mattermost on on RHEL 6.0 following this guide: http://docs.mattermost.com/install/prod-rhel-6.html
I've reached the Finish section here: http://docs.mattermost.com/install/prod-rhel-6.html#finish-mattermost-server-setup
On Step 1 it says to navigate to Mattermost server I installed to create the initial user. When I navigate to that URL I get the login page and do not see a place to create a user. Did I miss a step?
Posts: 1
Participants: 1
@scsi wrote:
Hi all... I have mattermost running behind a reverse proxy, at the root.. So, say
[edited... I can only include 2 links in this post since I'm a new user, evidently... ]
foo.example.com/
I have the proxy server redirect /stats/ to another server.
So,
foo.example.com/ => mattermost
foo.example.com/stats/ => some other serverThat works all fine and well. But when I link to https://foo.example.com/stats/ in a mattermost chat, users are redirected to the choose a team page instead of actually loading this address.
Is there any way to stop mattermost from hijacking these URLs?
Thanks!
Posts: 1
Participants: 1
@andrey wrote:
I've got runnnig matternost 3.1 under Centos 7.2, there are 211 members, most of them are active.
Constantly after 2-3-4 days I start to get error messages in log like this:[2016/06/29 12:09:15 MSK] [EROR] /api/v3/users/cewojitd7pn7drbwxu56c9xsph/image:createProfileImage code=500 rid=tybi8g9hqiyzdper8forsuxhpa uid=seq8mnj73jb5mef5bie9doz31y ip=XXXXX Could not create default profile image font [details: open /opt/mattermost/fonts/luximbi.ttf: too many open files]
and clients start to lose connections. Solution is restarting mattermost service, so I have to do that every few days.
Mattermost running under root user(I need run mattermost on 80, by the way, are there any solutions to run in 80 without root privelegies?)
Root user has these limits:
ulimit -Hn
100000
ulimit -Sn
100000
At moment I get error messages I can see mattermost has about 15-16 thousands of openned files:
lsof | grep platform | wc -l
15450
The same troubles I had with 3.0.2 version
So, Is it mattermost bug or configuration bug?
Posts: 1
Participants: 1
@swdream wrote:
Summary
memleak in mattermost
Steps to reproduce
Configuration file
{ "ServiceSettings": { "ListenAddress": "127.0.0.1:8065", "MaximumLoginAttempts": 10, "SegmentDeveloperKey": "", "GoogleDeveloperKey": "", "EnableOAuthServiceProvider": false, "EnableIncomingWebhooks": true, "EnableOutgoingWebhooks": false, "EnableCommands": false, "EnableOnlyAdminIntegrations": true, "EnablePostUsernameOverride": false, "EnablePostIconOverride": true, "EnableTesting": false, "EnableDeveloper": false, "EnableSecurityFixAlert": true, "EnableInsecureOutgoingConnections": false, "EnableMultifactorAuthentication": false, "AllowCorsFrom": "", "SessionLengthWebInDays": 30, "SessionLengthMobileInDays": 30, "SessionLengthSSOInDays": 30, "SessionCacheInMinutes": 10, "WebsocketSecurePort": 443, "WebsocketPort": 80, "WebserverMode": "regular" }, "TeamSettings": { "SiteName": "Mattermost", "MaxUsersPerTeam": 50, "EnableTeamCreation": false, "EnableUserCreation": true, "EnableOpenServer": false, "RestrictCreationToDomains": "", "RestrictTeamNames": true, "EnableCustomBrand": false, "CustomBrandText": "", "RestrictDirectMessage": "any" }, "SqlSettings": { "DriverName": "postgres", "DataSource": "postgres://mattermost:psql_password@127.0.0.1:5432/mattermost?sslmode=disable&connect_timeout=10", "DataSourceReplicas": [], "MaxIdleConns": 10, "MaxOpenConns": 10, "Trace": false, "AtRestEncryptKey": encrypt_key }, "LogSettings": { "EnableConsole": false, "ConsoleLevel": "WARNING", "EnableFile": true, "FileLevel": "WARNING", "FileFormat": "", "FileLocation": "/var/log/mattermost/mattermost.log" }, "FileSettings": { "DriverName": "local", "Directory": "/var/lib/mattermost/", "EnablePublicLink": true, "PublicLinkSalt": Public_link, "ThumbnailWidth": 120, "ThumbnailHeight": 100, "PreviewWidth": 1024, "PreviewHeight": 0, "ProfileWidth": 128, "ProfileHeight": 128, "InitialFont": "luximbi.ttf", "AmazonS3AccessKeyId": "", "AmazonS3SecretAccessKey": "", "AmazonS3Bucket": "", "AmazonS3Region": "", "AmazonS3Endpoint": "", "AmazonS3BucketEndpoint": "", "AmazonS3LocationConstraint": false, "AmazonS3LowercaseBucket": false }, "EmailSettings": { "EnableSignUpWithEmail": true, "EnableSignInWithEmail": true, "EnableSignInWithUsername": true, "SendEmailNotifications": true, "RequireEmailVerification": true, "FeedbackName": Feedback_user, "FeedbackEmail": feedback_email, "SMTPUsername": feedback_user, "SMTPPassword": password, "SMTPServer": mailserver, "SMTPPort": "465", "ConnectionSecurity": "TLS", "InviteSalt": invite salt, "PasswordResetSalt": password, "SendPushNotifications": false, "PushNotificationServer": "", "PushNotificationContents": "generic" }, "RateLimitSettings": { "EnableRateLimiter": true, "PerSec": 10, "MemoryStoreSize": 10000, "VaryByRemoteAddr": true, "VaryByHeader": "X-Real-IP" }, "PrivacySettings": { "ShowEmailAddress": true, "ShowFullName": true }, "GitLabSettings": { "Enable": false, "Secret": "", "Id": "", "Scope": "", "AuthEndpoint": "", "TokenEndpoint": "", "UserApiEndpoint": "" } }Version: 3.0.0 (3.0.3)
But we suffer this issue since old version (2.1.0)$ lsb_release -d; uname -r; free -m Description: Ubuntu 14.04.4 LTS 3.13.0-68-generic total used free shared buffers cached Mem: 490 478 12 29 20 173 -/+ buffers/cache: 283 206 Swap: 0 0 0Expected behavior
memory is stable
Observed behavior
platform consumes more and more memory until it's killed by kernel (OOM)
Does anybody is experiencing the same issue ? Is this a know issue or just because I wrongly config mattermost?
Thanks & best regards.
Posts: 1
Participants: 1
@jelies wrote:
Hi all,
I wanted to have a try to Mattermost, so I decided to run the Docker image. Folowing the docs Docker page, everything is up an running but there is nothing to display at http://localhost:8065. These are the mattermost.log content:
[2016/07/01 11:22:49 UTC] [INFO] Current version is 3.0.0 (3.0.3/Fri May 27 18:08:10 UTC 2016/cb745475452a9fc8ef3a9fedf6b34af7d05adba9) [2016/07/01 11:22:49 UTC] [INFO] Enterprise Enabled: false [2016/07/01 11:22:49 UTC] [INFO] Current working directory is /mm/mattermost [2016/07/01 11:22:49 UTC] [INFO] Loaded config file from /mm/mattermost/config/config_docker.json [2016/07/01 11:22:49 UTC] [INFO] Server is initializing... [2016/07/01 11:22:49 UTC] [INFO] Pinging sql master database [2016/07/01 11:22:49 UTC] [CRIT] Failed to ping db err:dial tcp [::1]:3306: getsockopt: connection refusedAny clue how to fix this? The problem looks related to MySQL (port 3306). I'm testing it on my local Ubuntu 14.04 desktop, Docker 1.11.2.
Thanks!
Posts: 1
Participants: 1
@my65bug wrote:
No matter which machine I try this on I can't seem to get this to work. I have tried two different mac machines and now I am using a virtual Joyent machine with ubuntu and still having the exact same issue.
start on runlevel [2345]
stop on runlevel [016]
respawn
chdir /mattermost
setuid root
exec bin/platformI get the following error:
start: Unknown job: mattermost
Any ideas?
Posts: 1
Participants: 1
@MasinAD wrote:
Hello,
I can't get email notifications to work. Mattermost cannot authenticate against my SMTP server.
Connection unsuccessful: Failed to authenticate on SMTP server - 535 5.7.8 Error: authentication failed:
In /var/log/mail.log there're these lines to be found at each attempt:
Jul 5 00:15:15 vmd9662 postfix/smtpd[2857]: connect from vmd9662.contabo.host[5.189.134.50]
Jul 5 00:15:15 vmd9662 postfix/smtpd[2857]: Anonymous TLS connection established from vmd9662.contabo.host[5.189.134.50]: TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)
Jul 5 00:15:17 vmd9662 postfix/smtpd[2857]: warning: vmd9662.contabo.host[5.189.134.50]: SASL PLAIN authentication failed:
Jul 5 00:15:17 vmd9662 postfix/smtpd[2857]: disconnect from vmd9662.contabo.host[5.189.134.50]I configured my email client with the exact same settings and get this log output when sending an email:
Jul 5 00:03:14 vmd9662 postfix/smtpd[2623]: connect from ipservice-092-214-156-164.092.214.pools.vodafone-ip.de[92.214.156.164]
Jul 5 00:03:14 vmd9662 postfix/smtpd[2623]: Anonymous TLS connection established from ipservice-092-214-156-164.092.214.pools.vodafone-ip.de[92.214.156.164]: TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)
Jul 5 00:03:15 vmd9662 postfix/smtpd[2623]: NOQUEUE: client=ipservice-092-214-156-164.092.214.pools.vodafone-ip.de[92.214.156.164], sasl_method=plain, sasl_username=mattermost@fluchtkapsel.de
Jul 5 00:03:15 vmd9662 postfix/smtpd[2659]: connect from localhost[127.0.0.1]
Jul 5 00:03:15 vmd9662 postfix/smtpd[2659]: 9834A244171D: client=localhost[127.0.0.1], orig_client=ipservice-092-214-156-164.092.214.pools.vodafone-ip.de[92.214.156.164]
Jul 5 00:03:15 vmd9662 postfix/cleanup[2660]: 9834A244171D: message-id=<…
Jul 5 00:03:15 vmd9662 postfix/smtpd[2659]: disconnect from localhost[127.0.0.1]
Jul 5 00:03:15 vmd9662 postfix/qmgr[12338]: 9834A244171D: from=…, size=1269, nrcpt=1 (queue active)
Jul 5 00:03:15 vmd9662 amavis[12364]: (12364-02) Passed CLEAN {RelayedOutbound}, SUBMISSION LOCAL [92.214.156.164]:40544 [92.214.156.164] … -> …, Message-ID: …, mail_id: qq7B1-HT9Tno, Hits: -0.998, size: 796, queued_as: 9834A244171D, 243 ms
Jul 5 00:03:15 vmd9662 postfix/smtpd[2623]: proxy-accept: END-OF-MESSAGE: 250 2.0.0 from MTA(smtp:[127.0.0.1]:10035): 250 2.0.0 Ok: queued as 9834A244171D; from=… to=… proto=ESMTP helo=<[192.168.1.72]>
Jul 5 00:03:15 vmd9662 postfix/smtpd[2623]: disconnect from ipservice-092-214-156-164.092.214.pools.vodafone-ip.de[92.214.156.164]
Jul 5 00:03:15 vmd9662 postfix/smtp[2661]: Untrusted TLS connection established to gmail-smtp-in.l.google.com[66.102.1.26]:25: TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)
Jul 5 00:03:16 vmd9662 postfix/smtp[2661]: 9834A244171D: to=…, relay=gmail-smtp-in.l.google.com[66.102.1.26]:25, delay=0.48, delays=0.03/0.04/0.17/0.23, dsn=2.0.0, status=sent (250 2.0.0 OK 1467669796 o10si86009wjs.136 - gsmtp)Am I missing something obvious? Should I provide more information about my setup?
Masin
(removed all email addresses because forum software thought I wanted to post links)
Posts: 1
Participants: 1
@Punkado wrote:
Hello,
I am having a problem with the link in the emails sent by the
mattermost. Im my setup, i have a mattermost behind a Apache proxy for the ssl and when the mattermost send a email, like the reset password email, the link is pointing to the http not the https.
The mattermost is get the information about the url from the rewrite rule in the apache configuration file of the site:
RewriteRule .* http://mysite.com:8065%{REQUEST_URI} [P,QSA,L]
The problem is that i can not change the site in the rewrite rule, otherwise the server stops to work.
Does anyone know how to solve this?
Thanks!
The full configuration of the site in the apache is here:
> <IfModule mod_ssl.c> > <VirtualHost *:443> > ServerName mysite.com > ServerAdmin webmaster@example.org > ErrorLog ${APACHE_LOG_DIR}/mattermost-error.log > CustomLog ${APACHE_LOG_DIR}/mattermost-access.log combined > RewriteEngine On > RewriteCond %{REQUEST_URI} ^/api/v1/websocket [NC,OR] > RewriteCond %{HTTP:UPGRADE} ^WebSocket$ [NC,OR] > RewriteCond %{HTTP:CONNECTION} ^Upgrade$ [NC] > RewriteRule .* ws://127.0.0.1:8065%{REQUEST_URI} [P,QSA,L] > RewriteCond %{DOCUMENT_ROOT}/%{REQUEST_FILENAME} !-f > RewriteRule .* http://mysite.com:8065%{REQUEST_URI} [P,QSA,L] > # RequestHeader set X-Forwarded-Proto "https" > > RequestHeader unset If-Modified-Since > RequestHeader unset If-None-Match > <Location /api/v1/websocket> > Require all granted > ProxyPassReverse ws://127.0.0.1:8065/api/v1/websocket > ProxyPassReverseCookieDomain 127.0.0.1 mysite.com > </Location> > <Location /> > Require all granted > ProxyPassReverse http://127.0.0.1:8065/ > ProxyPassReverseCookieDomain 127.0.0.1 mysite.com > </Location> > # Some rewrite rules in this file were were disabled on your HTTPS site, > # because they have the potential to create redirection loops. > # RewriteRule ^/?(.*) https://%{SERVER_NAME}/$1 [R,L] > SSLCertificateFile /etc/letsencrypt/live/mysite.com/fullchain.pem > SSLCertificateKeyFile /etc/letsencrypt/live/mysite.com/privkey.pem > Include /etc/letsencrypt/options-ssl-apache.conf > </VirtualHost> > </IfModule>
Posts: 2
Participants: 2
@tetafro wrote:
Hi. I have Ubuntu 16.04 LTS server, that I've just installed and Gitlab CE on it. I installed it with install-script from http://gitlab.com. Mattermost is enabled and everything works fine except SMTP notifications.
I tried to change settings from system console (in browser), but they get reset on
gitlab-ctl reconfigure.Then I tried to change directly
/etc/gitlab/gitlab.rbwith this settings:mattermost['email_enable_sign_up_with_email'] = false mattermost['email_send_email_notifications'] = true mattermost['email_smtp_username'] = "mattermost@***.com" mattermost['email_smtp_password'] = "***" mattermost['email_smtp_server'] = "smtp.gmail.com" mattermost['email_smtp_port'] = 587 mattermost['email_connection_security'] = "STARTTLS" mattermost['email_feedback_name'] = "Mattermost" mattermost['email_feedback_email'] = "mattermost@***.com"They look fine when I go back to system console, but it shows me auth error:
Failed to authenticate on SMTP server [details: 535 5.7.8 Username and Password not accepted.But now if I set password in the system console to the same password from config - everything works. Until next
gitlab-ctl reconfigurewhen password is reset again.So how can I set password permanently?
Posts: 3
Participants: 2
@shadowmaster63 wrote:
Just write in mattermost chat
test.test/%%
Received empty line.Version: 3.1.0
Build Number: 3.1.0
Build Date: Mon Jun 13 19:08:00 UTC 2016
Build Hash: 974238231b9cdbd39a825ec8e9299fbb0b51f6b8
Build Enterprise Ready: false
DB Version: 3.1.0
Posts: 1
Participants: 1
@ravidverve wrote:
HI,
I am trying to request the mattermost API suing Angular JS + Nodejs + Gulp + Bower.
But I get below error
Please help me ASAP.Thanks & Regards
Posts: 5
Participants: 2
@techspawn wrote:
I have an instance of gitlab which when I installed, I set up mattermost but didn't use it at the time.Now that I've upgraded gitlab and plan to use it, I run the interactive upgrade but it says I have 0 teams (expected), but I can't do the upgrade because I can't choose any team for the script to keep running.
gitlab@gitlab:~/mattermost/bin$ sudo -u mattermost -i bash
mattermost@gitlab:~$ cd /opt/gitlab/embedded/service/mattermost
mattermost@gitlab:/opt/gitlab/embedded/service/mattermost$ /opt/gitlab/embedded/bin/mattermost -config='/var/opt/gitlab/mattermost/config.json' -upgrade_db_30Please see http://www.mattermost.org/upgrade-to-3-0/
WARNING This upgrade process will be irreversible.
Have you performed a database backup? (YES/NO): YES
We found 0 teams.
Please pick a primary team from the list above:
Posts: 1
Participants: 1
@theonetruemoo wrote:
Hi
first post is one that is vexing me terribly,
We have just installed Matter most on our systems and are looking at integrating it across board,
as a result we are building our own API implementation to do what is needed
,the problem I'm facing is I cannot find a list of API commands and requirements.
I have tried to get a list from
//MyURL/api/v3/
//MyURL/api/v2/
//MyURL/api/v1/
//MyURL/api/among many other stabs in the dark
after some hunting I found a partial guide in the code:
//github.com/mattermost/platform/tree/master/apiwhich when testing some of the results work others not so much because I can't seem to determine what the required inputs are
Eg for login need email, team and password and run a GET that returns the my user details
So if anyone can show me where to look for the API's and what is required in the payloads it would be super beneficial
Edit:
My main concern here is how to use the API to create a channel, and move team members into it
If any one can let me know the URL and the Payloads to post to make this happen I would be truly gratefulThanks in advance
Posts: 2
Participants: 1
@upk wrote:
For feature requests, please see: http://www.mattermost.org/feature-requests/.
For troubleshooting questions, please post in the following format:
Summary
Starting mattermost with ./platform works
But starting mattermost with systemctl start mattermost failedSteps to reproduce
Debian Jessie:
Linux version 3.16.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version 4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.7-ckt25-2+deb8u3 (2016-07-02)Mattermost:
Version 3.2.0Expected behavior
executing
/etc/init.d/mattermost start
should start mattermost daemonObserved behavior
executing
/etc/init.d/mattermost start
shows
[ ok ] Starting mattermost (via systemctl): mattermost.service.But mattermost is not reachable.
Nginx shows 502 Bad Gateway/etc/init.d/mattermost status
shows● mattermost.service - Mattermost is an open source, self-hosted Slack-alternative
Loaded: loaded (/etc/systemd/system/mattermost.service; enabled)
Active: activating (auto-restart) (Result: exit-code) since Mi 2016-07-20 08:01:49 CEST; 23s ago
Process: 13589 ExecStart=/opt/mattermost/bin/platform (code=exited, status=2)
Main PID: 13589 (code=exited, status=2)in /var/syslog
Jul 20 08:07:52 mattermost platform open /opt/mattermost/logs/mattermost.log: permission denied
Jul 20 08:07:52 mattermost platform[13711]: panic: runtime error: invalid memory address or nil pointer dereference [recovered]
Jul 20 08:07:52 mattermost platform[13711]: panic: interface conversion: interface is runtime.errorString, not string
Jul 20 08:07:52 mattermost platform[13711]: [signal 0xb code=0x1 addr=0x0 pc=0x775569]
Jul 20 08:07:52 mattermost platform[13711]: goroutine 1 [running]:
Jul 20 08:07:52 mattermost platform[13711]: panic(0xcd1aa0, 0xc820043a80)
Jul 20 08:07:52 mattermost platform +0x3e6
Jul 20 08:07:52 mattermost platform[13711]: main.doLoadConfig.func1(0xc820145d48)
Jul 20 08:07:52 mattermost platform +0x6f
Jul 20 08:07:52 mattermost platform[13711]: panic(0xccbec0, 0xc82000a0a0)
Jul 20 08:07:52 mattermost platform +0x4e9
Jul 20 08:07:52 mattermost platformJul 20 08:07:52 mattermost platform +0x539
Jul 20 08:07:52 mattermost platform 0x22)
Jul 20 08:07:52 mattermost platform +0x109c
Jul 20 08:07:52 mattermost platform[13711]: main.doLoadConfig(0xdce990, 0xb, 0x0, 0x0)
Jul 20 08:07:52 mattermost platform +0x6a
Jul 20 08:07:52 mattermost platform[13711]: main.main()
Jul 20 08:07:52 mattermost platform +0x43
Jul 20 08:07:52 mattermost systemd[1]: mattermost.service: main process exited, code=exited, status=2/INVALIDARGUMENT
Jul 20 08:07:52 mattermost systemd[1]: Unit mattermost.service entered failed state.
Posts: 1
Participants: 1
@a9tm wrote:
Hi, I've just installed fresh CentOS 6.8 64 bit system, successfully installed latest Mattermost by following official docs (http://docs.mattermost.com/install/prod-rhel-6.html). Tested running Mattermost OK on TCP/8065 port then installed nginx 1.10.1 from its repo. But Nginx gave Error 502, though I still can access Mattermost:8065 with out problem. I disabled iptables, ip6tables, and SElinux just in case but still no working.
Does anybody have the same problem?
Edit: Restart server and it works! Sorry for the noise.
Posts: 1
Participants: 1
@springshot_guy wrote:
Summary
My company have asked me to do a simple evaluation of Mattermost.
They want me to confirm that channels can be created programatically.Steps to reproduce
I create the Docker evaluation installation using the instructions at:
http://docs.mattermost.com/install/docker-local-machine.html
I verified that I can login via the web interface.
But when I try to acquire a authentication token via curl I get the following error:
`$ curl -i -d '{"name":"springshot","login_id":"foo@bar.com","password":"password"}' http://dockerhost:8065/api/v3/users/login
HTTP/1.1 400 Bad Request
Content-Type: application/json
X-Ratelimit-Limit: 10
X-Ratelimit-Remaining: 9
X-Ratelimit-Reset: 1
X-Request-Id: zt33utt497gjdyujpc9hiynmqy
X-Version-Id: 3.0.0.1466368946
Date: Wed, 20 Jul 2016 17:07:14 GMT
Content-Length: 281{"id":"store.sql_user.get_for_login.app_error","message":"We couldn't find an existing account matching your credentials. This team may require an invite from the team owner to join.","detailed_error":"","request_id":"zt33utt497gjdyujpc9hiynmqy","status_code":400,"is_oauth":false}
`Do I need to enable something?
Posts: 1
Participants: 1
