Hi!
I’m doing a clean install seafile CE 6.2.5 and onlyoffice, its worked fine
Then, i’m upgrade seafile CE to seafile pro 6.2.12 and onlyoffice stops saving documents
in seahub_access.log:
Error: ESOCKETTIMEDOUT
at ClientRequest.<anonymous> (/var/www/onlyoffice/documentserver/server/Common/node_modules/request/request.js:813:19)
at ClientRequest.g (events.js:292:16)
at emitNone (events.js:86:13)
at ClientRequest.emit (events.js:185:7)
at TLSSocket.emitTimeout (_http_client.js:630:10)
at TLSSocket.g (events.js:292:16)
at emitNone (events.js:86:13)
at TLSSocket.emit (events.js:185:7)
at TLSSocket.Socket._onTimeout (net.js:338:8)
at ontimeout (timers.js:386:11)
in seahub.log
2018-05-07 14:58:29,971 [INFO] seahub.onlyoffice.views:70 onlyoffice_editor_callback 6919a958-0c29-4ef1-b4f5-4bdfcb0c4d89/test.docx updated by
This is caused since pro version 6.2.10 (Use inner fileserver url to save file when edit office via OOS). I’m already talking to the Seafile support to investigate the issue.
You should be able to get this running again by opening seafile-server-latest/seahub/seahub/onlyoffice/views.py, then change ‘gen_inner_file_upload_url’ back to ‘gen_file_upload_url’. See the + and - here:
diff --git a/seahub/onlyoffice/views.py b/seahub/onlyoffice/views.py
index 2ee36546f..1b1aae52a 100644
--- a/seahub/onlyoffice/views.py
+++ b/seahub/onlyoffice/views.py
@@ -11,7 +11,7 @@ from django.views.decorators.csrf import csrf_exempt
from seaserv import seafile_api
from .settings import VERIFY_ONLYOFFICE_CERTIFICATE
-from seahub.utils import gen_inner_file_upload_url
+from seahub.utils import gen_file_upload_url
# Get an instance of a logger
logger = logging.getLogger(__name__)
@@ -59,7 +59,7 @@ def onlyoffice_editor_callback(request):
if not update_token:
return HttpResponse('{"error": 0}')
- update_url = gen_inner_file_upload_url(update_token, 'update-api')
+ update_url = gen_file_upload_url(update_token, 'update-api')
files = {
'file': file_content,
After this, restart seafile and seahub. I recommend to use the original pro code.
No offence but did you ever hear about CI & CD?
Code quality testing before release?
Rather take more time before a release than to release a faulty version of code that renders your customers incapable to work.
We are talking about pro version here.
Yes, it is being used. But the tests do not cover everything …
I totally agree with this. Looking at the history, quite some versions have an immediate release following because some fault were found shortly after publishing it.