external openoffice server without nginx

[lephtHanded]

Hey,
So I'm trying to figure out how to use a different openoffice container with sync_in without using the nginx proxy container.

according to the documentation, I should be able to use an external server, but I can't quite get it working.
here is my compose file along with the environment.yaml:

services:
  sync_in:
    image: syncin/server:latest
    container_name: sync-in-app
    restart: always
    #environment:
    #  - INIT_ADMIN=true
    #  - INIT_ADMIN_PASSWORD
    #  - INIT_ADMIN_LOGIN
    #  - PUID=${PUID:-8888}
    #  - PGID=${PGID:-8888}
    ports:
      - "7075:8080"
    volumes:
      - ${DKRpath}/sinkin/environment.yaml:/app/environment/environment.yaml
      - /mnt/storage/cloudSync/sinkin:/app/data
      - desktop_releases:/app/static/releases:ro
    depends_on:
      - mariadb
    logging:
      driver: json-file
      options:
        max-size: "25m"
        max-file: "5"
    networks:
      - sync_in

  mariadb:
    image: mariadb:11
    container_name: sync-in-db
    restart: always
    command: --innodb_ft_cache_size=16000000 --max-allowed-packet=1G
    environment:
      MYSQL_ROOT_PASSWORD: reallyLongString#3
      MYSQL_DATABASE: sync_in
    volumes:
      - ${DKRpath}/sinkin/deebee:/var/lib/mysql
    networks:
      - sync_in

  onlyoffice:
    image: onlyoffice/documentserver:9.0
    container_name: sink-in-office2508
    restart: always
    volumes:
      - ${DKRpath}/onlyoffice/data:/var/www/onlyoffice/Data
      - ${DKRpath}/onlyoffice/log:/var/log/onlyoffice
    ports:
      - 17075:80
    environment:
      - JWT_SECRET=reallyLongString#4
      - JWT_IN_BODY=true
      - USE_UNAUTHORIZED_STORAGE=true
    logging:
      driver: json-file
      options:
        max-size: "25m"
        max-file: "5"
    networks:
      - sync_in
      
networks:
  sync_in:
    driver: bridge

volumes:
  desktop_releases:



####ENV-YAMLFILE
server:
  # prevent displaying Docker internal IP addresses
  trustProxy: true
mysql:
  url: mysql://root:reallyLongString#3@mariadb:3306/sync_in
auth:
  token:
    access:
      secret: reallyLongString#1
    refresh:
      secret: reallyLongString#2
applications:
  files:
    dataPath: /app/data
    onlyoffice:
      enabled: true
      secret: reallyLongString#4
      verifySSL: true
      externalServer: https://docs.domain.com

Attached are the logs from when I try it out.

Edit: I'm pointing docs.domain.com to the openoffice container through pangolin

sync-in-app-2025-08-21T01-32-57.log

[johaven]

Have you checked that https://docs.domain.com can connect to your Sync-in container ?

[lephtHanded]

Not sure why the docs server would be connecting to the sync server.
i could be totally wrong, but i thought the sync server connected to the doc server through an API call.

• again, I could be totally wrong.

but the point is moot because I got it working, though there are still a lot of warning in the docker logs:

how I got it working:
i did some surfing and found this little nugget on dreadit.

basically, adding the entrypoint section following to my docker compose:

    ports:
      - 17075:80
    environment:
      - JWT_SECRET=reallyLongSooperSecretAlphabetSoup
      - JWT_IN_BODY=true
      - USE_UNAUTHORIZED_STORAGE=true
    entrypoint:
     - "sh"
     - "-c"
     - |
       echo 'change nginx conf to req https..'
       sed -i "s/[$]the_scheme[;]/https;/g" /etc/onlyoffice/documentserver/nginx/includes/http-common.conf
       echo 'done! starting server...'
       /app/ds/run-document-server.sh
    logging:
      driver: json-file
      options:
        max-size: "25m"
        max-file: "5"
    networks:
      - sync_ino

not sure if you want me to mark this resolved and open a new issue about the errors i'm seeing above.

thanks again, you've got a great app here.

[johaven]

The warnings are related to the indexing of your documents, nothing serious. I’ll try to catch them in a future version :)
The OnlyOffice instance or server must be reachable by the Sync-in server and the web browser, and must have a valid SSL certificate (if verifySSL is set to true).