-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Google Authenticator was unable to read the code #11
Comments
I don't face the issue. Btw, I have update the Google Authenticator class with the latest one. Don't know if this have an effect on this issue or not. I have upload it to my repo too! :) |
Will do, need the colleague back in the office tomorrow ;) |
@dionysius will do. But,
Is that ok? I am new to git. Teach me please :) |
@wzul then it is difficult :) no problemo, I'll have a look myself |
@wzul send us the code then we can PR the code. There is instructions on github that help make this easier. I am on phone now and as soon as possible I will send you links with help. Basically you need to fork and and send a PR after changes. |
Sorry for late. You have found my code and it was sent to pull request. Thank you :) |
I've merged the pull request of wzul so you might test it when I release the next version. If it fails: please provide (e.g. from a dummy account for privacy reasons) a screenshot of the qr-code |
Hello, Go whmcs module folder. /htdocs/modules/addons/oath Open the clientareaoath.tpl with notepad++ Find This Line : Change TO : Return oauth page and CTRL + F5 flush page. Authenticator will work this time. Regards. |
one of my users got the error message from Google Authenticator that "Is unable to interpret this code"
In German, it was "Code kann nicht ausgewertet werden"
My WHMCS version is the newest 7.1
entering the code from hand worked
The text was updated successfully, but these errors were encountered: