Seafile server 6.3 is ready for testing! A WYSIWYG Markdown editor and more

Switch to mariadb-server? As I can see, Debian 8 offers version 10.0.32-0+deb8u1. I don’t know, if this will be sufficiant.

I’m using version 10.1.33 (on CentOS 7). You can get 10.1 (and even newer) for Debian 8 from MariaDB Repositories:


Just upgraded to 6.3.0 beta
Everything went fine. It would be great, if the /seahub-data/custom/style.css would be imported to the new css textfield in admin settings. I had to manually copy the content and enable custom css.

Remove login log after delete a user

Some questions:

  • Does login log refer to an actual web log file or the (desktop/mobile) client log, too?
  • What happens with history in shared libraries, where one user was deleted?

It should be possible to change the colors via color selectors. Adding css config via gui doesn’t really add any advantage to what we could do until now. O_o
This looks more like adding “something” to fulfill the promised “customization” options. :frowning:
Why is it so difficult to add color selectors that define the basic colours. :unamused:


+1 It would be nice if we could get this feature as soon as possible.

@all Thanks for your work on Seafile

1 Like

Thank you very much, I really appreciate the new features. Would it be possible to fix this little issue in the next point release @daniel.pan ?

It is only about showing a little notification that javascript has to be enabled if it is disabled. The current behaviour is a forever rotating circle which made me think that the Seafile instance is broken many times… :grin:


Hi @Simsala, please manually create wiki table with following SQL:

  `username` varchar(255) NOT NULL,
  `name` varchar(255) NOT NULL,
  `slug` varchar(255) NOT NULL,
  `repo_id` varchar(36) NOT NULL,
  `permission` varchar(50) NOT NULL,
  `created_at` datetime NOT NULL,
  PRIMARY KEY (`id`),
  UNIQUE KEY `slug` (`slug`),
  UNIQUE KEY `wiki_wiki_username_3c0f83e1b93de663_uniq` (`username`,`repo_id`),
  KEY `wiki_wiki_fde81f11` (`created_at`)

We will update the upgrade/sql/6.3.0/mysql/seahub.sql soon.

Could u please paste your logs/seahub.log ? There should be some error message.

Can the WSGI port be configured? Else I’m unable to run multiple instaces of Seafile on the same server. See Github #87 for details.

1 Like

You could start using docker which might be a better options anyways if you run multiple instances on one machine.
It also makes upgrading very easy.


Thank you @xiez that fixed the MySQL problem. Unfortunately Seafile 6.3 still does not start, the file gunicorn_error.log contains the following error message:

[2018-05-28 23:29:46 +0000] [24202] [INFO] Starting gunicorn 19.8.1
[2018-05-28 23:29:46 +0000] [24202] [ERROR] Connection in use: ('', 8000)
[2018-05-28 23:29:46 +0000] [24202] [ERROR] Retrying in 1 second.
[2018-05-28 23:29:47 +0000] [24202] [ERROR] Connection in use: ('', 8000)
[2018-05-28 23:29:47 +0000] [24202] [ERROR] Retrying in 1 second.
[2018-05-28 23:29:48 +0000] [24202] [ERROR] Connection in use: ('', 8000)
[2018-05-28 23:29:48 +0000] [24202] [ERROR] Retrying in 1 second.
[2018-05-28 23:29:49 +0000] [24202] [ERROR] Connection in use: ('', 8000)
[2018-05-28 23:29:49 +0000] [24202] [ERROR] Retrying in 1 second.
[2018-05-28 23:29:50 +0000] [24202] [ERROR] Connection in use: ('', 8000)
[2018-05-28 23:29:50 +0000] [24202] [ERROR] Retrying in 1 second.
[2018-05-28 23:29:51 +0000] [24202] [ERROR] Can't connect to ('', 8000)

The problem is that there is already an OnlyOffice service running on port 8000 where I haven’t figured out how to change the port yet.

So far it was sufficient to change the port in the NGINX configuration file with proxy_pass; and then start Seahub with ./ start 8002
Is this no longer possible?

Update: Okay, I figured out how to change the port for OnlyOffice. If someone else has installed OnlyOffice via repository, here are the instructions to change the port:

So far the port of wsgi cannot be changed.

Okay, that’s too bad. Back to version 6.2.5 there it works without problems, although I already changed everything in the NGINX configuration according to the WSGI configuration.

Well, this might be a clever solution but our policy currently doesn’t allow using docker, hence this is not an option. But what’s the point of having every port but 1 configurable anyway?

PS: Is there a reason why Github issues seem to be ignored by developers? I see hardly any response from developers on Github.

Support issues should go to the forum. We don’t response to support issues in Github.

I suspect that the lack of official responses creates a lot of unnecessary frustration for your users. If you don’t respond to Github issues, why not just disable issues on Github in general? Or atleast create an issue template stating that issues don’t receive responses by you and direct them to the forum?

1 Like

This might be stated on your website (or wherever you copied it from) but I can’t find anything like this mentioned on Github. For some people like me it’s a natural thing to first look at the Github issues if they exist. I guess it wouldn’t hurt to briefly inform the users who are already on Github.

Apart from that I see a huge amount of bugs on Github who seem to have never received any official response.

PS: Sorry for abusing this topic - this was not my intention.


It is from the readme of the seafile repository ( I agree that there should be more communication. I also think the policy should be implemented consequently, thus issues that aren’t bugs should be closed immediately.


Well, containers are part of the future. Push for a change of your policy then. :wink:

It would be good if one could choose an existing library for the personal wiki like it was possible in 6.2.