@salo wrote:

Summary

After upgrading to Gitlab version 8.12.6, users cannot authenticate via Gitlab SSO anymore and this error message is displayed: "GitLab Mattermost needs your help: We encountered an error trying to find the account by authentication type."

Steps to reproduce

Have an existing Gitlab installation with users that authenticate via Gitlab SSO and upgrade Gitlab to version 8.12.6.
Then try to log in to Mattermost.

Expected behavior

Users should be able to authenticate via Gitlab SSO as it was possible prior to the update.

Observed behavior

Some relevant log entries from the mattermost.log:
[2016/10/12 13:54:06 CEST] [EROR] /api/v3/users/initial_load:SqlUserStore.GetDirectProfiles code=500 rid=5fjr49ya9jb9fxa7w5669spaue uid=ufhs8xpo5idsjkqbwrybyttdwe ip=10.54.74.60 We encountered an error while finding user profiles [details: gorp: no fields [themeprops] in type User]
[2016/10/12 13:59:21 CEST] [EROR] /signup/gitlab/complete:SqlUserStore.GetByAuth code=500 rid=oxr9c6bautdh7mf99tq54rybth uid= ip=127.0.0.1 We encountered an error trying to find the account by authentication type. [details: authData=2, authService=gitlab, gorp: no fields [themeprops] in type User]

Posts: 2

Participants: 1

Read full topic

@Yxogen wrote:

Hi everyone,
I have a problem with mattermost. I installed it on docker for Windows, it seems to work properly, I'm now able to access the mattermost administration page from the host.

The problem is, I have 5 PC in LAN under a HP-A5120 switch. DHCP IP is handled with this switch like : 10.42.x.x.x with MAC address lock.
The docker ip address (the virtual machine) is 192.168.x.x

I can access to the docker ip address from the host, i can access to the host from another PC on the same LAN, but I can't access to the docker itself from another PC.

Do I need to do something with "docker" ? maybe virtualbox settings ? or the switch ?

Thank you !

ps : English isn't my native language

Posts: 2

Participants: 2

Read full topic

@jhr wrote:

Hi
since we upgraded everything to 3.4 (TEAM Edition Server, iOS Apps and push-proxy), the Push-Notifications are not working anymore. We see the following error message at the push-proxy:

2016/10/14 11:08:37 INFO Sending apple push notification
2016/10/14 11:08:37 ERROR Failed to send apple push sid=xxxxxxxxxxxxxxxxxxxxxxxx did= err=device token has incorrect length

We have checked the installation several times, certificates are OK, too.
Does anyone have an idea where this error comes from? Could it be a problem within the iOS App?
ciao,
JR

Posts: 1

Participants: 1

Read full topic

@sumanmaity112 wrote:

Summary

Error creating database tables: pq: syntax error at or near "not"

Steps to reproduce

I am using mattermostV3.2.0 and postgres9.5
I used https://docs.mattermost.com/install/prod-ubuntu.html documentation link to setup mattermost.
I am trying to install in centos 6.6

Expected behavior

It should start mattermost server

Observed behavior

The current config is
{
"ServiceSettings": {
"ListenAddress": ":8065",
"MaximumLoginAttempts": 10,
"SegmentDeveloperKey": "",
"GoogleDeveloperKey": "",
"EnableOAuthServiceProvider": false,
"EnableIncomingWebhooks": true,
"EnableOutgoingWebhooks": true,
"EnableCommands": true,
"EnableOnlyAdminIntegrations": true,
"EnablePostUsernameOverride": false,
"EnablePostIconOverride": false,
"EnableTesting": false,
"EnableDeveloper": false,
"EnableSecurityFixAlert": true,
"EnableInsecureOutgoingConnections": false,
"EnableMultifactorAuthentication": false,
"AllowCorsFrom": "",
"SessionLengthWebInDays": 30,
"SessionLengthMobileInDays": 30,
"SessionLengthSSOInDays": 30,
"SessionCacheInMinutes": 10,
"WebsocketSecurePort": 443,
"WebsocketPort": 80,
"WebserverMode": "gzip",
"EnableCustomEmoji": false,
"RestrictCustomEmojiCreation": "all"
},
"TeamSettings": {
"SiteName": "Mattermost",
"MaxUsersPerTeam": 50,
"EnableTeamCreation": true,
"EnableUserCreation": true,
"EnableOpenServer": false,
"RestrictCreationToDomains": "",
"RestrictTeamNames": true,
"EnableCustomBrand": false,
"CustomBrandText": "",
"RestrictDirectMessage": "any",
"RestrictTeamInvite": "all",
"RestrictPublicChannelManagement": "all",
"RestrictPrivateChannelManagement": "all"
},
"SqlSettings": {
"DriverName": "postgres",
"DataSource": "postgres://mmuser:mmuser_password@127.0.0.1:5432/mattermost?sslmode=disable&connect_timeout=10",
"DataSourceReplicas": [],
"MaxIdleConns": 10,
"MaxOpenConns": 10,
"Trace": false,
"AtRestEncryptKey": "7rAh6iwQCkV4cA1Gsg3fgGOXJAQ43QVg"
},
"LogSettings": {
"EnableConsole": true,
"ConsoleLevel": "DEBUG",
"EnableFile": true,
"FileLevel": "INFO",
"FileFormat": "",
"FileLocation": "",
"EnableWebhookDebugging": true
},
"PasswordSettings": {
"MinimumLength": 5,
"Lowercase": false,
"Number": false,
"Uppercase": false,
"Symbol": false
},
"FileSettings": {
"MaxFileSize": 52428800,
"DriverName": "local",
"Directory": "./data/",
"EnablePublicLink": false,
"PublicLinkSalt": "A705AklYF8MFDOfcwh3I488G8vtLlVip",
"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": false,
"RequireEmailVerification": false,
"FeedbackName": "",
"FeedbackEmail": "",
"FeedbackOrganization": "",
"SMTPUsername": "",
"SMTPPassword": "",
"SMTPServer": "",
"SMTPPort": "",
"ConnectionSecurity": "",
"InviteSalt": "bjlSR4QqkXFBr7TP4oDzlfZmcNuH9YoS",
"PasswordResetSalt": "vZ4DcKyVVRlKHHJpexcuXzojkE5PZ5eL",
"SendPushNotifications": false,
"PushNotificationServer": "",
"PushNotificationContents": "generic"
},
"RateLimitSettings": {
"EnableRateLimiter": true,
"PerSec": 10,
"MemoryStoreSize": 10000,
"VaryByRemoteAddr": true,
"VaryByHeader": ""
},
"PrivacySettings": {
"ShowEmailAddress": true,
"ShowFullName": true
},
"SupportSettings": {
"TermsOfServiceLink": "https://about.mattermost.com/default-terms/",
"PrivacyPolicyLink": "https://about.mattermost.com/default-privacy-policy/",
"AboutLink": "https://about.mattermost.com/default-about/",
"HelpLink": "https://about.mattermost.com/default-help/",
"ReportAProblemLink": "https://about.mattermost.com/default-report-a-problem/",
"SupportEmail": "feedback@mattermost.com"
},
"GitLabSettings": {
"Enable": false,
"Secret": "",
"Id": "",
"Scope": "",
"AuthEndpoint": "",
"TokenEndpoint": "",
"UserApiEndpoint": ""
},
"GoogleSettings": {
"Enable": false,
"Secret": "",
"Id": "",
"Scope": "",
"AuthEndpoint": "",
"TokenEndpoint": "",
"UserApiEndpoint": ""
},
"LdapSettings": {
"Enable": false,
"LdapServer": "",
"LdapPort": 389,
"ConnectionSecurity": "",
"BaseDN": "",
"BindUsername": "",
"BindPassword": "",
"UserFilter": "",
"FirstNameAttribute": "",
"LastNameAttribute": "",
"EmailAttribute": "",
"UsernameAttribute": "",
"NicknameAttribute": "",
"IdAttribute": "",
"SyncIntervalMinutes": 60,
"SkipCertificateVerification": false,
"QueryTimeout": 60,
"MaxPageSize": 0,
"LoginFieldName": ""
},
"ComplianceSettings": {
"Enable": false,
"Directory": "./data/",
"EnableDaily": false
},
"LocalizationSettings": {
"DefaultServerLocale": "en",
"DefaultClientLocale": "en",
"AvailableLocales": ""
},
"SamlSettings": {
"Enable": false,
"Verify": false,
"Encrypt": false,
"IdpUrl": "",
"IdpDescriptorUrl": "",
"AssertionConsumerServiceURL": "",
"IdpCertificateFile": "",
"PublicCertificateFile": "",
"PrivateKeyFile": "",
"FirstNameAttribute": "",
"LastNameAttribute": "",
"EmailAttribute": "",
"UsernameAttribute": "",
"NicknameAttribute": "",
"LocaleAttribute": "",
"LoginButtonText": "With SAML"
}
}

While I am trying to run platform then its giving error Error creating database tables: pq: syntax error at or near "not"

This is the link for screenshot http://pasteboard.co/gn5k15s7n.png

Posts: 1

Participants: 1

Read full topic

@ktechmidas wrote:

Summary

No notification - occasionally have to refresh to see new messages. (Probably a WSS issue, can someone advise on how to fix? Is there a config I've missed in the migration?)

Steps to reproduce

I started on a LXC container, copied the rootfs of the mattermost container into another LXC host as we were migrating from one host to another (with a different IP). I've updated the internal IP address on the container and changed the config.json to reflect the new host (MySQL etc)

Expected behavior

For mattermost to work as expected, people to be online etc.

Observed behavior

Mattermost came up okay once the container started and I can login and see old messages and send messages - however if someone sends a message to anyone else they need to refresh the page in order to see it, and they cannot see anyone online even if they are. I also occasionally have WebRTC errors.

My nginx config is quite simple and looks like:

server {
listen 80;
server_name chat.xx;
return 301 https://$host$request_uri;
}

server {

listen 443 ssl;
server_name chat.xx;

ssl_certificate           /etc/letsencrypt/live/chat.xx/fullchain.pem;
ssl_certificate_key       /etc/letsencrypt/live/chat.xx/privkey.pem;

ssl on;
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;

access_log            /var/log/nginx/chat.ibbchina.com.access.log;
error_log             /var/log/nginx/chat.ibbchina.com..asia.error.log;

location / {
    gzip off;
    proxy_set_header X-Forwarded-Ssl on;
    client_max_body_size 100M;
    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://172.30.254.107:8065;

}}

Posts: 1

Participants: 1

Read full topic

@spivey76 wrote:

We are trying to evaluate Mattermost for company messaging. I've setup and installed on Debian 8; everything is working fine except for email notifications. When I test the following I receive 2 errors:

TLS on 25: Failed to open TLS connection [details: tls: first record does not look like a TLS handshake]

STARTTLS on 587: Failed to authenticate on SMTP server [details: 504 5.7.4 Unrecognized authentication type]

The only way I've received successful test notifications via email is by using no encryption (PLAIN)

I did see how this was mentioned with regards to Office360 but we use an in-house Exchange 2013 server. Has anyone has luck getting this to work?.

Posts: 1

Participants: 1

Read full topic

@marcchang wrote:

Summary

Using ./platform -invite_user -team_name="team" -email="email" sends an email with an invalid link.

Steps to reproduce

Just run ./platform -invite_user -team_name="team" -email="email"

Expected behavior

The Join Team link in the invite email should take you to the mattermost site URL.

Observed behavior

The link doesn't have the site URL pre-pended It just starts with "/signup_user_complete/" instead of "mattermost.example.com/signup_user_complete".

Posts: 1

Participants: 1

Read full topic

@bennnjamin wrote:

Summary

Had a functioning integration with Zapier and it stopped working 4 days ago, with Zapier saying that the session expired:
Bargle. We hit an error creating a post message. :-( Error:
team.ulets.us returned (401) Unauthorized and said "Invalid or expired session, please login again."

I tried to reconnect the account following the steps outlined in the Zapier/Mattermost documentation and it fails with invalid_request: Bad client_id

Steps to reproduce

1. Install mattermost-docker 3.4.0
2. Proxy mattermost from apache2 to nginx to docker
3. Create an OAuth2 integration for Zapier following these steps: https://docs.mattermost.com/integrations/zapier.html
4. Connect the account on Zapier
5. Get error "invalid_request: Bad client_id"

Expected behavior

Zapier authorizes successfully

Observed behavior

[2016/10/26 18:21:41 UTC] [EROR] /oauth/access_token:getAccessToken code=500 rid=pqxemy1pb7dgmgb6ffwccea8za uid= ip=54.210.27.170 invalid_request: Bad client_id [details: ]

Apache VHost Config:
`

   ServerName mydomain.com

  
RewriteEngine On
RewriteCond %{HTTPS} off
RewriteRule (.*) https://%{HTTP_HOST}%{REQUEST_URI}

    ServerName mydomain.com

SSLEngine on
    SSLCipherSuite ALL:!ADH:!EXPORT56:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP
    SSLCertificateFile    mycert.cry
    SSLCertificateKeyFile mykey.key
    SSLCertificateChainFile myccf.ca-bundle
Header add Strict-Transport-Security: "max-age=15768000;includeSubdomains"

SSLCompression Off
SSLProxyEngine On

RewriteEngine On
RewriteCond %{HTTP:Upgrade} =websocket [NC]
RewriteRule /(.*) wss://localhost:4343/$1 [P,L]

ProxyPreserveHost On
ProxyPass / https://0.0.0.0:4343/
ProxyPassReverse / https://0.0.0.0:4343/
#ProxyPass "/ws2/"  "https://0.0.0.0:8080/"
#ProxyPass "/wss2/"  "wss://0.0.0.0:4343/"
#ProxyPassReverse "/wss2/"  "wss://0.0.0.0:4343/"

LogLevel warn
Customlog /var/log/apache2/mattermost-access.log combined

`

Nginx config:

`server {

 listen 4343 ssl;
 server_name mydomain.com;

 ssl on;

 ssl_certificate chained.crt;
 ssl_certificate_key mykey.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: 1

Participants: 1

Read full topic

@seymourp wrote:

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

For troubleshooting questions, please post in the following format:

Summary

Many 504 logs from nginx as the front-end to Mattermost.

Steps to reproduce

Mattermost 3.4.0
nginx 1.10.1
Postgres 9.5

All are hosted on separate VM's running RHEL7.2

Expected behavior

MM responds as expected

Observed behavior

Attempting to use our POC Mattermost environment in a large chat we experienced 504 errors from the system. There doesn't seem to be anything relevant in the MM logs, or the Postgres logs but the web server constantly saw these.

504:60.000:60.000:.:183 1674861 mattermost. - [28/Oct/2016:22:59:57 +0100] "POST /api/v3/users/status/set_active_channel HTTP/1.1" "-" "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:47.0) Gecko/20100101 Firefox/47.0" "-" 10.34.176.24:8065 - "in: _ga=GA1.2.1558470232.1473435083; MMAUTHTOKEN=hjejbnx8qpfs3dyqjqzymuiu6r"
504:60.000:60.000:.:183 1703753 mattermost. - [29/Oct/2016:01:22:38 +0100] "POST /api/v3/teams/9t198y14rbf45k6xtaijjcngna/channels/9b7j54at7jgbjew3zabydj564c/update_last_viewed_at HTTP/1.1" "-" "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:47.0) Gecko/20100101 Firefox/47.0" "-" 10.34.176.24:8065 - "in: _ga=GA1.2.1558470232.1473435083; MMAUTHTOKEN=hjejbnx8qpfs3dyqjqzymuiu6r"
504:60.002:60.002:.:585 1703750 mattermost.. - [29/Oct/2016:01:22:46 +0100] "POST /api/v3/teams/9t198y14rbf45k6xtaijjcngna/channels/9b7j54at7jgbjew3zabydj564c/update_last_viewed_at HTTP/1.1" "-" "Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.71 Safari/537.36" "-" 10.34.176.24:8065 - "in: MMAUTHTOKEN=tqwzyjf6mir73fwmshhwaemfgc"
504:60.002:60.002:.:585 1703747 mattermost.. - [29/Oct/2016:01:22:50 +0100] "POST /api/v3/users/status/set_active_channel HTTP/1.1" "-" "Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.71 Safari/537.36" "-" 10.34.176.24:8065 - "in: MMAUTHTOKEN=tqwzyjf6mir73fwmshhwaemfgc"
504:60.001:60.001:.:183 1722359 mattermost.. - [29/Oct/2016:03:22:24 +0100] "POST /api/v3/teams/9t198y14rbf45k6xtaijjcngna/channels/9b7j54at7jgbjew3zabydj564c/update_last_viewed_at HTTP/1.1" "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/602.2.14 (KHTML, like Gecko) Version/10.0.1 Safari/602.2.14" "-" 10.34.176.24:8065 - "in: MMAUTHTOKEN=e9g611986fbzfqh3hqeq1xizsw; _ga=GA1.2.1132465454.1473346131"
504:60.000:60.000:.:183 1722563 mattermost.. - [29/Oct/2016:03:22:24 +0100] "GET /static/files/3812df668bb0144f7ae51853b202315b.mp3 HTTP/1.1" "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/602.2.14 (KHTML, like Gecko) Version/10.0.1 Safari/602.2.14" "-" 10.34.176.24:8065 - "in: MMAUTHTOKEN=e9g611986fbzfqh3hqeq1xizsw; _ga=GA1.2.1132465454.1473346131"
504:60.001:60.001:.:183 1722564 mattermost.. - [29/Oct/2016:03:22:24 +0100] "GET /static/files/3812df668bb0144f7ae51853b202315b.mp3 HTTP/1.1" "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/602.2.14 (KHTML, like Gecko) Version/10.0.1 Safari/602.2.14" "-" 10.34.176.24:8065 - "in: MMAUTHTOKEN=e9g611986fbzfqh3hqeq1xizsw; _ga=GA1.2.1132465454.1473346131"
504:60.002:60.002:.:585 1722403 mattermost.. - [29/Oct/2016:03:22:25 +0100] "POST /api/v3/teams/9t198y14rbf45k6xtaijjcngna/channels/9b7j54at7jgbjew3zabydj564c/update_last_viewed_at HTTP/1.1" "-" "Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.143 Safari/537.36" "-" 10.34.176.24:8065 - "in: MMAUTHTOKEN=ucwwc7ux8tfmpe5rmr498q7kka"
504:60.001:60.001:.:585 1722568 mattermost. - [29/Oct/2016:03:22:28 +0100] "POST /api/v3/users/status/set_active_channel HTTP/1.1" "-" "Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.143 Safari/537.36" "-" 10.34.176.24:8065 - "in: MMAUTHTOKEN=ucwwc7ux8tfmpe5rmr498q7kka"
504:60.009:60.008:.:183 1722443 mattermost. - [29/Oct/2016:03:22:28 +0100] "POST /api/v3/teams/9t198y14rbf45k6xtaijjcngna/channels/9b7j54at7jgbjew3zabydj564c/posts/create HTTP/1.1" "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/602.2.14 (KHTML, like Gecko) Version/10.0.1 Safari/602.2.14" "-" 10.34.176.24:8065 - "in: MMAUTHTOKEN=e9g611986fbzfqh3hqeq1xizsw; _ga=GA1.2.1132465454.1473346131"
504:60.001:60.001:.:183 1722571 mattermost. - [29/Oct/2016:03:22:28 +0100] "GET /api/v3/users/egr5ucx1ftdrfd3sn5fhsfogja/image?time=1477559367554 HTTP/1.1" "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/602.2.14 (KHTML, like Gecko) Version/10.0.1 Safari/602.2.14" "-" 10.34.176.24:8065 - "in: MMAUTHTOKEN=e9g611986fbzfqh3hqeq1xizsw; _ga=GA1.2.1132465454.1473346131"

Is there anything I should be setting either on the MM end, or the nginx end to try and prevent this ?

Thanks

Posts: 1

Participants: 1

Read full topic

@ntwrkguru wrote:

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

For troubleshooting questions, please post in the following format:

Summary

Running gitlab-ctl reconfigure wipes all System Console settings

Steps to reproduce

Mattermost 3.4.0 on Gitlab 8.12.4-ee

Expected behavior

Settings should persist

Observed behavior

Settings in gitlab.rb persist, but settings changed in the System Console are wiped

Posts: 1

Participants: 1

Read full topic

@Pablo wrote:

Hi!

In one moment my Mattermost chat changed from using the whole screen to use only a section, as shown in the photo, there is a white space on the right and on the bottom.
Could someone tell me how to set it that the screen chat is display in that white parts also?

Thank you!

Im using:
Mattermost Version 3.4.0
Windows 10

mattermost windows problem.jpg1920x1080 157 KB

Posts: 1

Participants: 1

Read full topic

@steven wrote:

Summary

Having issues with the proxy server receiving connections on 443.

Steps to reproduce

I initially built the Proxy server using the instructions here:

https://docs.mattermost.com/install/ee-prod-ubuntu.html

But I couldn't get the proxy server to work. Curl was refusing connection on both 80 and 443. I recreated the server using the SSL instructions here.

https://docs.mattermost.com/install/prod-ubuntu.html

After much trial and error I got nginx to respond via port 80 but not 443. netstat -plnt shows it's listening on port 80 for both ipv4 and ipv6. Any help would be greatly appreciated. I've gone through the entire process on the above link, so, in theory, I have SSL set up, but it doesn't appear that the server is listening on 443.

Also, just as a side-note, I've got a Microsoft background and a large part of the issue is likely that I don't know enough about Linux to get this up and running. Any assistance would be greatly appreciated. Thanks in advance.

Expected behavior

Describe your issue in detail

Observed behavior

What did you see happen? Please include relevant error messages and/or screenshots.

Posts: 1

Participants: 1

Read full topic

@esodov wrote:

I set up a new Mattermost 3.4.0 Team Edition,
but the create account button doesn't display on the login page.
Login forms just display on it.

capture.PNG1101x819 31.9 KB

"Enable Account Creation" is true.
I can create user accounts by CLI but I want my team members to create their own accounts.

Could you tell me how to solve this?
Thank you.

I'm using
OS : CentOS 7.2 on Windows Server 2008 R2 with Vagrant.
DB : MySQL 5.7.
Client : Firefox, Chrome, Mattermost Desktop

Posts: 1

Participants: 1

Read full topic

@fraziern wrote:

I'm trying to set up a local development environment and am getting stuck with database issues. Any help is appreciated.

Running OS X 10.11
Gotten through the setup instructions but when I run make run I get the following:

ldap_sasl_bind(SIMPLE): Can't contact LDAP server (-1)
ldap_sasl_bind(SIMPLE): Can't contact LDAP server (-1)
ldap_sasl_bind(SIMPLE): Can't contact LDAP server (-1)
ldap_sasl_bind(SIMPLE): Can't contact LDAP server (-1)
ldap_sasl_bind(SIMPLE): Can't contact LDAP server (-1)
ldap_sasl_bind(SIMPLE): Can't contact LDAP server (-1)
make: *** [start-docker] Error 255

When I try make clean-docker, then make start-docker, then make run-server, I get this:

[2016/11/16 06:38:42 EST] [INFO] Server is initializing...
[2016/11/16 06:38:42 EST] [INFO] Pinging sql master database
[MySQL] 2016/11/16 06:38:42 packets.go:32: EOF
[2016/11/16 06:38:42 EST] [CRIT] Failed to ping db err:driver: bad connection
exit status 102

docker ps:
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
2066b033613e mattermost/webrtc:latest "/bin/sh -c /opt/janu" 12 minutes ago Up 11 minutes 0.0.0.0:7088-7089->7088-7089/tcp, 0.0.0.0:8188-8189->8188-8189/tcp mattermost-webrtc
3c46780a03ef osixia/openldap:1.1.6 "/container/tool/run" 15 minutes ago Up 15 minutes 0.0.0.0:389->389/tcp, 0.0.0.0:636->636/tcp mattermost-openldap
295feb9e3957 postgres:9.4 "/docker-entrypoint.s" 15 minutes ago Up 15 minutes 0.0.0.0:5432->5432/tcp mattermost-postgres
9bc309abd2a2 mysql:5.7 "docker-entrypoint.sh" 16 minutes ago Up 15 minutes 0.0.0.0:3306->3306/tcp mattermost-mysql

Any ideas?

Posts: 1

Participants: 1

Read full topic

@jasonblais wrote:

Opening a new thread to help troubleshoot "There was a problem connecting the video call." errors with the new preview of video and audio calls (WebRTC).

If you're receiving this error after setting up WebRTC, please help answer the following questions:

1. Did you use Mattermost Docker preview for WebRTC? Or did you set up a Janus for WebRTC gateway? How about Coturn for STUN/TURN? (See documentation for more info).
2. What distribution and database is your Mattermost instance installed on?
3. Which browser/desktop app (and version) are the two users using? How about operating system?
4. Does the issue reproduce with more than one person?
5. Does the issue reproduce each time, if you try to call the same person 2-3 times? (sometimes we've had issues in the past where first try doesn't connect)

Thanks for testing the early preview feature!

Posts: 3

Participants: 2

Read full topic

@marcchang wrote:

Summary

Websocket connections are not connecting, so new posts don't show up unless I reload the page.

Steps to reproduce

Enabling SSL on nginx causes this problem

Expected behavior

When I enable SSL for nginx... websocket connections are not getting upgraded to wss. I get this error: was loaded over HTTPS, but attempted to connect to the insecure WebSocket endpoint 'ws://mattermost1.nyc.deshaw.com/api/v3/users/websocket'. This request has been blocked; this endpoint must be available over WSS.

I follow configuration steps in the RHEL7 setup doc, but I can't seem to get it to work...

Posts: 1

Participants: 1

Read full topic

@gubbins wrote:

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

For troubleshooting questions, please post in the following format:

Summary

A specific user is in several channels, but when someone mentions them by @username they see a bogus message "username was mentioned, but they did not receive a notification because they do not belong to this channel."

Steps to reproduce

Has occurred since upgrading from 3.2 to 3.5. Conditions to reproduce are otherwise unknown.

Expected behavior

Since the user is in the channel we do not expect this message to appear, and we expect the user to get a notification.

Observed behavior

Observations:

• username is correct in the user's account settings and in the database
• user is shown as a channel member and is in the ChannelMembers database table, and has many posts in the channel
• autocomplete of the username works fine, and shows the user as in the channel
• using other mention words seems to work as expected - only the username has this curious effect

Posts: 2

Participants: 2

Read full topic

@dwsc wrote:

Summary

After upgrading from 3.4.0 to 3.5.0, I am unable to add new profile pics.

Steps to reproduce

• Upgrade from 3.4.0 to 3.5.0.
• Upload user profile picture

Expected behavior

Profile picture successfully upload

Observed behavior

Original s3 endpoint set to "s3.amazonaws.com" in 3.4.0 and integration worked fine.

User receives "Could not upload profile image" error message
Server logs show:
[details: The bucket you are attempting to access must be addressed using the specified endpoint. Please send all future requests to this endpoint.]

When changing the storage endpoint to the aws listed endpoint xxx.s3-website-us-west-2.amazonaws.com (other variants tried), the error changes to:
[details: Amazon S3 endpoint should be 's3.amazonaws.com'.]

Config file appears correct (bucket redacted):
"AmazonS3Bucket": "xxx",
"AmazonS3Region": "us-west-2",
"AmazonS3Endpoint": "s3.amazonaws.com",
"AmazonS3SSL": true

Posts: 2

Participants: 1

Read full topic

@qwertypuffs wrote:

Summary

Desktop Notifications are not showing up in Firefox 43 and Firefox 45 on Centos 6. Installed Mattermost 3.5.1 to Centos 7. Websockets connecting properly and it gets sent in real time.

Steps to reproduce

1. Log in to Mattermost
2. Allow Notifications for site
3. Change tabs
4. Have someone message the channel,
5. No notifications pop up.

Expected behavior

Since websockets are set up properly, the notifications should pop up whenever someone messages a user.

Observed behavior

• No pop ups are shown when someone messages another user
• Notification.permission == "granted" in the web browser console
• Attached image as proof that websockets work fine.
  
  websocket_mattermost.jpeg1669x685 72.1 KB

Posts: 3

Participants: 2

Read full topic

@moomoo wrote:

Summary

Using apache2 vhosts for gitlab + mattermost on the same machine, letsencrypt for SSL, gitlab SSO fails with "Bad token type"

Steps to reproduce

On a clean Ubuntu 16.04, install gitlab-ce [ GitLab Community Edition 8.14.1 e45bf3d ] and letsencrypt. Have DNS for example.com, git.example.com, and chat.example.com all pointing to that same machine, and get certs for all three. Configure gitlab's nginx to run on port 8001, and mattermost by default runs the service on localhost:8065. This is the /etc/gitlab/gitlab.rb:

external_url 'https://git.example.com'
gitlab_rails['gitlab_email_from'] = 'gitlab@example.com'
nginx['enable'] = true
nginx['ssl_certificate'] = "/etc/letsencrypt/live/example.com/fullchain.pem"
nginx['ssl_certificate_key'] = "/etc/letsencrypt/live/example.com/privkey.pem"
nginx['listen_port'] = 8001 

mattermost_external_url 'https://chat.example.com'
mattermost['enable'] = true
mattermost['service_use_ssl'] = true
mattermost_nginx['enable'] = false

Apache2 vhosts are used to redirect https://git.example.com and https://chat.example.com to the right ports:

<VirtualHost *:443>                                                                                 
  ServerName git.example.com                                                 

  <Proxy *>                                                                  
    Require all granted                                                      
  </Proxy>                                                                   

  SSLProxyEngine on                                                          
  SSLProxyVerify none                                                        
  SSLProxyCheckPeerCN off                                                    
  SSLProxyCheckPeerName off                                                  
  SSLProxyCheckPeerExpire off                                                
                                                                             
  ProxyRequests Off                                                          
  ProxyPass / https://127.0.0.1:8001/                                        
  ProxyPassReverse / https://git.example.com/                                
                                                                             
  RewriteEngine on                                                           
  RewriteCond %{DOCUMENT_ROOT}/%{REQUEST_FILENAME} !-f                       
  RewriteRule .* https://127.0.0.1:8001%{REQUEST_URI} [P,QSA]                
                                                                             
  # needed for downloading attachments                                       
  DocumentRoot /opt/gitlab/embedded/service/gitlab-rails/public              
                                                                             
  SSLEngine on                                                               
  SSLCertificateFile /etc/letsencrypt/live/example.com/fullchain.pem         
  SSLCertificateKeyFile /etc/letsencrypt/live/example.com/privkey.pem        
  Include /etc/letsencrypt/options-ssl-apache.conf                           
</VirtualHost>

and

<VirtualHost *:443>                                                                                 
  ServerName chat.example.com                                                
                                                                             
  SSLEngine on                                                               
  SSLCertificateFile /etc/letsencrypt/live/example.com/fullchain.pem         
  SSLCertificateKeyFile /etc/letsencrypt/live/example.com/privkey.pem        
  Include /etc/letsencrypt/options-ssl-apache.conf                           
                                                                             
  ServerSignature Off                                                        
  ProxyPreserveHost On                                                       
  ProxyRequests Off                                                          
                                                                             
  # Ensure that encoded slashes are not decoded but left in their encoded state.
  # http://doc.gitlab.com/ce/api/projects.html#get-single-project            
  AllowEncodedSlashes NoDecode                                               
                                                                             
  DocumentRoot /var/opt/gitlab/mattermost                                    
                                                                             
  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://127.0.0.1:8065%{REQUEST_URI} [P,QSA,L]               
  RequestHeader set X-Forwarded-Proto "https"                                
                                                                             
  <Location /api/v1/websocket>                                               
    Require all granted                                                      
    ProxyPassReverse http://127.0.0.1:8065                                   
    ProxyPassReverseCookieDomain 127.0.0.1 chat.example.com                  
  </Location>                                                                
                                                                             
  <Location />                                                               
    Require all granted                                                      
    ProxyPassReverse http://127.0.0.1:8065                                   
    ProxyPassReverseCookieDomain 127.0.0.1 chat.example.com                  
  </Location>                                                                
                                                                             
</VirtualHost>

Expected behavior

You can log in to Mattermost using Gitlab SSO

Observed behavior

Clicking on Gitlab Single-Sign-On sends me to Gitlab [ git.example.com ] to log in, which succeeds.
I get a prompt to "Authorize GitLab Mattermost to use your account?"
I click "authorize", which sends me back to chat.example.com with the error:

GitLab Mattermost needs your help:
Bad token type
Go back to Mattermost

In the logfile /var/log/gitlab/mattermost/mattermost.log, I have the error

[EROR] /signup/gitlab/complete:AuthorizeOAuthUser code=500 rid=<###> uid= ip=<###> Bad token type [details: token_type=, response_body=]

Posts: 1

Participants: 1

Read full topic