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
Impossible to login as admin with 2.1.9 fresh install on wamp #3602
Comments
I think I had the same issue. Will need to reproduce again to be sure. Will get back to this. |
I work with wampserver 3.1.3 : |
@Moc Would be good to see the actual password string after install to determine which algorithm was used. |
Clean install with Github files, PHP 7.1. During installation:
Frontend login: Works Will do more testing with different environments asap. |
Just tested this with PHP 5.6.40 and MariaDB 10.3.12. Still no luck reproducing. Logged in both on frontend and admin area. I am sure I had a similar issue but then I only could login via frontend and not directly via admin area. |
@jipem01 Could you try and reproduce the issue on your environment and share the encrypted password strings please? |
Today I try the following :
|
@jipem01 Any luck trying to reproduce it? :) |
Tried with my setup at work... Success once but to be shure re-trie. And then no more success. And I haven't logged anything... |
You mean, you couldn't login? |
I am assuming this was caused by #4004 and that is fixed. If the issue still occurs for you, please let me know and I'll re-open. |
Hello,
Trying a fresh install today on a wamp server for local developpment. After successully installing e107 2.1.9, i try to login with login and password provided during installation, with no success (Login and password does not match an existing user etc...).
I could create a new user, and copy his encrypted password as admin password directly with phpMyAdmin, and then, it was possible to connect with admin login.
Something went wrong with password encryption during install?
I've try several installation and still same problem...
The text was updated successfully, but these errors were encountered: