@pmccarthy wrote:

Summary

Mobile notifications don't seem to be working with Team Edition.

Steps to reproduce

Mattermost Team Edition
Version: 3.3.0
Database: postgres

System Console > NOTIFICATIONS > Mobile Push

Set Enable Push Notifications to Use iOS and Android apps on iTunes and Google Play with TPNS

Set Push Notifications Server to http://push-test.mattermost.com

Set Push Notification Contents to Send generic description with user and channel names

Click Save

Expected behavior

Mobile push notifications expected, especially when desktop/browser is closed and mobile phone is locked

Observed behavior

No mobile push notifications are received.

After clicking Save in the Mobile Push settings in System Console, the settings seem to revert back to the default settings, i.e. Do not send push notifications

Posts: 1

Participants: 1

Read full topic

@pmccarthy wrote:

Summary

Identity Provider Public Certificate from Okta fails to Upload to Mattermost

Steps to reproduce

Mattermost Enterprise Edition
Version: 3.3.0
Database: postgres

System Console > AUTHENTICATION > SAML

Upload Identity Provider Public Certifcate from Okta

https://docs.mattermost.com/deployment/sso-saml-okta.html

Expected behavior

Expected behavior is for the certificate to upload properly

Observed behavior

After Uploading the certificate file, it displays Could not save certificate file

Okta provides a .cert file; I have a suspicion that this is not the format that Mattermost is expecting...

Posts: 6

Participants: 2

Read full topic

@ajoy39 wrote:

On the Mattermost iOS client of you leave the app and come back it starts the sign in flow all over again no matter how you return the app. This makes signing in with a Gitlab account with 2 factor authentication enabled impossible as by the time you have clicked the "login with Gitlab" button, entered your credentials, and gotten to the 2FA code entry screen whatever 2FA code you copied has expired.

Posts: 2

Participants: 2

Read full topic

@goa31 wrote:

hi

i am getting the below error on my mattermost

[EROR] websocket connect err: websocket: could not find connection header with token 'upgrade'
[2016/09/01 09:53:28 BST] [EROR] /api/v3/users/websocket:connect code=500

can anyone help with this . we are running of HTTP only

Posts: 1

Participants: 1

Read full topic

@stevekessler wrote:

Summary

I am trying to create an init script based on the one described in the Production Install docs. I have Centos 6.8. I have seen other help requests about the issues I am having but I have not seen anything that works.

When I run the script I get:

panic: Failed to load system translations for 'en'

I verified my configuration file with https://jsonformatter.curiousconcept.com/ .

Steps to reproduce

The code I am using for the init script is as follows:

#!/bin/sh
start on runlevel [2345]
stop on runlevel [016]
#respawn
exec /home/site/chat.site.com/mattermost/bin/platform -config=/home/site/chat.site.com/mattermost/config/config.json

I have tried many more internations of this code based on reading these forums and other Linux formus.

Expected behavior

When running this I want platform script to run. Once it is working it should run on system boot.

Observed behavior

Currently, when it runs it produces the following output.

[root@site init.d]# sh mattermost.conf
    start: Unknown job: on
    stop: Unknown job: on
    panic: Failed to load system translations for 'en'

    goroutine 1 [running]:
    panic(0xbd2b00, 0xc820010b70)
    	/usr/local/go/src/runtime/panic.go:481 +0x3e6
    github.com/mattermost/platform/utils.GetTranslationsBySystemLocale(0xd37400)
    	/var/lib/jenkins/jobs/msr/jobs/platform-release/workspace/src/github.com/mattermost/platform/utils/i18n.go:50 +0x2fd
    github.com/mattermost/platform/utils.InitTranslations(0xc82029d770, 0xc82029d790, 0xc82029d7a0)
    	/var/lib/jenkins/jobs/msr/jobs/platform-release/workspace/src/github.com/mattermost/platform/utils/i18n.go:27 +0x3e
    main.main()
    	/var/lib/jenkins/jobs/msr/jobs/platform-release/workspace/src/github.com/mattermost/platform/mattermost.go:102 +0x247

Any help with getting this to work correctly is greatly appreciated.

Thanks,
Steve

Posts: 1

Participants: 1

Read full topic

@tripkin wrote:

Hopefully this is the right place for this.

Summary

I would like to install Mattermost in my Apache vhost directory instead of /opt so that each domain can have it's own forums in a virtual hosting environment.

Steps to reproduce

I have followed the Debian Jessie install instructions with Postgres, my vhosts are managed by the latest version of virtualmin (5.04). I am also running Mattermost 3.2.0. Debian and all packages are fully upgraded and running the latest versions. I am only running packages from the official debian repositories.

To reproduce my setup, install the latest debian, selecting only ssh server - no other services or desktops. Download and install the free 10 doamin version of Virtualmin which will install and configure apache, email, etc. Install PostgreSQL from inside Virtualmin. Virtual hosting will also be setup. Create a domain and enable PostgreSQL as the database for that domain, then create a subdomain. Install Mattermost into the subdomain (or parent domain if you prefer) following the Mattermost installation guide for Debian Jessie but not installing Postgres as it is already installed. Integrate the vhost info into the domain.conf or sub.domain.conf depending on where you want to access Mattermost. After following the instructions including tests, you should have a functioning install.

Now try having Mattermost run from /home/domain/mattermost or /home/domain/domains/sub-domain/mattermost or even just put the data directory in those locations with permissions for the mattermost directory structure owned by mattermost:mattermost.

Alternatively, leaving mattermost fully installed and running from /opt/mattermost, create domain2 and then set it up so that it also accesses the same server - without exposing the first domains teams.

Expected behavior

I would like to be able to have mattermost run completely from inside a vhost so that I can cleanly migrate or backup all domain assets as the occasion arises.

Observed behavior

Everything is working from /opt/mattermost, but if I move it to /home/domain/mattermost then it does not run, or try to put the data directory in /home/domain/mattermost/data then none of that profile images work, etc.

Alternatively, I want to be able to run mattermost from domain, domain1, etc. I haven't tried this config yet and it might actually work. I will hopefully be testing the second option in the next couple of days, but it would still be nice to have the data stored in the domain for migration purposes as well as backup and restore.

Posts: 1

Participants: 1

Read full topic

@vali_shah wrote:

Hi All, I'm trying to setup Development environment and while running the test with "make test" , i'm getting the following error. Would like to request for some suggestions. Thanks. Here, i'm attaching the stack .

P.S. : I'm on MAC - OS X EL Capitan

FULL247-PRT:platform valishah$ make test
Starting docker containers
Ldap test user test.one
starting mattermost-openldap
Unable to find image 'osixia/openldap:1.1.2' locally
Pulling repository docker.io/osixia/openldap
docker: Tag 1.1.2 not found in repository docker.io/osixia/openldap.
See 'docker run --help'.
Error response from daemon: No such container: mattermost-openldap
Error response from daemon: No such container: mattermost-openldap
Error response from daemon: No such container: mattermost-openldap
Error response from daemon: No such container: mattermost-openldap
Error response from daemon: No such container: mattermost-openldap
Error response from daemon: No such container: mattermost-openldap
make: *** [start-docker] Error 1
FULL247-PRT:platform valishah$

Posts: 1

Participants: 1

Read full topic

@maddawgx9 wrote:

Summary

Certain users on our team see all other team members as being logged out.

Steps to reproduce

We have about 20 people at our company and only 2 of them have this problem. One is using Windows 10 and the other is using Windows 7. When a user who's account works on another computer logs in using one of these two computers, the same problem occurs which indicates it is a setting on the computer or perhaps some network config issue. When users log in from different network locations/configurations, the issue doesn't change, so it's likely a computer setting rather than a network issue.

Expected behavior

Users on the left-hand "Direct Messages" section and the channel dropdown should indicate with color and icon that they are logged in/connected.

Observed behavior

Users under "Direct Messages" on left hand menu appear as grey with an "x" even though they are logged in/connected to the system and other users on the same team who are working properly can see them logged in. The channel drop-down for users at the top also displays users as being logged out.

Posts: 2

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: 2

Participants: 1

Read full topic

@jdlaroche wrote:

Summary

I'm using the native app on windows 7 (v 1.3.0). The app is minimized in the small icons at the bottom right of my taskbar. When I receive a message, the small icon changes, but there is no notification showing up on my screen. The desktop notifications are enabled for all activities in my account settings and notifications are set to Always in the mattermost native app settings.

Steps to reproduce

Minimize desktop app on windows 7 and receive a new message.

Expected behavior

A notification should appear to warn you that you received a message

Observed behavior

Icon changes, but there is no notification on the screen.

Posts: 3

Participants: 2

Read full topic

@dav wrote:

With IOS app i got this message all the time since 3.3.0 and 3.4.0:
" Please check connection, Mattermost unreachable. If issue persists, ask adminsitrator to check WebSocket port."

From 3.2.0 to 3.3.0
didn't change anything in config.json or nginx.conf (in conf.d):

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

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

ssl on;
ssl_certificate /etc/nginx/conf.d/sllmatter.pem;
ssl_certificate_key /etc/nginx/conf.d/sllmatter.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: 2

Participants: 2

Read full topic

@datwiddler wrote:

We did a limited deployment to a few people to test and everything was good. we rolled it out to our entire company of 140 users and now I'm getting SQL error for users profiles and channel info and the Town square is showing message but there are no names infront of anything anymore.

from the log file

[2016/09/20 19:20:48 EDT] [EROR] /api/v3/users/profiles/hxncopn41bnxtb9zux8e7uatoh:SqlUserStore.GetProfiles code=500 rid=wc9x64uf3idb8e5a1upf51tyeh uid=53skyqit37fw9n9rmjd1nm5ata ip=208.113.14.6 We encountered an error while finding user profiles [details: sql: Scan error on column index 10: unsupported Scan, storing driver.Value type into type *string]
[2016/09/20 19:20:48 EDT] [EROR] /api/v3/users/profiles/hxncopn41bnxtb9zux8e7uatoh:SqlUserStore.GetProfiles code=500 rid=ebmqrgcjwjyg5yogse8di6hjfo uid=jfarpbsegi8gpj9zxyca6nhjxe ip=208.113.14.6 We encountered an error while finding user profiles [details: sql: Scan error on column index 10: unsupported Scan, storing driver.Value type into type *string]
[2016/09/20 19:20:48 EDT] [EROR] /api/v3/users/profiles/hxncopn41bnxtb9zux8e7uatoh:SqlUserStore.GetProfiles code=500 rid=kbg9jsoibprj5bkj3ooa4ktf5c uid=u3quuy76qidk5dxx4men6xidyc ip=204.11.121.222 We encountered an error while finding user profiles [details: sql: Scan error on column index 10: unsupported Scan, storing driver.Value type into type *string]
[2016/09/20 19:20:48 EDT] [EROR] /api/v3/users/profiles/hxncopn41bnxtb9zux8e7uatoh:SqlUserStore.GetProfiles code=500 rid=c7kc9d5r67bt3x148om7awomma uid=ia36wt694ffzup57dtd9n48r8h ip=208.113.14.6 We encountered an error while finding user profiles [details: sql: Scan error on column index 10: unsupported Scan, storing driver.Value type into type *string]
[2016/09/20 19:20:49 EDT] [EROR] /api/v3/users/profiles/hxncopn41bnxtb9zux8e7uatoh:SqlUserStore.GetProfiles code=500 rid=j5e7gqkgrfykinhh6nbthsfxre uid=wyqonkkzb3g58n1syaxaujyy7r ip=208.113.14.6 We encountered an error while finding user profiles [details: sql: Scan error on column index 10: unsupported Scan, storing driver.Value type into type *string]
[2016/09/20 19:20:49 EDT] [EROR] /api/v3/users/profiles/hxncopn41bnxtb9zux8e7uatoh:SqlUserStore.GetProfiles code=500 rid=o8i8p4xxoiy5p84qjdu6snf7jr uid=womksazsb7f5je9y7pcr9n3mrr ip=204.11.121.222 We encountered an error while finding user profiles [details: sql: Scan error on column index 10: unsupported Scan, storing driver.Value type into type *string]
[2016/09/20 19:20:49 EDT] [EROR] /api/v3/users/profiles/hxncopn41bnxtb9zux8e7uatoh:SqlUserStore.GetProfiles code=500 rid=c5wuyqmqiiyh3bmy5bkpohtiee uid=pci7dwkyjjrnbxwrf96zstu49e ip=208.113.14.6 We encountered an error while finding user profiles [details: sql: Scan error on column index 10: unsupported Scan, storing driver.Value type into type *string]
[2016/09/20 19:20:49 EDT] [EROR] /api/v3/users/profiles/hxncopn41bnxtb9zux8e7uatoh:SqlUserStore.GetProfiles code=500 rid=1oik9etd57nsdfs61esx6nk6ww uid=k6j4jtn4opdbpgps4r8cand6jy ip=208.113.14.6 We encountered an error while finding user profiles [details: sql: Scan error on column index 10: unsupported Scan, storing driver.Value type into type *string]
[2016/09/20 19:20:49 EDT] [EROR] /api/v3/users/profiles/hxncopn41bnxtb9zux8e7uatoh:SqlUserStore.GetProfiles code=500 rid=6ecmrbsdmffcie7tyhibszn9uy uid=695hpi4o9tdexgj48hz9et67za ip=208.113.14.6 We encountered an error while finding user profiles [details: sql: Scan error on column index 10: unsupported Scan, storing driver.Value type into type *string]
[2016/09/20 19:20:49 EDT] [EROR] /api/v3/users/profiles/hxncopn41bnxtb9zux8e7uatoh:SqlUserStore.GetProfiles code=500 rid=ik637t9aybgqumsfrk5nainc8w uid=t5ezfmf31tfa5ksai9ie4hc4iy ip=208.113.14.6 We encountered an error while finding user profiles [details: sql: Scan error on column index 10: unsupported Scan, storing driver.Value type into type *string]
[2016/09/20 19:20:49 EDT] [EROR] /api/v3/users/profiles/hxncopn41bnxtb9zux8e7uatoh:SqlUserStore.GetProfiles code=500 rid=3eom8fd3kj8q9ghg9qq9n5ufqe uid=bom3u15otpne9nuqepdsz6ed6c ip=204.11.121.222 We encountered an error while finding user profiles [details: sql: Scan error on column index 10: unsupported Scan, storing driver.Value type into type *string]
[2016/09/20 19:20:49 EDT] [EROR] /api/v3/users/profiles/hxncopn41bnxtb9zux8e7uatoh:SqlUserStore.GetProfiles code=500 rid=sys71o199fdnfnc93q8cdk85bo uid=mx8tuzbaifgu3gjxuo9ijqshqe ip=216.191.114.222 We encountered an error while finding user profiles [details: sql: Scan error on column index 10: unsupported Scan, storing driver.Value type into type *string]
[2016/09/20 19:20:49 EDT] [EROR] /api/v3/users/profiles/hxncopn41bnxtb9zux8e7uatoh:SqlUserStore.GetProfiles code=500 rid=z6s6sjg9rbdr88q8cyzjbb9p3a uid=sp5xs1sfj7bqpxup98pesk1zar ip=208.113.14.6 We encountered an error while finding user profiles [details: sql: Scan error on column index 10: unsupported Scan, storing driver.Value type into type *string]
[2016/09/20 19:20:49 EDT] [EROR] /api/v3/users/profiles/hxncopn41bnxtb9zux8e7uatoh:SqlUserStore.GetProfiles code=500 rid=jaahonxmstbh3exehu3rqgnhse uid=pe8ifotie3d7dx533pthhdw7zh ip=63.250.106.58 We encountered an error while finding user profiles [details: sql: Scan error on column index 10: unsupported Scan, storing driver.Value type into type *string]
[2016/09/20 19:20:49 EDT] [EROR] /api/v3/users/profiles/hxncopn41bnxtb9zux8e7uatoh:SqlUserStore.GetProfiles code=500 rid=4sehcd4mdjrridw8qzg3yofkny uid=ddjc7c6ocb8cdxo86hc98896hr ip=204.11.121.222 We encountered an error while finding user profiles [details: sql: Scan error on column index 10: unsupported Scan, storing driver.Value type into type *string]
[2016/09/20 19:20:49 EDT] [EROR] /api/v3/users/profiles/hxncopn41bnxtb9zux8e7uatoh:SqlUserStore.GetProfiles code=500 rid=acwyp1u8cbbq9ch1ahckxbcxny uid=womksazsb7f5je9y7pcr9n3mrr ip=204.11.121.222 We encountered an error while finding user profiles [details: sql: Scan error on column index 10: unsupported Scan, storing driver.Value type into type *string]

[SNIP]

Running as a VM on Ubuntu 16.04.1 LTS

Followed the instructions for a Ubuntu install.

Using Mysql as DB backend with innodb

Any ideas what happened?

Posts: 2

Participants: 1

Read full topic

@pavel wrote:

Hi,

I'm trying (and failing) to get push notifications working properly on mattermost 3.4. The relevant config.json section goes as:

    "SendPushNotifications": true,
    "PushNotificationServer": "http://push-test.mattermost.com",
    "PushNotificationContents": "generic",
    "EnableEmailBatching": true,
    "EmailBatchingBufferSize": 256,
    "EmailBatchingInterval": 30

account settings : notifications : mobile push notifications is set for all activity, online away or offline. Sending a private message from @another_users account to @user , while tagging @user shows up on @user's mm android app, but there is no notification sound and no visual notification outside the app (i.e. in the notification drawer) - tested & failed against 3 different android phones.

Is this a server or client problem?

Thanks, P.

Posts: 2

Participants: 1

Read full topic

@gubbins wrote:

Summary

Desktop client users sometimes have missing posts until they refresh

Steps to reproduce

Happens unpredictably, currently with desktop client 1.2.1 / mattermost 3.2.0 but also reported with earlier versions. Might only happen after a period of inactivity (not sure)

Expected behavior

If posts are shown in a channel, users expect all earlier posts to be visible too

Observed behavior

Sometimes an earlier post is missing, and remains missing even on further user activity, until they do a refresh in the client. There is no indication of the missing post at all, and other users can see it, so users may not even realise they are missing one (unless surrounding conversation makes it obvious!)

On earlier versions I saw an issue where a newly-joined user's posts was invisible until next refresh, but the issue reported here can affect well-established users who were already in the channel, etc.

Posts: 1

Participants: 1

Read full topic

@domrue wrote:

Hi there!

Summary

I'm trying to submit a post via the REST API.
I am able to authenticate.
However, when trying to submit the post, I get a the error "You do not have the appropriate permissions".

Steps to reproduce

I'm using Mattermost preview version 3.4.0 running in Docker.
My request is the following:

Request URL:
http://localhost:8065/api/v3/teams/teem1/channels/upmx6ed7f7b3dmazncjzmoaric/posts/create

Request body:
{"user_id":"dm1","message":"First test 12345.","channel_id":"upmx6ed7f7b3dmazncjzmoaric"}

Expected behavior

I expect a response with status code 200 and the message should be added to the message stream.

Observed behavior

I got the following error response:

{"id":"api.context.permissions.app_error","message":"You do not have the appropriate permissions","detailed_error":"","request_id":"d46p13oujpgi3bh3g6n1kdru5a","status_code":403}

What I've tried and didn't work:
Using "town-square" as the channel id. This gave another error:

{"id":"api.context.404.app_error","message":"Sorry, we could not find the page.","detailed_error":"There doesn't appear to be an api call for the url='/api/v3/teams/teem1/channels/town-square/posts/create'. Typo? are you missing a team_id or user_id as part of the url?","status_code":404}

Any ideas about what I'm doing wrong?
Thanks

Posts: 1

Participants: 1

Read full topic

@ngcnelson wrote:

Summary

In the payload of an incoming webhook, specifying a user results in error 500 "Couldn't find the channel"

Steps to reproduce

1. Create incoming webhook
2. Open Firefox (or web browser with capability to POST and pass parameters)
3. Use the URL of the webhook and post the suggested example in the documentation (Make sure to put application/json in the content type of the header):
   {"text": "Hello, this is some text."}
4. Message should appear in the channel
5. Try again, but now add the channel property
   {"channel":"@username","text": "Hello, this is some text."}
6. Enter a valid user name in @username (leave the @ sign).
7. Post will now fail with a 500 error and message "Couldn't find the channel"
8. Changing channel property to a public channel works. Only with @username is not working.

Expected behavior

As per documentation, "the message will be sent to that user’s direct message channel"

Observed behavior

Returned JSON:
{"id":"web.incoming_webhook.channel.app_error","message":"Couldn't find the channel","detailed_error":"","request_id":"8aajaxpkybn8mmm7t4nkefnrca","status_code":500}

Also, misspelling the username or putting an invalid username results in "Couldn't find the user". So maybe the problem is that there's no "channel" message for the user (as in Slack, the user can have private messages with themselves)

Posts: 1

Participants: 1

Read full topic

@gabx wrote:

I am attempting to connect Mattemost to Postgresql DB via the Unix socket and NOT the tcp one as described in the docs.
1- I modified the pg_hba.conf and pg_ident.conf postgresql files accordingly to allow a local connection to mattermost DB from user mmuser, which is mapped to mattermost Unix user.

pg_hba.conf
local   mattermost          mmuser                      peer       map=mattermap

pg_ident.conf
mattermap      mattermost              mmuser

2- I changed the URI in config.json this way:
postgres://mmuser:XXYYY@/mattermost?connect_timeout=10

NB:
- I know this command is correct as I tested it with the unix psql command.
- from postgresql docs, sslmode is ignored for Unix domain socket communication.

When running # ./plateform, I have this error:
Failed to ping db err:pq: SSL is not enabled on the server

Why do this arise ?

Posts: 1

Participants: 1

Read full topic

@lobsang wrote:

I followed the guide "Production Install on Ubuntu 14.04 LTS" and I have successfully installed it (3.4.0) in one machine configuration.
Everything seems to works, but after a while the server has started, the mattermost service always stops working. I have to restart the server to see mattermost working again.
Here is the log:
[2016/10/09 22:50:59 CEST] [INFO] Server is initializing...
[2016/10/09 22:50:59 CEST] [INFO] Pinging sql master database
[2016/10/09 22:50:59 CEST] [INFO] Pinging sql replica-0 database
[2016/10/09 22:51:01 CEST] [WARN] Unable to find active license
[2016/10/09 22:51:01 CEST] [INFO] Starting Server...
[2016/10/09 22:51:01 CEST] [INFO] Server is listening on :8065
[2016/10/09 22:51:01 CEST] [INFO] RateLimiter is enabled
[2016/10/09 22:55:32 CEST] [EROR] Invalid session token=475yuw79m7rwfy8qrkder8t1zh, err=sessionIdOrToken=475yuw79m7rwfy8qrkder8t1zh
[2016/10/10 07:44:51 CEST] [INFO] Stopping Server...

Posts: 1

Participants: 1

Read full topic

@andrea wrote:

I have Omnibus Gitlab and Mattermost installed on two separate machines. Both use HTTPS with Let's encrypt certificates and HTTPS works fine.

The problem is that when I use SSO with Gitlab, Mattermost returns the dreadful error: Bad response from token request. The log file is the following (note how the details section is empty!):

[EROR] /signup/gitlab/complete:AuthorizeOAuthUser code=500 rid=o9nzr1yjbtr15xqi5hy8pwssnh uid= ip=68.194.84.101 Bad response from token request [details: ]

I have tried including Let's encrypt certificate authority as explained in other posts, etc. but it did not help. Any Suggestions? Would love to solve this issue.

Thanks!

Posts: 1

Participants: 1

Read full topic

@MaitreDede wrote:

Hi !

Summary

I can't authenticate the Android client on my Mattermost instance with Gitlab authentication.

Steps to reproduce

Install the android client (3.4.1), connect to a mattermost server with only gitlab authentication, click "gitlab" link to authenticate...

The gitlab authentication page is opened in android's browser, not inside the app. So I am authenticated inside the brower, not the app.

Expected behavior

I expect that the authentication form of Gitlab is opened inside mattermost app.

Observed behavior

On desktop browser, it works fine, and there is no popup.

I am using Android 4.4.3.

Posts: 2

Participants: 2

Read full topic