SeaDoc incompatible with go fileserver

m4v commented 2 months ago

I was giving it a try to SeaDoc and I was getting errors in my selfhosted instance:

sdoc-server.log

[2024-07-13 14:07:52] [ERROR] document-manager.js[331] - test3.sdoc(2e501cc3-cb78-4188-ab0b-8c57a82aff62) save failed
[2024-07-13 14:07:52] [ERROR] document-manager.js[332] - {"status":400,"error_msg":"{\"error\": \"No target_file given.\n\"}\n"}
[2024-07-13 14:07:52] [INFO] index.js[58] - test3.sdoc(2e501cc3-cb78-4188-ab0b-8c57a82aff62) unlocked success

seahub.log

2024-07-13 14:07:52,032 [ERROR] seahub.seadoc.apis:175 post save sdoc failed 2e501cc3-cb78-4188-ab0b-8c57a82aff62, {"error": "No target_file given."}
2024-07-13 14:07:52,032 [WARNING] django.request:241 log_response Bad Request: /api/v2.1/seadoc/upload-file/2e501cc3-cb78-4188-ab0b-8c57a82aff62/

After trying a lot of things I found out it was because I was using use_go_fileserver = true in my seafile.conf, setting it to false resolved the problem.

Seafile version: 11.0.8 SeaDoc version: 0.7 SeaDoc and Seafile are deployed with docker on the same host

freeplant commented 2 months ago

We will check the problem.

killing commented 1 week ago

This is fixed in latest version 11.

haiwen / seafile

SeaDoc incompatible with go fileserver #2796