Seafile 11.0.4 CE Error by sign in LDAP users

Hi everyone,

I had successfully implemented LDAP in my system, so I can see my “test” user from my Windows AD under Users → LDAP in my seafile control panel.
My seafile server is version 11.0.4 CE on Ubuntu 22.04. LTS and MariaDB 10.6.
(With 11.0.6 the same error appears.)
Local users are able to login.
The AD server and the seafile server are in the same subnet and can directly speech to each other.

Unfortunatly I can´t login with my test LDAP user. I have already reset the passwort in AD.
The seafile installation is clean and only a few hours old. No errors at the installation process and everything works fine.

Seahub.log gives me the following output:

[ERROR] seahub.utils.timeutils:65 timestamp_to_isoformat_timestr ‘<=’ not supported between instances of ‘int’ and ‘NoneType’
[ERROR] seahub.utils.timeutils:65 timestamp_to_isoformat_timestr ‘<=’ not supported between instances of ‘int’ and ‘NoneType’
[ERROR] seahub.base.accounts:987 authenticate ldap user test@domain.com not found.
[WARNING] django.request:241 log_response Unauthorized: /api2/repos/
[WARNING] django.request:241 log_response Unauthorized: /api2/repos/
[WARNING] django.request:241 log_response Unauthorized: /api2/repos/
[WARNING] django.request:241 log_response Unauthorized: /api2/auth/ping/
[WARNING] django.request:241 log_response Unauthorized: /api2/account/info/

When I try to see the test-AD users libaries etc. from Seafile Admin Panel:

[ERROR] seahub.api2.endpoints.admin.users:1637 get User matching query does not exits.
[WARNING] django.request:241 log_response Not Found: /api/v2.1/admin/users/test@domain.com/upload-links/
[WARNING] django.request:241 log_response Not Found: /api/v2.1/admin/users/test@domain.com/

I have set the mail attribute for this user in my AD. The LDAP config in seahub_settings.py is:

#LDAP

ENABLE_LDAP = True
LDAP_SERVER_URL = ‘ldap://172.19.0.251’
LDAP_BASE_DN = ‘CN=Users,dc=domain,dc=intern;OU=whatever,dc=domain,dc=intern’
LDAP_ADMIN_DN = ‘user@domain.intern’
LDAP_ADMIN_PASSWORD = ‘whatever’
LDAP_LOGIN_ATTR = ‘mail’
LDAP_FILTER = ‘memberOf=CN=Seafile,CN=Users,DC=domain,DC=intern’
LDAP_USER_FIRST_NAME_ATTR = ‘givenName’
LDAP_USER_LAST_NAME_ATTR = ‘sn’
LDAP_USER_NAME_REVERSE = False
LDAP_CONTACT_EMAIL_ATTR = ‘’
LDAP_USER_ROLE_ATTR = ‘’
LDAP_PROVIDER = ‘ldap’

Anyone who has ideas to this?I cannot find any information to this error…
(Yes, the BASE_CN and LDAP_FILTER attributes are correct I checked all this multiple times)
I think seafile is not able to write the LDAP user in his own database…

Greetings
Marcel

Hej,
I have exactly the same problem. It occured after changing my userbase to another DC and upgrading to 11.

Existing users still are able to login and details are displayed in admin-panel.

Not yet activated users from LDAP are listed in admin-panel, but instead of details/infos i get the error-message “user x@y not found.” These users are not able to login.
In seafile.log I receive:

2024-09-06 09:21:08,960 [WARNING] django.request:241 log_response Not Found: /api/v2.1/admin/users/xxx@example.com/
2024-09-06 09:22:13,191 [ERROR] seahub.base.accounts:987 authenticate ldap user xxx@example.com not found.

And indeed I suppose, that seafile is not able to write infos to DB or similar…

Try to upgrade to MariaDB 11 LTS and the latest Seafile CE Version. I tried to upgrade it days ago with Ubuntu 24.04 Upgrade and it works fine now.

I got it finally!!
The hell knows why, but the ldap auth started to work when I put back the ldap-config in ccnet.conf!
I thought it moved to seahub_settings.py, so I deleted it in the old place.
I compared with another instance which was still running after upgrading. There I just forgot to remove the deprecated config.

Another Error I dicovered in seafile.log was:

../common/user-mgr.c(852): Invalide db passwd format !.