Need expert checking FileBrowser Quantum with wiredoor #110
-
|
filebrowser quantum Hi, i need help regarding wiredoor, is there any settings need to configure to make onlyoffice integeration with filebrowser quantum working under reverse proxy? I have tried without using wiredoor(reverse proxy), the onlyoffice integration is working, but if i use wiredoor, onlyoffice it cant load Thanks |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 4 replies
-
|
Hi @husainihisan, I suspect this might be a CORS related issue. Wiredoor already includes the common reverse proxy headers required by OnlyOffice. I'll try deploying FileBrowser with OnlyOffice behind Wiredoor later today and will let you know what I find. |
Beta Was this translation helpful? Give feedback.
-
|
Hi! Iβve been able to reproduce the issue and get Filebrowser working with Onlyoffice behind Wiredoor. Below Iβll walk you through the exact setup I used and the steps needed to make the integration work. My environmentFor simplicity, I used the Wiredoor Gateway Docker variant, but this setup should work with any Wiredoor node type (local, k8s, etc). Setting Up Wiredoor node
Local Setup (Docker Compose)Hereβs a working example of networks:
wiredoor:
driver: bridge
ipam:
config:
- subnet: 172.18.100.0/24
services:
filebrowser:
volumes:
- './filebrowser/data:/srv'
- './filebrowser/database:/home/filebrowser/database'
- './filebrowser/config.yaml:/home/filebrowser/config.yaml'
ports:
- 80:80
image: gtstef/filebrowser
restart: unless-stopped
networks:
- wiredoor
onlyoffice:
image: onlyoffice/documentserver
environment:
JWT_SECRET: ${ONLYOFFICE_SECRET:?ONLYOFFICE environment variable is required in your .env file}
ports:
- 8080:80
networks:
- wiredoor
wiredoor-gw:
image: wiredoor/wiredoor-cli:latest
cap_add:
- NET_ADMIN
environment:
WIREDOOR_URL: ${WIREDOOR_URL:?WIREDOOR_URL environment variable is required in your .env file}
TOKEN: ${WIREDOOR_TOKEN:?WIREDOOR_TOKEN environment variable is required in your .env file}
networks:
- wiredoorCreate a ONLYOFFICE_SECRET=onlyoffice_secret
WIREDOOR_URL=https://your-wiredoor-server.com
WIREDOOR_TOKEN=YOUR_GATEWAY_NODE_TOKENFilebrowser configurationYour server:
port: 80
baseURL: "/"
logging:
- levels: "info|warning|error"
sources:
- path: "/srv"
internalUrl: "http://filebrowser"
userDefaults:
preview:
image: true
popup: true
video: false
office: false
highQuality: false
darkMode: true
disableSettings: false
singleClick: false
permissions:
admin: false
modify: false
share: false
api: false
integrations:
office:
url: "https://onlyoffice.example.com" # Domain used to expose onlyoffice
secret: onlyoffice_secret
Exposing services via wiredoorUse wiredoor to expose:
Make sure the names ( At this point, both services should be accessible independently, but the integration will still fail because of iframe restrictions. βPatch Wiredoor's Default Security HeadersBy default, Wiredoor sets To fix this: docker compose exec -u root wiredoor bash
apk add nano
nano /etc/nginx/partials/security.confFind and comment out the following line: # add_header X-Frame-Options "DENY" always;Then reload NGINX: nginx -s reloadWiredoor services: The FileBrowser editor should now successfully load the OnlyOffice iframe, and you should be able to open |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
Thank you so much @dmesad for helping me! 1 last question but slightly out of topic, |
Beta Was this translation helpful? Give feedback.
Hi! Iβve been able to reproduce the issue and get Filebrowser working with Onlyoffice behind Wiredoor. Below Iβll walk you through the exact setup I used and the steps needed to make the integration work.
My environment
For simplicity, I used the Wiredoor Gateway Docker variant, but this setup should work with any Wiredoor node type (local, k8s, etc).
Setting Up Wiredoor node
172.18.100.0/24Local Setup (Docker Compose)
Hereβs a working example of
docker-compose.yml: