Cannot open Seadoc document, nor crate a wiki page

SeaDoc
,
22

This is not possible. The browser does not allow to mix content of http and https.

23

The fix will be included in the next release 13.0.12.

24

I made a mistake while entering the DNS record, which I corrected. After that, I waited a while until all DNS servers returned the correct IP address. I also obtained and installed an LE certificate.

Unfortunately, I still can’t open a SeaDoc document. I receive the following error in my web browser:
message: “Request failed with status code 500”, name: “AxiosError”, code: “ERR_BAD_RESPONSE”

The following entry is found in the sdos-server.log file:
[ERROR] document-controller.js[56] - Get doc download link error

I tried the following configurations in the Apache configuration, as specified here:

<Location /sdoc-server/>
    ProxyPass "http://127.0.0.1:80/"
    ProxyPassReverse "http://127.0.0.1:80/"
</Location>

<Location /socket.io/>
    # Since Apache HTTP Server 2.4.47
    ProxyPass "http://127.0.0.1:80/socket.io/" upgrade=websocket
</Location>

I’m surprised that ProxyPassReverse isn’t specified for socket.io.

The address https://my.domain.tld/sdoc-server/ is still accessible without any problems. This test seems to be pointless.

25

This means sdoc-server cannot connect to seafile instance.

You should check that sdoc-server can connect to seafile instance by the seafile’s public URL. For example, you may need to add seafile’s domain to HOST file to correctly resolute the DNS. Or you should make sure the HTTPS CA is valid for the sdoc-server.

26

For me it seams to be a problem with access to media:

Object { message: “Request failed with status code 500”, name: “AxiosError”, code: “ERR_BAD_RESPONSE”, config: {…}, request: XMLHttpRequest, response: {…}, status: 500, stack: “”, … }
​code: “ERR_BAD_RESPONSE”
​config: Object { timeout: 0, xsrfCookieName: “XSRF-TOKEN”, xsrfHeaderName: “X-XSRF-TOKEN”, … }
​message: “Request failed with status code 500”
​name: “AxiosError”
​request: XMLHttpRequest { readyState: 4, timeout: 0, withCredentials: false, … }
​response: Object { data: {…}, status: 500, statusText: “”, … }
​stack: “Te@https://seafile12-test.domain.tld/media/assets/frontend/static/js/viewFileSdoc.db4ce4b9.js:2:4353767\nv@https://seafile12-test.domain.tld/media/assets/frontend/static/js/viewFileSdoc.db4ce4b9.js:2:4358075\n”
​status: 500

27

In an installation where Seafile and SeaDoc are behind a firewall, there’s a problem with the internal and external IP addresses. I have to specify the web server’s private IP address in the /etc/hosts file in the SeaDoc container; otherwise, SeaDoc tries to use the public address, and the firewall seems to be blocking something, although I can’t see what.

How can I permanently modify the /etc/hosts file in the SeaDoc container?

28

After modifying the /etc/hosts/, you can save the docker image using docker command.

29

Hello. I have problem when import Wiki with 404 error:

/api/v2.1/query-io-status/?task_id=dee70268-cec0-45e2-be6d-7033ce37174b&task_type=import

GET 404 Not Found

==> /opt/seafile-data/seafile/logs/seafevents.log <==
[2025-12-04 01:01:01] [INFO] root:87 Run task: 8bc434cd-dec8-4093-a61c-ac5c9010911d <function import_wiki_page at 0x7510ee0874c0>

==> /opt/seafile-data/seafile/logs/seahub.log <==
[2025-12-04 01:01:01] [WARNING] django.request:253 log_response Not Found: /api/v2.1/query-io-status/

==> /opt/seafile-data/seafile/logs/seafevents.log <==
[2025-12-04 01:01:02] [INFO] root:94 Run task success: 8bc434cd-dec8-4093-a61c-ac5c9010911d <function import_wiki_page at 0x7510ee0874c0> cost 0s