401 after login to webgui

Hello,
I have trouble using the seafile web interface. I was on 7.1.5, but upgraded to 8.0.4, but no change. The login page is served as it should and I can login as well with my credentials. However after login there is a red text in the right window side saying “Error”.
I checked the log files and saw several 401 errors:

#####################################################################
2021-03-30 19:34:07,999 [WARNING] django.request:228 log_response Unauthorized: /api/v2.1/notifications/
2021-03-30 19:34:08,010 [WARNING] django.request:228 log_response Unauthorized: /api/v2.1/repos/
2021-03-30 19:34:25,220 [WARNING] django.request:228 log_response Unauthorized: /api2/account/info/
2021-03-30 19:40:37,492 [WARNING] django.request:228 log_response Unauthorized: /api/v2.1/notifications/
2021-03-30 19:40:38,023 [WARNING] django.request:228 log_response Unauthorized: /api/v2.1/repos/
2021-03-30 19:40:45,362 [WARNING] django.request:228 log_response Unauthorized: /api/v2.1/notifications/
2021-03-30 19:40:45,987 [WARNING] django.request:228 log_response Unauthorized: /api/v2.1/repos/
2021-03-30 19:41:10,612 [WARNING] django.request:228 log_response Unauthorized: /api2/account/info/
2021-03-30 19:41:28,041 [WARNING] django.request:228 log_response Unauthorized: /api/v2.1/repos/
2021-03-30 19:41:28,044 [WARNING] django.request:228 log_response Unauthorized: /api/v2.1/notifications/
2021-03-30 19:41:55,054 [WARNING] django.request:228 log_response Unauthorized: /api2/account/info/
#####################################################################

I can also see those errors as 401 when using the Web browser debug tools. I am using NGINX as Proxy server but I cannot find a configuration error here.
The setup was working without error and I really do not know when this has changed for me.

I can mount webdav folders of seafile so the problem is located only somewhere in the frontend. Seafile and seahub start without problems.

Anyone an idea where I can look next?

Thank you for help.

Oh dear, I found the problem…
I have installed the browser extension ModHeader and used this to test another web application. This plugin was used to test authentication by setting a token manually. This of course interferes with seafile when the same authentication method is used.
What a bloody mistake, no error of seafile at all !

1 Like