Initial google authentication setup stuck in loop, cant get back to site

[luckyshoot3r]

• I have enabled debug mode
• [ x] I have read checked the Common Issues page

Just recently set up Snipe IT. Attempted to set up MFA using google authentication. After setting it to required for all users, it then prompted me with a qr code and a box for the code. After adding the qr code to google authenticator and then pasting mfa code into the box i'm now stuck in a loop. i click "submit code" and it takes me back to the same page asking me for a code. any help is welcome.

• Snipe-IT Version: 4.9.4
• OS: Windows Server 2012 r2
• Web Server: IIS
• PHP Version: 7.3.20

[snipe]

We've never seen this loop before. My guess would be something else is amiss and the 2FA is just conflating the original issue. Something possibly misconfigured in your .env. Not exactly sure how to help you troubleshoot here though, since it's not reproducible on our end. Can you disable 2FA and see if you can see anything funny in your browser's console?

[luckyshoot3r]

Thanks for the reply. In this particular scenario there was no way to ever disable 2fa because when I would try to log it kept prompting me over and over for 2fa on all users. I was essentially locked out. I went into the sql database and just deleted the user and settings table and it let me back in, however. Kind of had to start over but it is what it is. Now that I’m back in, should I send you some logs? Or a copy of the .env file? From: snipe <[email protected]> Sent: Friday, July 24, 2020 2:38 PM To: snipe/snipe-it <[email protected]> Cc: Russell Matthews <[email protected]>; Author <[email protected]> Subject: Re: [snipe/snipe-it] Initial google authentication setup stuck in loop, cant get back to site (#8259) CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. We've never seen this loop before. My guess would be something else is amiss and the 2FA is just conflating the original issue. Something possibly misconfigured in your .env. Not exactly sure how to help you troubleshoot here though, since it's not reproducible on our end. Can you disable 2FA and see if you can see anything funny in your browser's console? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<#8259 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AQL6ECMZRRXWG4SSKPDDKTDR5H5LXANCNFSM4PFJNDWQ>.

[stale]

Is this still relevant? We haven't heard from anyone in a bit. If so, please comment with any updates or additional detail.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Don't take it personally, we just need to keep a handle on things. Thank you for your contributions!

[luckyshoot3r]

I basically had to start over. Bummer! Thanks for reaching out though.

…

________________________________ From: stale[bot] <[email protected]> Sent: Saturday, October 3, 2020 10:21:12 PM To: snipe/snipe-it <[email protected]> Cc: Russell Matthews <[email protected]>; Author <[email protected]> Subject: Re: [snipe/snipe-it] Initial google authentication setup stuck in loop, cant get back to site (#8259) CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. Is this still relevant? We haven't heard from anyone in a bit. If so, please comment with any updates or additional detail. This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Don't take it personally, we just need to keep a handle on things. Thank you for your contributions! — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<#8259 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AQL6ECKZG4ETR7G6J4FMXSDSJAA4RANCNFSM4PFJNDWQ>.

[stale]

Okay, it looks like this issue or feature request might still be important. We'll re-open it for now. Thank you for letting us know!

[stale]

Is this still relevant? We haven't heard from anyone in a bit. If so, please comment with any updates or additional detail.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Don't take it personally, we just need to keep a handle on things. Thank you for your contributions!