-
Notifications
You must be signed in to change notification settings - Fork 13
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
Broken installation via webadmin, broken LDAP / Login #65
Comments
Seems to be a drawback of 380d91c |
It seems the LDAP plugin is not installed anymore during the installation... Running The current method, does not work:
|
Seems to be a problem with manifest handling in webadmin, right ? |
Hello ! I had the same issue, I've another issue however: when I go to mydomain.com/ where grav is install it's redirecting to mydomain.com/grav and give a 404 error. When I go to mydomain.com/home it gives me the standard home page. Would you know what is happening? Thanks |
Glad it worked for you!
Please open a dedicated issue for that. ;) |
Fixed by #67. |
Describe the bug
When trying to install the App via the Web admin panel, it freezes before I can click Install, the ask selections for domain and admin user cannot be accessed, it only shows a loading indicator forever.
Also, when trying to install via CLI (which works) and then trying to login, no user is able to login. grav.user and grav.admin permissions are given to a user, but when trying to login, it just rejects with "login failed.."
There are no meaningful logs in /var/www/grav/user/logs/grav.log or nginx or php-fpm. The normal behaviour that the grav LDAP plugin logs access rejections to this log is not present, the log only contains infos about flex-objects.
The app is broken because of these issues and can not be used
Context
Steps to reproduce
Expected behavior
Installation via Webadmin works
Login with authorized user works
Logs
Logs are empty! No Grav-related info/error messages produced, apart from the nginx 200 entries in the access logs, which are not very helpful
The text was updated successfully, but these errors were encountered: