I am running Seafile and OnlyOffice Document Server in Docker. Both have different ip addresses in the same subnet.
As web server nginx is used. Nginx is running as a reverse proxy for Seafile (SSL) and different other services.
nginx is running in a seperate container.
Seafile and OnlyOffice Document Server are running fine.
I followed the instructions in manual for the integration Seafile and OnlyOffice Document Server.
I tried first via Subdomain but the result was alyways a blank page opening a document.
Also, even if you do not speak German take a look at this video. I found it very useful even though I was still not able to successfully integrate OnlyOffice with Seafile using the Subfolder method.
The docker container for the Only Office Document Server is running on port 80. I have an nginx server as a central reverse proxy server running for several services.
The manual recommends port 88 just for the reason that the nginx reverse proxy is running in the same container/vm as the Seafile Server.
Seafile Server, Only Office and nginx are running in its own docker container. All are in the same LAN and “lan_ip_address” stands for the IP address of the OnlyOffice LAN IP address.
Does anybody see a general error in the configuration? It is only altered regarding the port of the Only Office Dcument Server. I tried with port 88. But I got the same result.
Please try all connection scenarios with nmap and check routes to see if routing works properly.
I guess you are running your containers in a dedicated network, otherwise it’s a serious security flaw.
Sorry, I don’t follow. Can you clarify this for me?
Are you saying that Nginx, Seafile and OnlyOffice are running in their own container? I was imagining a plain vanilla setup where Nginx/Seafile were collocated with a Docker container running OnlyOffice DS. Is that what you’re running?
On the other hand, are you running the OODS Docker container on another host on the network?
nginx, seafile and only office are running in their own containers. nginx is not included in the plain vanilla docker seafile.
All docker containers are in the same network on the same host.
Have you tried using the Developer Tools (Web Console; Javascript Console) in your web browser(s) to detect the error in the link? In diagnosing blank pages from the Seafile-OODS integration I found many instances of https CallBack errors and other resultant 404 pages. It might be useful in your case to pin point where the error is originating.
Here is a little background on the Callback and the transactions between OODS and server from the OwnCloud/NextCloud perspective. It seems the OwnCloud folks have the same problems integrating OODS as the Seafile folks.