jcr
March 14, 2018, 10:22am
1
For feature requests, please see: http://www.mattermost.org/feature-requests/ .
For troubleshooting questions, please post in the following format:
Summary
MFA QR Code + Secret not appearing after turning on MFA - Note, using NGINX with Mattermost
Steps to reproduce
Turn on MFA and try to login
Expected behavior
Would expect a QR code and secret to appear
Observed behavior
Step 2: Use Google Authenticator to scan this QR code, or manually type in the secret key
An empty box appears and nothing after Secret
lindy65
(Lindy65)
March 15, 2018, 10:56am
2
Hi @jcr ,
Thanks for your feedback,
Could you share which server version of Mattermost you have installed as well as whether this is on the browser, desktop app or mobile?
Thanks!
jcr
March 15, 2018, 11:10am
3
Hi Lindy, its Mattermost Enterprise Edition Version 4.7.1. We are getting the issue on all platforms
lindy65
(Lindy65)
March 16, 2018, 8:39am
4
Thanks @jcr ,
I’m not able to reproduce your issue on our nightly build server running off the latest master.
Can you try to reproduce the issue on your set-up on the above server?
Also, perhaps upgrading to the latest version will resolve the issue for you…
If this doesn’t work, we can ask the engineers for help as it might be related to NGINX…
jcr
March 16, 2018, 8:58am
5
Hi Lindy, thanks for getting back to me. It is definitely related to NGINX, I put it into learning mode and the issue disappeared, so it looks like NGINX is blocking it in some way. Would your engineers know a way around this?
lindy65
(Lindy65)
March 19, 2018, 7:27am
6
Hi @jcr ,
I’ve asked our engineers for their thoughts / assistance on your issue…
Hopefully have feedback for you later today…
amy.blais
(Amy Blais)
March 19, 2018, 10:06pm
7
Hi @jcr ,
To further troubleshoot this report, can you help provide the following from around the time the issue occurs:
console.log output
the developers tools network tab output
the nginx configuration.
amy.blais
(Amy Blais)
May 10, 2018, 12:16am
8
Hi @jcr Following up on this - has this been resolved or do you need further assistance with this? If you need further assistance, we will get one of our engineers to take a further look.
jcr
May 10, 2018, 2:01am
9
Hi
This is resolved, it was an nginx issue
I’m also having the same issue with nginx. how did you fix it?