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
[Bug] Unable to log in. #984
Comments
This definitely sounds like a bug, but I haven't experienced it and have done many installs of BB while developing it. Since 4.22-beta.1 is so old, could you try this upcoming release? it's not officially out, but it has a fair few bug fixes and security improvements. Hasn't been thoroughly tested yet but I'm pretty sure it should be just as if not more stable than the version you're trying. This is just the current master branch but with all of the composer dependencies pre-packaged. If for whatever reason you don't feel comfortable with this then download the current mast branch and user composer to install the dependencies as directed in our readme. 4.22-beta.2 (updated 8/23/21) If you're going to try re-using your current config please take note of the new config options which must be added.
It may also be helpful to know what software the webserver is being run on and the respective versions. Thanks |
@it911now Hi there, haven't heard back from you in quite awhile. |
What happened?
After logging out of the BoxBilling site, I am unable to log into the site.
a)I copied the password HASH from the working user account to the admin user "pass" field but that didn't work either.
b) So in looking at another Boxbilling issue about the trailing slash, I noticed that there is a SALT included in the bb-config.php file but not in the database in the "table:admin".
So to fix the problem, I copied the salt from the bb-config.php file and placed it in the salt field for each user, and this allowed all the users to log into the site.
My question is,
BoxBilling Version
v4.22-beta.1
What version of PHP are you running?
7.4x
Additional Notes
Additional notes
The text was updated successfully, but these errors were encountered: