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


Yes it was, on 6.0.6


I updated to version 6.3.1 today, but this bug has not been fixed.
And what about these questions?


I have upgraded to version 6.3 and seafile can´t start

seafile[19248]: Error: ‘/media/xxxxx13-dd9d-4869-b8b5-xxxxx/xxxxxx/conf/gunicorn.conf’ doesn’t exist

these file is new to me


Is it normal that v6.3.1 is much slower than 6.2.5?

import os

daemon = True
workers = 5

default localhost:8000

bind = “”


pids_dir = ‘/home/seafile/pids’
pidfile = os.path.join(pids_dir, ‘’)


logs_dir = ‘/home/seafile/logs’
errorlog = os.path.join(logs_dir, ‘gunicorn_error.log’)
accesslog = os.path.join(logs_dir, ‘gunicorn_access.log’)

for file upload, we need a longer timeout value (default is only 30s, too short)

timeout = 1200

limit_request_line = 8190

This file is also new to me, but it’s existing.



Same problem for me/
I do a minor update from 6.2.5 to 6.3.1 and get the same error.
Go back to 6.2.5…
Is there a solution?



now works!

is there any wiki about all the config options for that file?


Your problem is that there is no write permission for the folder from the user you’ve upgraded. Change it with chmod and upgrade another time.


We will keep the current behaviour that only display h2 and h3. In the future, it maybe modified.

What browser do you use, IE edge?


It would be great to include the H1 header in the content.

I’m using Google Chrome. I checked the behavior in the following browsers:
google chrome v. 67 this error is present;
opera v. 53 this error is present;
vivaldi v. 1.15 this error is present;
firefox v.60.0.2 no error;
internet explorer v.11 - the editor markdown does not start and does not work custom CSS.


All the same egine -> nearly same browser


Just saw by debugging firefox that all markdown javascript tools are always running. Is this really necessary?


Which page is much slower? Can you post a snapshot of your debugging console?


Wanted to add a (first) file comment in 6.3.1 CE, but failed in main.de99968ae34e.js with

SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the JSON data

Anyone experiencing the same issue?


Did you run ./ python-env seahub/ migrate_file_comment
according to


What has changed in the mobile interface Onlyoffice in seafile 6.3.1, I do not see any changes, looks exactly the same as on the PC.
Everything is very small, and in the doc file it’s not possible to browse the pages at all.


This is missing in the upgrade documentation


Thank you, that did the trick. Didn’t expect database changes in a minor release even the first was a beta one, so I didn’t check the changelog again. My bad. :blush:


We will check the problem.


With Seafile only maintenance do not require database upgrades. Major and minor upgrades can require them as documented at