Sync-in with collabora/openoffice behind different Reverse Proxy

[KarelWintersky]

I want to run Sync-In + Collaboration Office on a VM on my home server behind a reverse proxy (running in the VM).

If I install SyncIn via NPM, there are no problems running it through a reverse proxy on another VM. However, neither Collaboration nor OpenOffice are available. I couldn't find any documentation on how to install or connect them.

If I install it via Docker, there's no difficulty in installing Collaboration or OpenOffice alongside Sync-In in Docker containers, but installing them requires a container with a reverse proxy.

And here's where the problem arises.

When accessing via internal IP (http://192.168.111.91/), OnlyOffice opens files normally, but Collaborator opens once and then reports "no space left on the server" (this is nonsense, there's at least a gigabyte of free space, even though the containers have already consumed 15 GB and are only growing) or a "configuration error."

This happens in response to the request:

ws://192.168.111.91/cool/http%3A%2F%2F192.168.111.91%2Fwopi%2Ffiles%2F37effe55ed81f7b2d43906c517fe4a8026a07c2c5be3fb924cdb35f949d190ad%3Faccess_token%3DeyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZGVudGl0eSI6eyJpZCI6MSwibG9naW4iOiJhcnJpcyIsImVtYWlsIjoiYXJyaXNAc3luYy1pbi5jb20iLCJmdWxsTmFtZSI6IkthcmVsIFdpbnRlcnNreSIsImxhbmd1YWdlIjoiZW4iLCJyb2xlIjowLCJhcHBsaWNhdGlvbnMiOltdLCJzcGFjZVVybCI6ImZpbGVzL3BlcnNvbmFsL9Ct0LvRjNGE0LjQudGB0LrQuNC1INCU0L7QvNCwINCyINCa0L7QvdGE0LXQtNC10YDQsNGG0LjQuC5kb2MiLCJkYkZpbGVIYXNoIjoiMzdlZmZlNTVlZDgxZjdiMmQ0MzkwNmM1MTdmZTRhODAyNmEwN2MyYzViZTNmYjkyNGNkYjM1Zjk0OWQxOTBhZCJ9LCJpYXQiOjE3NzcyMjgyMTcsImV4cCI6MTc3NzI0MjYxN30.zgOxR5U5qrgoZ9_4ZDwaiNlOLKiQAntdeHozvt4q9YE%26access_token_ttl%3D0%26permission%3Dedit/ws?WOPISrc=http%3A%2F%2F192.168.111.91%2Fwopi%2Ffiles%2F37effe55ed81f7b2d43906c517fe4a8026a07c2c5be3fb924cdb35f949d190ad&compat=%2Fws

I tried forwarding the container to a public address. Sync-In displays correctly (in both cases), but neither Collaborator nor OpenOffice launch. Collaborator simply doesn't display ANY messages, and OnlyOffice says:

The document server may be unreachable or the configuration is invalid 

I can't run the entire Sync-In ecosystem directly on a virtual machine facing the internet and with a public address for a number of technical reasons (the network architecture, etc.).

Internet <==> VM with nginx (proxypass to LAN) <==> VM with Sync-In (.91)  

I'm asking for help - both with advice on "how to run Collaboration or OnlyOffice when installing via NPM" and "how to integrate a container with a reverse proxy with a real reverse proxy."

[KarelWintersky]

My docker-compose.collabora.yaml:

services:
  collabora:
    image: collabora/code
    container_name: collabora
    restart: always
    ports:
      - "192.168.111.91:9980:9980"
    environment:
      extra_params: >-
        --o:ssl.enable=false
        --o:ssl.termination=false
        --o:logging.disable_server_audit=true
        --o:admin_console.enable=false
    cap_drop:
      - ALL
    cap_add:
      - SYS_CHROOT
      - SYS_ADMIN
      - FOWNER
      - CHOWN
    logging:
      driver: json-file
      options:
        max-size: "25m"
        max-file: "5"
    networks:
      - sync_in_network

I exposed port, without it collabora in LAN shows nothing. Anyway, without exposed ports, Collabora reported: "no disk space left on server". And, strangely enough, the server space is indeed constantly shrinking, and quite rapidly—by a megabyte per second. Is someone actively writing thousands of log lines?

[KarelWintersky]

My docker-compose.onlyoffice.yaml:

services:
  onlyoffice:
    image: onlyoffice/documentserver:9.3
    container_name: onlyoffice
    restart: always
    environment:
      - JWT_SECRET=onlyOfficeSecret
      - JWT_IN_BODY=true
      - USE_UNAUTHORIZED_STORAGE=true
    logging:
      driver: json-file
      options:
        max-size: "25m"
        max-file: "5"
    networks:
      - sync_in_network

his nginx section:

location ^~ /onlyoffice/ {
    proxy_pass http://onlyoffice:80/;
    proxy_set_header X-Real-IP  $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header X-Forwarded-Host $host/onlyoffice;
    proxy_set_header X-Forwarded-Proto $scheme;
    proxy_set_header Host $host;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection $connection_upgrade;
    proxy_no_cache 1;
    proxy_cache_bypass 1;
}

and section on public proxy:

    location /onlyoffice/ {
        proxy_pass http://192.168.111.91:80/;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection $connection_upgrade;
        proxy_buffering off;
        proxy_read_timeout 86400s;
    }

But, on public server is recieve a message: "The document server may be unreachable or the configuration is invalid "...

Without this section on public proxy I have a same result

[KarelWintersky]

We're trying to edit a document we just uploaded using an administrative account. What's the problem, what did I do wrong? Zero answers.

Just: GET ws://192.168.111.91/onlyoffice/9.3.1-3ff3a5b39972c980b1ebdd838b1514a5/doc/2200-19dced66fe7/c/?shardkey=2200-19dced66fe7&EIO=4&transport=websocket

reports:

Any ideas? ZERO...