Seadrive, seafile-client fails with sso


I have installed seafile one a VPS using the yunohost distribution (essentially debian 11). The VPS is using SSO for login for several services and I can login to seafile on the browser fine, however if I try to access with seafile-client or seadrive fails.

My installation is seafile version 9.0.2, with the default settings. The system is installed on a VPS at domain example_com seafile is using the domain files_example_com. Proper let’s encrypt certificates are installed on both domains (exchanged . with _ to avoid link restriction of forum software).

I can log into the webinterface without issue via the sso login, however if I try to use the client on my home PC (running Arch) I can not connect. What I do:

  • start seadrive-gui (same with seafile-client)
  • select login via SSO
  • use HTTPS://files_example_com as login URL.
  • The yunhost SSOlogin website appears in a s I enter my login and password.
  • Everything seems to work ok, the window closes and a window opens which says syncing file list
  • The syncing file list window just stays open
  • The indicator item menu indicates there is an unknown error.

Relevant sections from the logs (note I had to exchange the login URL with LINK inside the code below because I can’t post links):

  • ~/.seadrive/logs/seadrive.log*
    [10/14/22 13:13:14] start to serve on pipe client [10/14/22 13:13:14] http-tx-mgr.c(2255): Bad response code for GET LINK/api2/repos/: 302. [10/14/22 13:13:16] http-tx-mgr.c(5411): Bad response code for GET LINK/api2/account/info/: 302. [10/14/22 13:13:16] sync-mgr.c(832): Failed to get space usage for account LINK/

[14/10/22 13:17:07] Switched to account LINK 60464de [14/10/22 13:17:07] FetchAccountInfoRequest: failed to parse json:‘[’ or ‘{’ expected near ‘<’

So it seems to me that seadrive is getting to a wrong page when querying (I suspect and error page) and thus fails to parse the response.

Using the android client I can use the above steps without problems, hence I suspect this is a seafile issue, not a hosting issue (but please let me know if I’m incorrect).