-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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]: user_ldap Attempt for Paging? in Logging #31175
Comments
This comment was marked as resolved.
This comment was marked as resolved.
Yes, still on
|
Just to confirm I understand: the error is logged and those errors appear in the UI, but everything functions normally? 🤔 Can you provide the output of EDIT: I also just noted you're using NGINX. Can you confirm the following two lines exist in your nginx config: I suspect the telltale sign is that CLI test works, but not the web UI... |
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, forgot to answer.
|
I have the same issue, but running on apache2. Described it in the nextcloud forums, not solved (yet). https://help.nextcloud.com/t/attempt-for-paging-bad-search-filter/185970 |
still present in 29.0.3, seems to be related if LDAP - server has a inactivity timeout set. |
Also in v30.0.2
Raw entry:
I think it happens when accessing the LDAP config page. |
Bug description
In the admin logging I get the Error "Attempt for Paging?" from the
user_ldap
app.Not sure if related, but the LDAP/AD integration interface says
Configuration incorrect
and thatThe Base DN appears to be wrong
but when checking on command line everything appears to be correctroot@machine01:/var/www/nextcloud# sudo -u www-data ./occ ldap:test-config s03 The configuration is valid and the connection could be established!
Using google I stumbled into this owncloud/user_ldap#423 which seems related.
Steps to reproduce
Expected behavior
Installation method
Manual installation
Operating system
Debian/Ubuntu
PHP engine version
PHP 7.4
Web server
Nginx
Database engine version
MariaDB
Is this bug present after an update or on a fresh install?
Updated to a major version (ex. 22.2.3 to 23.0.1)
Are you using the Nextcloud Server Encryption module?
Encryption is Disabled
What user-backends are you using?
Configuration report
List of activated Apps
Nextcloud Signing status
Nextcloud Logs
Additional info
We are using Global Catalog (port 3269)
The text was updated successfully, but these errors were encountered: