Seafile 13.0 community edition is ready for testing!

upgraded from Seafile CE docker from 11 to 12, then 12 to 13.08 succesfully,

from 12 to 13.08, following should be noted:

  1. .env - COMPOSE_FILE list includes - seadoc.yml, but no download link provided for seadoc.yml, so when run docker compose up, you will get error, fix is easy, just remove - seadoc.yml from .env
  2. need add following line to seahub_settings.py after upgrade or you won’t able to login - ‘CSRF - error’ -
    CSRF_TRUSTED_ORIGINS = [“https://seafile.example.com”]
  3. Trash not working
  4. followed the exact steps on setting up OnlyOffice Integration, got download failed error,

Thank you for your feedback. We will improve the upgrade documentation soon. For the other two issues, we were unable to reproduce them. We recommend creating a new topic with detailed information about the problems so that we can assist you better.

sdoc-server, seafile-ai, notification-server and seafile-pro-mc all updated on 18/07/25 but I can’t see any mention on the changelog Seafile Community Edition - Seafile Admin Manual

Any info?

Is the thumbnail server solely for speeding up generation of thumbnails or will it also help with showing thumbnails in SeaDrive or will that functionality never come?

There was an error in seafile v13.0.10.

We have updated the docker image to v13.0.11. The changelog is also updated now.

Thumbnail server is for speeding up generation of thumbnails at the server side.

SeaDrive should also benefit from it.

As far as I tested, SeaDrive can show thumbnails for images, PDFs.

Hm, odd. Any pointer as to what could cause SeaDrive to not show thumbnails? I reinstalled it completely yesterday, deleting the dir with the config files etc. Thumbnails work ok in other local folders.

Do you use SeaDrive on Windows or Mac? And which version do you use?

Deploying Notification Server According to Official Guide (seafile13-ce)

On the Seafile web interface, when creating new files such as .sdoc or .xlsx, a duplicate file with the same name appears. Manually refreshing the page restores it to normal.

If either the NOTIFICATION_SERVER_URL or inner_notification_server_url line in seafile-server.yml is commented out, the issue with duplicate filenames disappears. However, similar issues still occur in the Wiki: creating a Wiki sometimes results in two with the same name, and the web page must be manually refreshed to make it normal in display.

It’s on Windows and I just installed the latest version, 3.0.16

Hi! Installed v13.0.8 and hitting a weird bug on mobile: after sharing a link to a pdf, the preview opens but the document never renders. The page loads just fine, but only the spinning wheel is visible and the document is never displayed. I assume is a rendering problem, as the pdf can be downloaded without hiccups. Tried several mobile devices without any luck.

Preview works perfect on desktop though. Tried to reproduce via devtools on desktop but without luck. Any ideas on what this could be?

edit: no matter how big or small, pdf never shows :frowning:

This isn’t unequivocally stated in the upgrade notes, but a cache server is now mandatory, right?

Yes, a cache server is now mandatory.

1 Like

Upgrade from 11 to 12 to 13 worked very well.

I do have two observations:

from 11 to 12: After migration i got every time on “docker compose up” the following error (but without any issues on seafile startup):

WARN[0000] The "fqwtwn" variable is not set. Defaulting to a blank string.

After some investigations i found out that my JWT_PRIVATE_KEY does contain “$” which declares a part of the private key as a variable in docker-env file.

After changing it in .env file from

JWT_PRIVATE_KEY=exampleprivate$key

to

JWT_PRIVATE_KEY='exampleprivate$key'

the error dissapeared and startup is working as well.

–> Maybe you can add one comment to upgrade notes or an example with single quotation marks in the .env file

from 12 to 13: I changed from MEMCACHED to REDIS as cache. After removal of CACHES part in seahub_settings.py for the old memcached config, i had some issues with HTTP 500 after seafile startup. I solved it as i removed from seahub_settings.py the following line:

COMPRESS_CACHE_BACKEND = 'locmem'

Maybe you can extend the upgrade manual to remove this optional parameter as well, if used.

One additional question: Is there a full list, which configs are obsolete now? I saw in a sidenote, that ccnet.conf can be removed after upgrade to version 12, but it was not mentioned in the upgrade notes as “config change” part and as ToDo to delete the config.

2 Likes

When is the stable version going to be available?? Or has it already been released.

In the changelog, it seems version 3.0.12 is out of beta.

The latest version is ready to be used in production. We will officially announce it at the beginning of year 2026.

We have prepared a document for listing obsolete configurations: Summary of obsolete configurations - Seafile Admin Manual