SeaDrive 3.0.2 is released!

Hi all,

SeaDrive 3.0.2 is released. The Windows version is stable and is available for download on official website. The macOS version is still in Beta and can be downloaded here:

The main changes are:

  • [mac] Use File Provider API to implement virtual drive (works for macOS 12.1 or later)
  • Allow syncing multiple accounts at the same time
  • Support notification server, which makes library and locked files update more timely

The notification server feature will be available in Seafile server 10.0.1 version.


It’s great! Thanks for working

Thanks for the macOS version 3.0.2 !
I just installed it and noticed a few things, maybe you can comment on them:

  1. QuickLook via Spacebar is not working. Is this a restriction made by the File Provider API or something you guys are still working on? In SeaDrive v2.x QuickLook via Spacebar worked as it should, it started playing back an audio file or showed the image, without the need to download it before. Now QuickLook only works after clicking the little cloud download icon and waiting for it to download.

  2. Right click Options are almost all gone? I have no right-click options when a file is “online only”, and when i download it via the cloud icon i only get the option to “lock” or “unlock” the file. No more (essential) options like “create a shared link” etc.

  3. “Removing” a downloaded file - no more option to manually remove a downloaded file from the cache and make it online-only again? Will this only happen with the automatic cache clear setting in seadrive’s settings?

In 2.x version the file can be read partially. In 3.x it’s not possible as the file provider API doesn’t support it. So video and audio files cannot be previewed. Thumbnails for image files are fetched from the server so the spacebar should work. We don’t have thumbnails for video and audio files on the server.

Creating links will be added later.

There is such an option in the right-click menu. This is provided by the OS.

I can’t get SeaDrive to show up in my finder window. I tried all the steps with SeaDrive 3.0.1 with rebooting, removing the meta data, fresh install of SeaDrive 3.0.2 but nothing in the finder despite the fact I have successfully entered a password for one of my encrypted libraries.

Hello @Larrikin , can you send us the logs of seadrive? You can get the logs through the open logs folder of the tray icon, and then email them to

Hi. I ended up getting it working by following the attached instructions. Note that you guys are clearly heading in the right direction with this so thanks for the great work. It would be great to have a feature where you can “pin” directories so always be synced so you can choose which directories to sync and which ones not too. That would save me having so many libraries as the seafile client doesn’t give me the option other than to sync the library (so I am using libraries as directory names). I saw there is a “Download Now” button for a directory but it quickly removes the cache of that directory. I’d like to have it something like “Permanently keep downloaded and synced” and also the ability to uncheck it later and operate back like on demand again.

Perhaps the downloaded files are removed by the automatic cache cleaning routine in the client. You can change the cache size to a larger number if you want to cache a lot of files. This can be change from the settings dialog.

I have no doubt that is happening but the feature I am asking for is to bypass the cache. I’ve seen this in other clients doing similar things to you. They call it “pinning” a directory which means it keeps it downloaded permanently and sync’d. Changing the cache is not the solution as it is unworkable to manage the variability.

I’ve install SeaDrive 3.0.2 on Windows and the following errors occur in the seadrive.log every minute:

[04/12/23 09:22:09] libcurl failed to GET Server returned nothing (no headers, no data).
[04/12/23 09:22:09] Failed to get fs id list for repo e9f8c1d9 on server
[04/12/23 09:22:09] Transfer repo 'e9f8c1d9': ('normal', 'fs') --> ('error', 'finished')
[04/12/23 09:22:09] Repo 'APP_DEPLOY_TEMP' sync state transition from downloading to 'error': 'Error occured in download.'.
[04/12/23 09:22:09] Repo 'APP_DEPLOY_TEMP' sync state transition from 'synchronized' to 'get sync info'.
[04/12/23 09:22:09] Repo 'APP_DEPLOY_TEMP' sync state transition from 'get sync info' to 'downloading'.
[04/12/23 09:22:09] Download with HTTP sync protocol version 2.
[04/12/23 09:22:09] Transfer repo 'e9f8c1d9': ('normal', 'init') --> ('normal', 'check')
[04/12/23 09:22:09] Transfer repo 'e9f8c1d9': ('normal', 'check') --> ('normal', 'commit')
[04/12/23 09:22:09] Transfer repo 'e9f8c1d9': ('normal', 'commit') --> ('normal', 'fs')

This library has a folder contain 700k subfolders and 7TB capacity! Is SeaDrive reading this library once a minute too short? How can I increase the time SeaDrive reads and syncs this library?

We’ll consider adding this feature.


Thank you. I think it would be a great feature and would make a huge difference in using Seafile. I appreciate you considering it.

The new SeaDrive Client 3.0.2 for Windows has the following problem:

Problem 1 - No synchronization despite network connection:
If SeaDrive is started automatically with Windows and initially there is no network connection (for example on a laptop that logs on via WLAN), then the data is not synchronized. The client shows the familiar green check mark as an icon in the taskbar, but newly created data (regardless of file type) is not loaded into the cloud and data created or edited in the cloud is not displayed locally in the file explorer.

Only when the client is restarted again after a network connection (internet connection), then it works. There seems to be a very malicious bug included here. I have not observed this phenomenon with previous versions.

Tested under Windows 10 Pro (build 19045) in combination with SeaFile Professional 9 (latest version).

Problem 2 - Profile settings are not cleaned up:
If a second or third profile is added with the new client and one of the profiles is deleted, the entry in Explorer remains even after a reboot. This is very annoying and should also be deleted accordingly from the Explorer (registry) when removing a profile from SeaDrive Client 3.0.2.

Problem 3 - Display in Explorer:
With the possibility that multiple profiles can now be used simultaneously with the new client is a very good progress. But it should be possible that the display name in Explorer can be customized with the own settings (on the server in the Seafile-Config). As soon as a user logs in with his profile, the SeaDrive client should read the display settings (the name) from the server and then enter it in Explorer together with the name.

Currently: SeaDrive (
Requested: Custom Cloudname (username or display name)

In SeaFile the display works at least in the application (with the Professional Edition). I wish that the cloud name is now also displayed in the explorer context as described above. The same applies to the menu when right clicking on a file.

Instead of SeaDrive → Create download link etc. then just “Custom Cloudname” → Create download link etc.

We have a multi-tenancy environment and in some cases people in board positions responsible for different companies. These companies are hosted with us in the multi-tenancy environment and therefore it is very confusing for people who have multiple accounts where the data is now.

In addition, you should really work with your own name in the Explorer context and not with SeaDrive.

kind regards

We’ll look into this problem.

In 3.0.3 the entry in Explorer will be removed when the account is removed. Actually the behavior is the same for 2.0.x. In 2.0.x you can also log into multiple account. But you just cannot sync them at the same time.

We don’t plan to support customization for the Cloud name. About displaying user name in the Explorer entry point, we think displaying the server domain name is better. Most users who log into multiple accounts because they have more than one servers to work with, instead of more than one accounts on the same server. We want to keep “SeaDrive” to make the entry point easier to identify. OneDrive also displays “OneDrive” in the Explorer entry point. Using the naming scheme “SeaDrive (cloud domain name - username)” is too long for the entry point.


Thank you for the information. Regarding the third point, from my point of view a solution like OneDrive and SeaFile is not comparable.

OneDrive is a Microsoft solution that keeps a common name across all tenants in their product universe. This product is run (hosted) by Microsoft and nothing else. Seafile and the individual solutions such as SeaDrive etc. are independent instantiations on self-operated environments. The web interface can be customized not only in terms of design, but also in terms of name.

I understand the thought process regarding the length. But this only occurs if SeaDrive is to remain in it, which I see no reason for, at least not for the Professional environment. With Community I am absolutely with you that here a certain branding for your product should be present. But not for a Professional solution. Also the argument that users have an account with different providers may well be, but does not speak against the use of its own naming quite the opposite.

I am still of the opinion that in the professional environment there must also be the possibility to adjust exactly such parameters.

The problem is increasingly that the competition comes along with their own products and their own branding and we as a provider of Seafile are left behind here because we cannot make our own identity of the product in our portfolio. If we do this, it becomes contradictory, confusing and increasingly uncompetitive at the latest with the use of the client solution.

I think the point should be to make the Seafile universe adaptable in today’s rapidly growing cloud-native environment. Otherwise, at some point we will definitely lose our customers to competing products that are pushing the solutions onto the market with enormous energy. I’m afraid that if we continue like this, our business model will change and at some point we will have to provide a Nextcloud solution to every customer instead of pushing our own solution, which would be a shame for us and for you.

Thanks and greetings


1 Like

Hello! Thank you for the Mac Seadrive client.

I am using the SeaDrive client 3.0.2 on my 13 inch 2020 M1 MacBook Pro. The SeaDrive client process sometime closing with the following error:

[05/23/23 19:44:07] pipe client failed to connect to server: Connection refused
[05/23/23 19:44:15] pipe client failed to connect to server: Connection refused
[05/23/23 19:44:17] pipe client failed to connect to server: Bad file descriptor
[05/23/23 19:45:37] pipe client failed to connect to server: Bad file descriptor
[05/23/23 19:45:38] QEventDispatcherUNIXPrivate(): Cannot continue without a thread pipe

Tell me, please, what could be the problem? If you need additional information, I am ready to send them.

Can you post which version of macOS you are running? Also, what version of macFUSE do you have installed? Is this Seafile CE or Pro; version 9 or 10? Server platform/OS? -Thanks

macOS 13.3.1 (a)
macFUSE not installed
seafile-server 9.0.2 CE
Ubuntu 20.04.3 LTS

Hello, have you clicked on the seadrive entry on the left column? Is there a seadrive extension running in a background process?

I just tried SeaDrive 3.0.2 on Monterey and had no luck until I clicked its icon under Locations in the Finder window sidebar.

I also noticed that there’s no Desktop icon like before. I suppose that’s related to the new Apple API. As a workaround I made an alias (folder) of ~/LibraryCloudStorage/SeaDrive and placed that on the Desktop.

If I understand correctly macFUSE is bundled with SeaDrive 3.X and is no longer required for Seafile.