From ArchWiki
Jump to navigation Jump to search

nginx, fastcgi

By following this guide I was able to install Seafile under Arch and get the client working but I could not get file downloads and uploads to work via the web interface when using nginx - I'd just get a gateway error (502?) error.

I presume this is because I'm starting seafile without the --fastcgi option but when I use that nothing works at all. The desktop client stops working and the web interface doesn't even load for me when I enable fastcgi.

The official manual didn't offer much else in the way of help and the IRC is useless so I'm going to try Apache instead.

—This unsigned comment is by Danboid (talk) 23 March 2015‎. Please sign your posts with ~~~~!

Understanding the tutorial

Art first: Thank you for providing a tutorial for arch linux. As an operation systems for advanced users it is not as a matter of course.

Following the tutorial I wondered several times understanding the steps in the right way. The following ones would be my questions:


$ mkdir -p $HOME/

Note: Replace every occurence of '' on this page with the actual domain of your new server instance

1.1 Do I have to set up the file structure with as folder under $HOME to get seafile working? And if so: Why? Is it to provide the possibility for several parallel seafile installations so can I just use $HOME if I only want to set up one seafile server?

1.2 Is '' a placeholder for my DynDNS/registered website name? For the case: If my DynDNS address would be '' do I have to name the folder just ''?

2) Those initial setup steps can be done with the `seafile-admin` command

2.1 It sounds a little bit optional. Maybe it would be better to write something like: for initial setup steps execute `seafile-admin setup` command I was confused if I have to execute this command now or not.

2.2 seafile-admin doesn't say something about consequences for choosing the server host address. The example says I can choose a DynDNS address or a local LAN IP. So I wondered: If I choose the LAN IP will Seafile be reachable via DynDNS anyway?

3) additional iptables/port forwarding information

It would be great to get some information which ports I have to allow in iptables and/or for port forwarding setup of a router. The overview for the seafile components in the official tutorial seems a little bit outdated.

Thanks alot!

Saljut7 (talk) 23:31, 28 March 2015 (UTC)

gc error Wrong ID

i got this error when i started seafserv-gc

[05/14/16 09:41:55] ccnet_client_load_confdir: Wrong ID

after some research i found that there is another Parameter that can be set: -F -F stands for the standard conf directory So my command looks now like:

seafserv-gc -c /srv/seafile/ -d /srv/seafile/ -F /srv/seafile/

and it worked for me MadMe (talk) 08:05, 14 May 2016 (UTC)

Seafile split

Be advised that there has been some kind of split between the European and Chinese Seafile devs: 21 July 16 Press Release

From the release:


Over the last years working with Seafile Ltd. has proven more and more difficult. Our cooperation now has reached a point where we can no longer in good conscience develop a software together.

Our goal at Seafile GmbH is and has always been to provide a stable and reliable product for our customers and the Open Source community. We have been disagreeing for a long time with

- the current development race, [note: I assume they mean 'pace' here]

- erratic changes of public plans,

- beta testing on paying customers,

- removal of features without proper prior notification or migration plans and

- disrespect towards data privacy when it comes to German or European law.


Current pro version offered by the is 5.1.8, whereas is 5.1.10.

Spangry (talk) 16:40, 28 July 2016 (UTC)