SeaDrive: Cannot login via SSO in Linux (Gnome/Wayland)

Hi,

I am testing using SeaDrive with the latest Debian Linux using Gnome. After i install the latest version of SeaDrive for Linux, in the Add Account screen i select Single Sign On. This opens a smaller window where i type in the address of the Seafile server and then a small browser window appear that has a blank white screen. This is supposed to show the SSO webpage but for some unknown reason on Gnome (or Wayland) built-in web browser cannot load the SSO page, thus i am not able to pass the login.

This works in windows, which i guess has a different underlying browser which loads the page.

Is there a way to bypass that or use an alternative way to login via SSO in Gnome?

I have also tested with a KDE environment with the same result as they both use Wayland as their backend.

Thanks

You can set the below option to true in seahub_settings.py:

CLIENT_SSO_VIA_LOCAL_BROWSER = True

This will ask the client to use local browser on your computer.

Refer to seahub_settings.py - Seafile Admin Manual

Thank you, that works.

This doesn’t work on Ubuntu 24.04..
It works on windows though

It may be due to some special problem on your computer. You can have a look at seadrive-gui.log. Which version of SeaDrive do you use?

Hi! I have a similar issue. On PopOS 24.04. the in-app browser does not seem to work: the auth URL itself appears correct and I can log in successfully in the browser, but the in-app browser is just stuck and never loads anything. Meanwhile, if I set the LOCAL_BROWSER flag as suggested above, the client just tells me “Failed to get client SSO link”. On Windows and MacOS, I have no login issues.

Any suggestion how to debug this? Where can I find the seadrive-gui.log?

Which version of Seafile server do you use? Please post the client log when you meet the error.

Hi! Sorry for the late reply. The server version is 11.0.13… Now that I think of it, that’s probably quite old. I’ll try to upgrade it as soon as I can, and hopefully that should help… Thank you for the response.

Hi all, I’m experiencing the same issue with Linux Mint 22.3 Zena, and sadly the CLIENT_SSO_VIA_LOCAL_BROWSER workaround doesn’t help.

Seafile server: 13.0.21
Seafile client: Seafile-x86_64-9.0.18.AppImage

I’m self-hosting seafile, using Authelia and LLDAP to drive user management, authn and authz. This is working without issues across a number of devices. However, from Linux, I’m not able to SSO.

  • When CLIENT_SSO_VIA_LOCAL_BROWSER = False, the “Single Sign On” button opens an embedded browser that stays like that (white screen).
  • When CLIENT_SSO_VIA_LOCAL_BROWSER = True, the “Single Sign On” button leads to an external login page in my default browser (Firefox). I can log in without issues, in the browser, but the client doesn’t seem to notice the login success.

Could you check applet.log for any error messages during the login?

Of course, just re-attempted a new login via the embedded browser and found this (I’ve replaced username and domain):

[06/02/2026 09:32:37 AM]read id from id file (/root/seafile-client/src/seafile-applet.cpp:841)
[06/02/2026 09:32:37 AM]client id is 8a23a4d42a2331ae452e4b1963a6bb75db771043 (/root/seafile-client/src/seafile-applet.cpp:253)
[06/02/2026 09:32:37 AM]starting seaf-daemon:  ("-c", "/home/myuser/.ccnet", "-d", "/home/myuser/Seafile/.seafile-data", "-w", "/home/myuser/Seafile") (/root/seafile-client/src/daemon-mgr.cpp:120)
[06/02/2026 09:32:37 AM]daemon mgr: init => starting (/root/seafile-client/src/daemon-mgr.cpp:213)
[06/02/2026 09:32:37 AM]seafile daemon is now running, checking if the service is ready (/root/seafile-client/src/daemon-mgr.cpp:131)
[06/02/2026 09:32:37 AM]daemon mgr: starting => connecting (/root/seafile-client/src/daemon-mgr.cpp:213)
[06/02/2026 09:32:38 AM][Rpc Client] connected to daemon (/root/seafile-client/src/rpc/rpc-client.cpp:118)
[06/02/2026 09:32:38 AM]seaf daemon is ready (/root/seafile-client/src/daemon-mgr.cpp:142)
[06/02/2026 09:32:38 AM]daemon mgr: connecting => connected (/root/seafile-client/src/daemon-mgr.cpp:213)
[06/02/2026 09:32:38 AM][Rpc Client] connected to daemon (/root/seafile-client/src/rpc/rpc-client.cpp:118)
[06/02/2026 09:32:38 AM]Starting the network status detector (/root/seafile-client/src/network-mgr.cpp:194)
[06/02/2026 09:32:38 AM][AutoUpdateManager] cancel all download tasks (/root/seafile-client/src/filebrowser/auto-update-mgr.cpp:109)
[06/02/2026 09:32:38 AM][AutoUpdateManager] clean file caches db (/root/seafile-client/src/filebrowser/auto-update-mgr.cpp:118)
[06/02/2026 09:32:38 AM][AutoUpdateManager] clean file caches (/root/seafile-client/src/filebrowser/auto-update-mgr.cpp:121)
[06/02/2026 09:32:38 AM][AutoUpdateManager] removing cached files (/root/seafile-client/src/filebrowser/auto-update-mgr.cpp:428)
[06/02/2026 09:32:38 AM]starting applet rpc service (/root/seafile-client/src/rpc/rpc-server.cpp:222)
[06/02/2026 09:32:38 AM]socket file exists, delete it anyway
[06/02/2026 09:32:38 AM]applet rpc service started (/root/seafile-client/src/rpc/rpc-server.cpp:227)
[06/02/2026 09:32:44 AM]ServerStatusService: ignore request for host "drive.mydomain.com" (/root/seafile-client/src/server-status-service.cpp:157)
[06/02/2026 09:32:44 AM]Sandboxing disabled by user. ((null):0)
[06/02/2026 09:32:45 AM]Uncaught SyntaxError: Unexpected token '=' (https://auth.mydomain.com/static/js/index.BrTK6y2i.js:2)

Thanks for your help!

The embedded browser wasn’t updated frequently. So it’s likely not compatible with the web page. Could you check the log after login with local browser?

It looks like this:


[06/03/2026 09:49:00 AM]ServerStatusService: ignore request for host "drive.mydomain.com" (/root/seafile-client/src/server-status-service.cpp:157)

[06/03/2026 09:49:00 AM]waiting for client sso login (/root/seafile-client/src/ui/login-dialog.cpp:516)

[06/03/2026 09:49:03 AM]ServerStatusService: ignore request for host "drive.mydomain.com" (/root/seafile-client/src/server-status-service.cpp:157)

[06/03/2026 09:49:03 AM]waiting for client sso login (/root/seafile-client/src/ui/login-dialog.cpp:516)

[06/03/2026 09:49:06 AM]ServerStatusService: ignore request for host "drive.mydomain.com" (/root/seafile-client/src/server-status-service.cpp:157)

[06/03/2026 09:49:06 AM]waiting for client sso login (/root/seafile-client/src/ui/login-dialog.cpp:516)

[06/03/2026 09:49:09 AM]ServerStatusService: ignore request for host "drive.mydomain.com" (/root/seafile-client/src/server-status-service.cpp:157)

[06/03/2026 09:49:09 AM]waiting for client sso login (/root/seafile-client/src/ui/login-dialog.cpp:516)

[06/03/2026 09:49:12 AM]ServerStatusService: ignore request for host "drive.mydomain.com" (/root/seafile-client/src/server-status-service.cpp:157)

[06/03/2026 09:49:12 AM]waiting for client sso login (/root/seafile-client/src/ui/login-dialog.cpp:516)

[06/03/2026 09:49:15 AM]ServerStatusService: ignore request for host "drive.mydomain.com" (/root/seafile-client/src/server-status-service.cpp:157)

[06/03/2026 09:49:15 AM]waiting for client sso login (/root/seafile-client/src/ui/login-dialog.cpp:516)

[06/03/2026 09:49:18 AM]ServerStatusService: ignore request for host "drive.mydomain.com" (/root/seafile-client/src/server-status-service.cpp:157)

[06/03/2026 09:49:18 AM]waiting for client sso login (/root/seafile-client/src/ui/login-dialog.cpp:516)

[06/03/2026 09:49:21 AM]ServerStatusService: ignore request for host "drive.mydomain.com" (/root/seafile-client/src/server-status-service.cpp:157)

[06/03/2026 09:49:21 AM]waiting for client sso login (/root/seafile-client/src/ui/login-dialog.cpp:516)

[06/03/2026 09:49:24 AM]ServerStatusService: ignore request for host "drive.mydomain.com" (/root/seafile-client/src/server-status-service.cpp:157)

[06/03/2026 09:49:24 AM]waiting for client sso login (/root/seafile-client/src/ui/login-dialog.cpp:516)

[06/03/2026 09:49:25 AM]ServerStatusService: ignore request for host "drive.mydomain.com" (/root/seafile-client/src/server-status-service.cpp:157)

[06/03/2026 09:49:25 AM]begin sso login via local browser (/root/seafile-client/src/ui/login-dialog.cpp:457)

[06/03/2026 09:49:25 AM]ServerStatusService: ignore request for host "drive.mydomain.com" (/root/seafile-client/src/server-status-service.cpp:157)

[06/03/2026 09:49:25 AM]open sso link in browser: "https://drive.mydomain.com/client-sso/e91d80fa7932450fb1ae77b4e918b21f1f9a3d9b5c4383bea4d16c8c247a/" (/root/seafile-client/src/ui/login-dialog.cpp:477)

[06/03/2026 09:49:28 AM]ServerStatusService: ignore request for host "drive.mydomain.com" (/root/seafile-client/src/server-status-service.cpp:157)

[06/03/2026 09:49:28 AM]waiting for client sso login (/root/seafile-client/src/ui/login-dialog.cpp:516)

[06/03/2026 09:49:31 AM]ServerStatusService: ignore request for host "drive.mydomain.com" (/root/seafile-client/src/server-status-service.cpp:157)

[06/03/2026 09:49:31 AM]waiting for client sso login (/root/seafile-client/src/ui/login-dialog.cpp:516)

[06/03/2026 09:49:34 AM]ServerStatusService: ignore request for host "drive.mydomain.com" (/root/seafile-client/src/server-status-service.cpp:157)

[06/03/2026 09:49:34 AM]waiting for client sso login (/root/seafile-client/src/ui/login-dialog.cpp:516)

Again, the auth succeeds in the browser without issues.