Seafile -> SDOC server not working?

Apps and Virtualization
1

Hello, i installed ‘Seafile’ and enabled ‘seadoc’ during the creation of the container. however when i try to add a .sdoc file and edit it it shows : the URL : http://192.168.1.5:48080/lib/3e57d969-ac9e-40fa-993d-4158f7393047/file/test.sdoc but with the error : Load doc content error

Also when going to the ‘wikis’ and try to add one or open one it shows : AxiosError
Also tried a ‘default’ installation with just ‘http://192.168.1.5’ as base url but same result.

also shows : Load doc content error.

I already searched the Seafile community for solutions but didn’t find a solution : Cannot open Seadoc document, nor crate a wiki page - SeaDoc - Seafile Community Forum

But got no real conclusion, nor can i register because it doesn’t allow @gmail.com..

All containers are running nicely:
nginx–Running

seafile–Running

seadoc–Running

mariadb–Running

redis–Running

permissions–Exited

Can access seafile on 192.168.1.5:48080 also through my domain office.example.com (with SSL).
Opening seafile isn’t the issue, getting ‘seadoc’ to work is.
Also i think webdav isn’t working either it gives ‘502 bad gateway’.

I do have my own NGINX instance running on 192.168.1.2, could that cause problems? i can’t find anything about it.

By default the installation doesn’t work completely it seems.

2

Yeah, I’d look at the extra nginx first. SeaDoc needs the public HTTPS hostname all the way through, not the 192.168.1.5:48080 URL.

  • Set SEAFILE_SERVICE_URL to https://office.example.com, then recreate or restart the app.
  • Proxy /sdoc-server/ to seadoc and pass WebSocket upgrade headers. Do the same for /socket.io/ (proxy_http_version 1.1, Upgrade, Connection).
  • Watch the seadoc container log while opening a .sdoc. A 502 there usually means nginx is sending it to the wrong upstream or port.

The WebDAV 502 points at the outer nginx routes too. Check its access/error log during a failed open.