Summary Getting Token request failed error on MM 4.3.2 using Gitlab Omnibus Steps to reproduce I am using Gitlab 10.2.2 and MM 4.3.2. Each on separate VM. Expected behavior I have MM configured to only allow Sign-In with Gitlab (Gitlab SSO). When I try to sign-in, MM should login directly but inst…

Hi @aitzubi @m407 Our devs have been trying to troubleshoot this issue on the GitLab forum , so, to prevent duplicate postings, I’ll close this issue off here and we can track it via GitLab forum.

[SOLVED] MM 4.3.2 Token request failed

Troubleshooting

lindy65 (Lindy65) December 7, 2017, 8:05am 2

Hi @aitzubi,

Thanks for your feedback,

This issue may be fixed in the latest version of Mattermost but I think you’ll need to wait for GitLab to upgrade to this version?

Topic		Replies	Views
[SOLVED] MM 4.2 to 4.3 - Gitlab authentication in error Troubleshooting	1	1509	October 24, 2017
"Token request failed" error on GitLab Mattermost Troubleshooting	7	6040	April 5, 2020
Configure stand-alone mattermost with gitlab sign-on Troubleshooting	16	7576	August 29, 2019
Token Request Error on Omnibus with Reverse Proxy Troubleshooting	3	3200	June 26, 2018
Gitlab-Mattermost behind AWS ALB does not work, i/o timeout Troubleshooting	0	1875	February 4, 2020

[SOLVED] MM 4.3.2 Token request failed

Related topics