This repository has been archived by the owner on Feb 22, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 20
can't create an account/ sign in. Password entry bug #118
Comments
@vrnico, I'm looking into it. I'll try to recreate the issue on my end and figure out the solution. Will get back to you asap! |
@vrnico, thanks for your patience! I looked into what you said above:
I'll let you know as soon as the password error resolution is merged into the master branch. You can then redeploy to Heroku and sign up on your self-hosted version successfully! |
@vrnico, the fix has been pushed to master. Feel free to redeploy, you should be able to create an account on your self-hosted version without any issues now. |
@harshamurthy hey just redeployed, and was able to sign in! solid job! |
Could it be that the error exists again? On a self-hosted herokuapp I see the same as the screenshot shows above. A login is not possible. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I've tried making/ signing in with a Google account on a self-hosted herokuapp, and on the usevolition.com portal. While I can't get the self-hosted sign up or sign on to work, I have been able to access my account through signing in through my Google account on the usevolition portal. Upon trying to sign up for an account on volition.com and in my heroku app I am unable to complete the form post because it is failing to reference it against the 100 most common passwords (pictured above). Any ideas on how to fix this?
Also any guidelines on running volition without authentication on a local vm?
The text was updated successfully, but these errors were encountered: