Unable to view files using onlyoffice

[colin715]

I have added onlyoffice per the instructions, have generated the JWT secret, have set up external access via NPM, and can enter in my external domain in the browser and am able to see the welcome screen. But I keep getting the "Preview not available for this file" message when I try to open an xls or ods file.

docker-compose:

services:
  filebrowser:
    image: gtstef/filebrowser
    ports:
      - 446:80
    volumes:
      - /homepool:/srv
      - ./database:/home/filebrowser/database
      - ./config.yaml:/home/filebrowser/config.yaml
    restart: always
  onlyoffice:
    image: onlyoffice/documentserver
    environment:
      JWT_SECRET: MY_SECRET
    ports:
      - 8089:80

config:

server:
  internalUrl: "http://192.168.1.25/"
  port: 80
  baseURL: "/"
  database: "/database/database.db"
  sources:
    - name: "Documents"
      path: "/srv/Documents"
integrations:
  office:
    url: "https://editor.mydomain.com"
    secret: MY_SECRET

[gtsteffaniak]

All your config is correct. I only tested text based documents like word when I added that feature. Let me double-check the config for spreadsheets and PowerPoint.

Do text based documents work for you?

[colin715]

I just checked a docx file and that's not working either.

[gtsteffaniak]

Hmm that doesn't seem right.

Just to confirm, I noticed you configured an internal url,

You are certain your onlyoffice service at "https://editor.mydomain.com" has access to the internal url "http://192.168.1.25/"? Can you out try without an internal url? The purpose of internal URL is for the integrations (like only office) to communicate on an internal channel. If your only office isn't able to see the local network it will not work.

I should probably clarify that better, but for now maybe just double check running it without internal url

[colin715]

I removed the internal URL but same results unfortunately.

And to confirm, https://editor.mydomain.com/healthcheck returns "true"

[gtsteffaniak]

Well there's two sides we could debug:

1. opening up F12 on your browser when loading should show client errors, maybe it would help understand what's going on. Do you see any console logs with errors?

2. do you have access to the logs of the onlyoffice server editor.mydomain.com? That should give a good idea if you have it

[colin715]

I was finally able to get it working. Looks like I needed to delete the containers then run docker compose up -d again. Additionally I'm only able to get it working if I'm accessing filebrowser through my external host (https://files.mydomain.com). It's not a problem at all, just not sure if that's expected behavior. Thanks so much for your help!

[gtsteffaniak]

Yeah, perhaps you weren't mounting the config in a way that allowed for changes? The examples on the configuration wiki should apply the config each time the container starts, but it would require a restart to apply the changes.

I'm glad you got it working. I know only office is pretty limited right now to just editing, but it will be more useful as time goes by.

If you notice any bugs or unusual issues at all, please open an issue on GitHub which is best for tracking bugfixes. I'm also going to leave this discussion open for a while, others might have questions that may not need their own issue and can just comment here related to onlyoffice.