2025/05/12 21:17:55 [error] 12469#12469: *16 open() "/var/www/onlyoffice/documentserver/web-apps/apps/api/documents/api.js'" failed (2: No such file or directory), client: 172.19.0.1, server: , request: "GET /web-apps/apps/api/documents/api.js' HTTP/1.1", host

Just adding.. I read about copying certs from my swag container and renaming them and putting them into the onlyoffice/data/certs folder.. started working in seafile.  apparently I missed that step?

 

16 hours ago, presence06 said:

Just adding.. I read about copying certs from my swag container and renaming them and putting them into the onlyoffice/data/certs folder.. started working in seafile.  apparently I missed that step?

 

That should not have been necessary. There should have been nothing changed from the default onlyoffice document server docker. I would suggest deleting onlyoffice, the appdata for it, and the container template and starting over.

The JWT secret key is the only thing you need to customize.

 

post your swag proxy config for onlyoffice. The only thing you needed to do to get it working with seafile was adding those handful of lines to the seahub_setings.py file.

 

these:

 

ENABLE_ONLYOFFICE = True
VERIFY_ONLYOFFICE_CERTIFICATE = False
ONLYOFFICE_APIJS_URL = 'https://onlyoffice.example.com/web-apps/apps/api/documents/api.js'
ONLYOFFICE_FILE_EXTENSION = ('doc', 'docx', 'ppt', 'pptx', 'xls', 'xlsx', 'odt', 'fodt', 'odp', 'fodp', 'ods', 'fods')
ONLYOFFICE_EDIT_FILE_EXTENSION = ('docx', 'pptx', 'xlsx')
ONLYOFFICE_FORCE_SAVE = True
ONLYOFFICE_JWT_SECRET = 'your-onlyoffice-jwt-key-here'

 

From this the only two lines you need to modify are the APIJS_URL and JWT_SECRET

Edited May 14, 20251 yr by MowMdown

2 hours ago, MowMdown said:

That should not have been necessary. There should have been nothing changed from the default onlyoffice document server docker. I would suggest deleting onlyoffice, the appdata for it, and the container template and starting over.

The JWT secret key is the only thing you need to customize.

 

post your swag proxy config for onlyoffice. The only thing you needed to do to get it working with seafile was adding those handful of lines to the seahub_setings.py file.

 

these:

 

ENABLE_ONLYOFFICE = True
VERIFY_ONLYOFFICE_CERTIFICATE = False
ONLYOFFICE_APIJS_URL = 'https://onlyoffice.example.com/web-apps/apps/api/documents/api.js'
ONLYOFFICE_FILE_EXTENSION = ('doc', 'docx', 'ppt', 'pptx', 'xls', 'xlsx', 'odt', 'fodt', 'odp', 'fodp', 'ods', 'fods')
ONLYOFFICE_EDIT_FILE_EXTENSION = ('docx', 'pptx', 'xlsx')
ONLYOFFICE_FORCE_SAVE = True
ONLYOFFICE_JWT_SECRET = 'your-onlyoffice-jwt-key-here'

 

From this the only two lines you need to modify are the APIJS_URL and JWT_SECRET

I uninstalled the docker, removed the appdata folder. 

reinstalled documentserver, added the JWT that's in my seahub_settings.py. 

restarted Seafile and now I have OnlyOffice working. 

Thank you,

Great you managed to make it run, @presence06!

Hello, I'm trying to get Seafile 12 running after I found my old container no longer maintained. I'm not seeing anyone else run into the issue I am now. It looks like Seafile has a user/pass defined but it's incorrect. Where is this variable defined so I can reset the password?

verifying password of user root ... done

verifying password of user seafile ...

Failed to connect to mysql server using user "seafile" and password "***": Access denied for user 'seafile'@'172.18.0.3' (using password: YES)

Hi @Gryman !

As you wrote: "Failed to connect to mysql server using user 'seafile' and password '***': Access denied..."

Please follow the instructions from dglb99. That should make it quite easy.

Otherwise, I can only guess. You're not exactly generous with information. That makes it almost impossible to help you.

Good luck!

Tom

Hi @Gryman !

Were you able to solve your issue?

And for anyone else who might be interested: I finally managed to get Seafile’s FUSE mount working on Unraid. The official documentation here – https://manual.seafile.com/latest/extension/fuse/ – is a good starting point, but if you’re not a Docker expert and still fairly new to Unraid (like me – using it for less than 3 months), you can run out of ideas quickly.

Here’s how I did it:

I edited the existing seafile-12 container and added an additional path. I first created a share /mnt/user/sync on Unraid, but then I switched to using the absolute disk path /mnt/disk1/sync as the host path, which I mapped to /seafile-fuse in the container. I don't know if I could have also used the /mnt/user/sync. Somewhere I read that it would be better to use the "real" location. Would be great if someone could confirm this.

• Important: you need to select “read-only shared” for this path, because the default is private, which prevents the mount from propagating to the host.

• The container also needs to run in privileged mode.

• Additionally, you need to set the following in the extra parameters: --cap-add=SYS_ADMIN. You need to switch from simple to extended view first on the upper right.

After restarting the container, I entered it using docker exec -it <SEAFILE_CONTAINER_NAME> bash. Then I navigated to cd /opt/seafile/seafile-server-latest and started the FUSE mount with ./seaf-fuse.sh start /seafile-fuse. To verify that the mount is actually shared, you can run findmnt -o TARGET,PROPAGATION | grep /seafile-fuse .

If everything is working correctly, you should now see several directories under /mnt/user/sync on the host. One of them will include the user’s email address. Inside that folder you’ll find the individual libraries, which have hash-based directory names. But once you go one level deeper, you’ll see the familiar folder structure and file names in plaintext.

This was important to me because I want to include the FUSE-mounted folder in my restic and rsync-based backup strategy (to QNAP and pCloud).

In addition, I’ll also be backing up the Seafile databases and blob data separately to ensure a full and restorable backup – just in case.

Hope this helps someone!

Best regards,
Tom

@tomkenobi How is your experience with Seafile so far? Did you stick with the pro or community version? How do you backup Seafile?

Stephan

On 5/10/2025 at 8:54 PM, tomkenobi said:

Quick update: I somehow managed to get Seasearch up and running. I took a detailed look at the seasearch.yml file and manually added all the variables that seemed necessary into a completely new Docker template on Unraid.

 

 

 

I have no idea which of the variables might be redundant. Maybe someone with a more trained eye could take a look and comment.

 

Here are the entries I added to seafevents.conf:

 

 

I wasn't entirely sure about the value for seasearch_url, so I just tried it this way.

 

The first sign of success was that, unlike my previous attempts with Elasticsearch, the local folder actually started filling up with data. After about 10-15 minutes, I was able to see relevant search results in Seafile. However, it doesn’t seem like the contents of the files themselves are being indexed yet. I'll keep an eye on that.

 

But for now, I consider this a success, even though it took me more than half a day to get it working.

 

Best regards,
Tom

Where do you get the information for seasearch_token?

Hi @stephan182730 !

Since my last migration, I’ve been using the Pro version because I wanted to take advantage of some features not available in the Community Edition – mainly fine-grained folder permissions and role-based account management.

Regarding backups, I’m still in the process of separating the files I always want available via Seafile from those I prefer to keep in an archive or a dedicated file storage directory on the server. On the server, I currently have two main locations: /sync – which contains the files and folder structures I work with on a daily basis – and /archive, which contains files that are mostly stored for reference and no longer actively edited. The latter also includes larger libraries such as my music and audiobooks, which are managed locally via Audiobookshelf and Navidrome.

I’m now close to the point where I can include both areas in my backup strategy. For /sync, my plan is to use Seafile FUSE to access the “Sync” data in plaintext, then back it up daily in two ways:

1. Via rclone + restic to an off-site cloud location.

2. In parallel, via rsync to a local QNAP NAS.

As for the databases, I will follow the official instructions at: Seafile Backup & Recovery Guide – that will be my next step. I haven’t implemented this yet, since most of my “Sync” data is not fully inside Seafile at this point, but the final migration is planned for later this week.

Regarding the seasearch_token, I had to retrace my steps to confirm how it works. It is generated from a combination of your username and password. You can find instructions here: SeaSearch Authentication Guide.

I hope this helps – good luck!

Cheers,

Tom