No Login after Upgrade

Seafile Server
1

Call me crazy but I went from version 11 to 12 and then to 13 in one day. Weird thing is my mobile sync apps work fine, I can login and all but only when I try to login via WEB I get this error

[2025-09-24 10:39:25] [WARNING] seahub.auth.views:160 login Login attempt limit reached, show Captcha, email/username: jochen@example.com, ip: 2001:1111:2222:29::1042, attempts: 5
[2025-09-24 10:39:34] [WARNING] seahub.auth.views:160 login Login attempt limit reached, show Captcha, email/username: jochen@example.com, ip: 2001:1111:2222:29::1042, attempts: 6
[2025-09-24 10:39:42] [WARNING] seahub.auth.views:160 login Login attempt limit reached, show Captcha, email/username: jochen@example.com, ip: 2001:1111:2222:29::1042, attempts: 7
[2025-09-24 10:41:12] [WARNING] seahub.auth.views:172 login Login attempt limit reached, show Captcha, ip: 2001:1111:2222:29::1042, attempts: 7
[2025-09-24 10:41:17] [WARNING] seahub.auth.views:160 login Login attempt limit reached, show Captcha, email/username: jochen@example.com, ip: 2001:1111:2222:29::1042, attempts: 8
[2025-09-24 10:46:41] [WARNING] seahub.auth.views:160 login Login attempt limit reached, show Captcha, email/username: jochen@example.com, ip: 2001:1111:2222:29::1042, attempts: 9
[2025-09-24 11:00:14] [ERROR] django.request:246 log_response Internal Server Error: /api/v2.1/admin/users/jochen@example.com/share-links/
Traceback (most recent call last):
  File "/opt/seafile/seafile-server-13.0.8/seahub/thirdpart/django/core/handlers/exception.py", line 55, in inner
    response = get_response(request)
               ^^^^^^^^^^^^^^^^^^^^^
  File "/opt/seafile/seafile-server-13.0.8/seahub/thirdpart/django/core/handlers/base.py", line 197, in _get_response
    response = wrapped_callback(request, *callback_args, **callback_kwargs)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/seafile/seafile-server-13.0.8/seahub/thirdpart/django/views/decorators/csrf.py", line 56, in wrapper_view
    return view_func(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/seafile/seafile-server-13.0.8/seahub/thirdpart/django/views/generic/base.py", line 105, in view
    return self.dispatch(request, *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/seafile/seafile-server-13.0.8/seahub/thirdpart/rest_framework/views.py", line 509, in dispatch
    response = self.handle_exception(exc)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/seafile/seafile-server-13.0.8/seahub/thirdpart/rest_framework/views.py", line 469, in handle_exception
    self.raise_uncaught_exception(exc)
  File "/opt/seafile/seafile-server-13.0.8/seahub/thirdpart/rest_framework/views.py", line 480, in raise_uncaught_exception
    raise exc
  File "/opt/seafile/seafile-server-13.0.8/seahub/thirdpart/rest_framework/views.py", line 506, in dispatch
    response = handler(request, *args, **kwargs)
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/seafile/seafile-server-13.0.8/seahub/seahub/api2/endpoints/admin/users.py", line 1658, in get
    link_info = get_user_share_link_info(fs)
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/seafile/seafile-server-13.0.8/seahub/seahub/api2/endpoints/admin/users.py", line 294, in get_user_share_link_info
    data['size'] = seafile_api.get_file_size(repo.store_id,
                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/seafile/seafile-server-13.0.8/seafile/lib/python3/site-packages/seaserv/api.py", line 202, in get_file_size
    return seafserv_threaded_rpc.get_file_size(store_id, version, file_id)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/seafile/seafile-server-13.0.8/seafile/lib/python3/site-packages/pysearpc/client.py", line 127, in newfunc
    return fret(ret_str)
           ^^^^^^^^^^^^^
  File "/opt/seafile/seafile-server-13.0.8/seafile/lib/python3/site-packages/pysearpc/client.py", line 11, in _fret_int
    raise SearpcError(dicts['err_msg'])
pysearpc.common.SearpcError: Invalid file id
[2025-09-24 11:01:19] [WARNING] django.request:246 log_response Unauthorized: /api2/repos/
[2025-09-24 11:15:04] [WARNING] django.request:246 log_response Unauthorized: /api/v2.1/repos/3960c580-bd61-412f-8bce-02e55be70175/dir/
[2025-09-24 15:30:57] [WARNING] seahub.auth.views:160 login Login attempt limit reached, show Captcha, email/username: jochen@example.com, ip: 2001:3333:4444:fe:12ff:e0ff:fe4e:51d1, attempts: 5
[2025-09-24 15:38:51] [WARNING] django.request:246 log_response Not Found: /.git/config

I created a new superuser via the reset-admin.shand with it I can login. I cannot allow to loose my shares and stuff because when I migrated my data to a new user. What I saw in DB is that my failing user is just carrying the login email in the email field in the EmailUser column.
The resetted and working user is like this: 6c91c112b3684f9fa691641e2adeiycc3@auth.local
Anyone got an idea what’s going on? I read something about native authentication and stuff but my mariadb 10.11 seems to have that configured for the user I login to the DB with. Running in podman containers btw.

Thanks so much

2

Hello, this seems like an error related to the data storage. Could you check again what errors are in seafile.log?

3

This is from my seafile.log

2025-09-24 12:31:55] [INFO] seafile-session.c(64): fileserver: web_token_expire_time = 3600
[2025-09-24 12:31:55] [INFO] seafile-session.c(76): fileserver: max_index_processing_threads= 3
[2025-09-24 12:31:55] [INFO] seafile-session.c(89): fileserver: fixed_block_size = 8388608
[2025-09-24 12:31:55] [INFO] seafile-session.c(101): fileserver: max_indexing_threads = 1
[2025-09-24 12:31:55] [INFO] ../common/seaf-utils.c(392): Use database Mysql
[2025-09-24 12:31:55] [INFO] http-server.c(196): fileserver: worker_threads = 10
[2025-09-24 12:31:55] [INFO] http-server.c(207): fileserver: verify_client_blocks = 1
[2025-09-24 12:31:55] [INFO] http-server.c(229): fileserver: cluster_shared_temp_file_mode = 600
[2025-09-24 12:31:55] [INFO] socket file exists, delete it anyway
[2025-09-24 12:34:25] [WARNING] ../common/seaf-db.c(928): Failed to prepare sql SELECT 1;: Lost connection to server during query
[2025-09-24 12:47:57] [INFO] seafile-session.c(64): fileserver: web_token_expire_time = 3600
[2025-09-24 12:47:57] [INFO] seafile-session.c(76): fileserver: max_index_processing_threads= 3
[2025-09-24 12:47:57] [INFO] seafile-session.c(89): fileserver: fixed_block_size = 8388608
[2025-09-24 12:47:57] [INFO] seafile-session.c(101): fileserver: max_indexing_threads = 1
[2025-09-24 12:47:57] [INFO] ../common/seaf-utils.c(392): Use database Mysql
[2025-09-24 12:47:57] [INFO] http-server.c(196): fileserver: worker_threads = 10
[2025-09-24 12:47:57] [INFO] http-server.c(207): fileserver: verify_client_blocks = 1
[2025-09-24 12:47:57] [INFO] http-server.c(229): fileserver: cluster_shared_temp_file_mode = 600
[2025-09-24 17:43:02] [INFO] seafile-session.c(64): fileserver: web_token_expire_time = 3600
[2025-09-24 17:43:02] [INFO] seafile-session.c(76): fileserver: max_index_processing_threads= 3
[2025-09-24 17:43:02] [INFO] seafile-session.c(89): fileserver: fixed_block_size = 8388608
[2025-09-24 17:43:02] [INFO] seafile-session.c(101): fileserver: max_indexing_threads = 1
4

anybody got an idea how to get this up and running again?

5

Login Attempt Limit Reached: The error logs indicate that the login attempts from the IP address have reached the limit, resulting in a captcha requirement. This can happen due to multiple failed login attempts. To resolve this, ensure that proper email and credentials are being used for the user jochen@example.com.

You can also set a contact email for this user jochen@example.com as below in the admin panel, the contact email can be used for login.

image
image1886×788 53.1 KB

Then you can reset password for that user to a simple one and try again.

In your log, you have Invalid File ID Error. But this is not related to the login issue as the time for this error log is far apart from the error log for login failing.