Hello,

 

was someone successful to get the newest seafile server running in docker on Unraid?

I tried it several hours now and I really have no idea what I am doing wrong...

 

The CA docker is outdated and even changing some files here and there didn't bring the success I was hoping of.

You should probably drop Seafile an email, as that version (last updated 3 years ago) is what they themselves have published on docker.

What is the problem you are facing @RedReddington ? I got the CA one running, I could update the container with some help if something is broken 

Edited January 12, 20224 yr by BoKKeR

Hi i tried to use https://hub.docker.com/r/seafileltd/seafile-mc instead of https://hub.docker.com/r/seafileltd/seafile (outdated, 3 years old).

with the seafile template delivered with the community plugin list. Installations and start works. Opening the seafile site = nginx bad gateway. The old version worked. Any advice?

I have setup seafile-mc and mariadb:10.5 (only for seafile) separate docker. I attached screenshots. I hope it helps.

 

Seafile docker;

 

 

mariadb;

 

 

summary;

 

 

 

On 4/20/2022 at 10:54 AM, Merron said:

Hi i tried to use https://hub.docker.com/r/seafileltd/seafile-mc instead of https://hub.docker.com/r/seafileltd/seafile (outdated, 3 years old).

with the seafile template delivered with the community plugin list. Installations and start works. Opening the seafile site = nginx bad gateway. The old version worked. Any advice?

I know this thread is a bit stale, but for anyone else landing here after searching for the same issue, I also initially saw "bad gateway" on a fresh install. In my case, the problem was because I didn't notice that the necessary seafile-mc environment variable is "DB_ROOT_PASSWD", not "DB_ROOT_PASSWORD". (notice the missing "OR"!)

Hey all, using the instructions provided within the template of Seafile-Official from the Unraid App store worked for me. @emrepolat7 was also very helpful!

 

Thank you, 

Hello all, since the last update (5 days ago) I can't log into my Seafile. I keep getting; (correction, I thought it was the last update, but it turns out that I had to roll back to 10.01, and update from 5 months ago)

 

Forbidden (403)

CSRF verification failed. Request aborted.

More information is available with DEBUG=True.

 

I rolled back to 10.01 and that fixed it. I guess it's been over 5 months since I've put in my passwords. 

 

Anyway, still looking for some advice to keep this up to date while still maintaining access. 

Edited November 23, 20232 yr by ppompili
Half solved

On 11/23/2023 at 9:52 PM, ppompili said:

Hello all, since the last update (5 days ago) I can't log into my Seafile. I keep getting; (correction, I thought it was the last update, but it turns out that I had to roll back to 10.01, and update from 5 months ago)

 

Forbidden (403)

CSRF verification failed. Request aborted.

More information is available with DEBUG=True.

 

I rolled back to 10.01 and that fixed it. I guess it's been over 5 months since I've put in my passwords. 

 

Anyway, still looking for some advice to keep this up to date while still maintaining access. 

 

i have the exact same problem on a new clean install with the seafileltd/seafile-mc repo. Cant fix it. Any ideas?

Hi @alexthunderstormI rolled back to 10.01. I then locked that into place, so no more updates for now. I'd rather take the risk of an outdated version rather than not being able to log in. I would roll back and then try to update at a later date. 

i had my seafile up and running in my unraid. now, how can i link all my share into this seafile instead of only one "Container Path: /shared/"

for example, for nextcloud, i can link all my other shares folder into nextcloud easily

Don't use seafile, but can you simply add in another path via the template and reference that in addition to /shared (eg: /shared2) within the app?

4 hours ago, Alvin Leong said:

i had my seafile up and running in my unraid. now, how can i link all my share into this seafile instead of only one "Container Path: /shared/"

for example, for nextcloud, i can link all my other shares folder into nextcloud easily

You can't.

 

I used seafile a few years ago and IIRC you can't mount a remote share like you do in nextcloud. Correct me if i'm wrong. Also, seafile (and nextcloud) is 'database based' so you have to upload all your files to the seafile server manually. I installed the seafile client for windows and had it run overnight to upload all my files. You can't just copy/paste files or folders into the "/shared/" seafile folder. They must be uploaded through your seafile website or client. You could do this in nextcloud but then you have to update your database manually (or script it) in the cli. I don't know if this works for seafile too.

I actually had an overall good experience with seafile, much better than with nextcloud.

I haven't been able to sync from my phone via the latest app. It keeps saying "Error when loading libraries. Tap to refresh".

And I'm exclusively on local LAN only (at least for now until I can get it to work).

The web version works just fine, no issues there.

The Linux (Fedora) app also works just fine.

I'm at a loss here.

Anyone else having this issue? Even better, anyone with a potential solution?

Thank you beforehand.

On 11/21/2022 at 11:51 AM, ppompili said:

Hey all, using the instructions provided within the template of Seafile-Official from the Unraid App store worked for me. @emrepolat7 was also very helpful!

 

Thank you, 

Which instructions? I only see some instructions in the seafile-mc template but they conflict with the technique that @emrepolat7 shows in his screenshots

 

I can't seem to figure it out. I get lost at Step 4, "a new database container that has nothing on it", what does that mean?

 

Trying to follow @emrepolat7's screenshots I get the "502 Bad Gateway" error.

Edited May 30, 20242 yr by Matt Elias

 Okay, I tried again after removing prev containers and deleting all mariadb & seafile directories from my appdata. This time I created the mariadb container first, then seafile and now it's working after following these instructions as closely as possible.

 

Now, does anyone know how to upgrade to PRO edition?

On 5/31/2024 at 2:29 AM, Matt Elias said:

Now, does anyone know how to upgrade to PRO edition?

you have to register and use their repository

On 6/1/2024 at 9:14 AM, emrepolat7 said:

you have to register and use their repository

Care to elaborate? How do I register?

On 6/22/2024 at 6:41 PM, Matt Elias said:

Care to elaborate? How do I register?

https://www.seafile.com/en/product/private_server/

I have registered with Seafile previously, but how to login with docker so that it can pull from their Pro repo? I can't find how to do that with the unRaid GUI. Is it cli only?

Edited June 26, 20242 yr by Matt Elias

Create account at https://customer.seafile.com

In unRAID terminal:

docker login docker.seadrive.org

Use your provided username and password you received earlier.  Hope this helps.

On 5/30/2024 at 7:17 AM, Matt Elias said:

Which instructions? I only see some instructions in the seafile-mc template but they conflict with the technique that @emrepolat7 shows in his screenshots

 

I can't seem to figure it out. I get lost at Step 4, "a new database container that has nothing on it", what does that mean?

 

Trying to follow @emrepolat7's screenshots I get the "502 Bad Gateway" error.

For step 4, what I was trying to say was to not create any tables, database users, etc. since Seafile has the root login it sets up the database for you.

Having different problems with SeaFile myself which I presume isn't exclusive to this Docker.

 

Background. I have two SeaFiles, one on UnRaid 1 using an older image, and another on UnRaid 2 using the latest version 11. I copied the contents of /mnt/user/SeaFile from UnRaid 1 to UnRaid 2 with success but had issues around SeaFile Origin hostnames. Went into the depths of it, edited all my conf files to point to a new hostname but still nothing. Assumed it would be related to copying older version files to the latest version so removed the docker container, renamed /mnt/user/SeaFile and started again. Now the damn thing won't start at all. So I removed it again, then used a script to purge hanging containers and volumes, then I deleted the xml template file. Same issue. I get this.

 

[2024-12-27 11:17:50] Skip running setup-seafile-mysql.py because there is existing seafile-data folder.

** (process:67): WARNING **: 11:17:50.619: seafile-controller.c(558): invalid config_dir: /opt/seafile/ccnet


** (process:67): WARNING **: 11:17:50.619: seafile-controller.c(64): seaf-controller exited with code 1

Traceback (most recent call last):
  File "/scripts/start.py", line 94, in <module>
    main()
  File "/scripts/start.py", line 79, in main
    call('{} start'.format(get_script('seafile.sh')))
  File "/scripts/utils.py", line 70, in call
    return subprocess.check_call(*a, **kw)
  File "/usr/lib/python3.10/subprocess.py", line 369, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '/opt/seafile/seafile-server-11.0.13/seafile.sh start' returned non-zero exit status 1.
2024-12-27 08:28:16 Nginx ready 
2024-12-27 08:28:16 This is an idle script (infinite loop) to keep container running. 

Starting seafile server, please wait ...
Failed to start seafile server
2024-12-27 08:44:03 Nginx ready 
2024-12-27 08:44:03 This is an idle script (infinite loop) to keep container running. 

Starting seafile server, please wait ...
Failed to start seafile server
2024-12-27 11:17:50 Nginx ready 
2024-12-27 11:17:50 This is an idle script (infinite loop) to keep container running. 

 

When I fire up a terminal window, /opt only contains a "containerid" folder, not seafile.

My /mnt/user/seafile has the expected top level folders but doesn't generate any sub directories and files.

Any ideas?

Edited December 27, 20241 yr by elmuziko

6 hours ago, elmuziko said:

Having different problems with SeaFile myself which I presume isn't exclusive to this Docker.

 

Background. I have two SeaFiles, one on UnRaid 1 using an older image, and another on UnRaid 2 using the latest version 11. I copied the contents of /mnt/user/SeaFile from UnRaid 1 to UnRaid 2 with success but had issues around SeaFile Origin hostnames. Went into the depths of it, edited all my conf files to point to a new hostname but still nothing. Assumed it would be related to copying older version files to the latest version so removed the docker container, renamed /mnt/user/SeaFile and started again. Now the damn thing won't start at all. So I removed it again, then used a script to purge hanging containers and volumes, then I deleted the xml template file. Same issue. I get this.

 

[2024-12-27 11:17:50] Skip running setup-seafile-mysql.py because there is existing seafile-data folder.

** (process:67): WARNING **: 11:17:50.619: seafile-controller.c(558): invalid config_dir: /opt/seafile/ccnet


** (process:67): WARNING **: 11:17:50.619: seafile-controller.c(64): seaf-controller exited with code 1

Traceback (most recent call last):
  File "/scripts/start.py", line 94, in <module>
    main()
  File "/scripts/start.py", line 79, in main
    call('{} start'.format(get_script('seafile.sh')))
  File "/scripts/utils.py", line 70, in call
    return subprocess.check_call(*a, **kw)
  File "/usr/lib/python3.10/subprocess.py", line 369, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '/opt/seafile/seafile-server-11.0.13/seafile.sh start' returned non-zero exit status 1.
2024-12-27 08:28:16 Nginx ready 
2024-12-27 08:28:16 This is an idle script (infinite loop) to keep container running. 

Starting seafile server, please wait ...
Failed to start seafile server
2024-12-27 08:44:03 Nginx ready 
2024-12-27 08:44:03 This is an idle script (infinite loop) to keep container running. 

Starting seafile server, please wait ...
Failed to start seafile server
2024-12-27 11:17:50 Nginx ready 
2024-12-27 11:17:50 This is an idle script (infinite loop) to keep container running. 

 

When I fire up a terminal window, /opt only contains a "containerid" folder, not seafile.

My /mnt/user/seafile has the expected top level folders but doesn't generate any sub directories and files.

Any ideas?

 

Have got it working. Because I've copied the database from unraid 1 to unraid 2, I needed to make sure the name of the docker container was correct. The default 'seafile-11' needing changing to seafile.