-
Notifications
You must be signed in to change notification settings - Fork 812
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[bug] Office Documents Are Not Viewable #807
Comments
Can confirm. Document viewer no longer functions at all. Spun up a Debian VM and installed docker compose and used the default compose YML and i cannot get office documents to load. I didn't get a console error, but using the default docker-compose.yml I am unable to load office documents. I also attempted to spin up an AWS instance and there is no office viewer at all in that version? Seems like an oversight. |
UPDATE: It looks like the filestash demo server is now working with the the collabora document viewer. Could we get updated instructions on how to make collabora work with the docker-compose? I again tested this morning on a fresh VM and the default docker compose does not work with office docs by default. Note: I'm only accessing the service via localhost:8334 i have not set up reverse proxy on this test scenario |
Right Cool! @mickael-kerjean could you share the compose file or the config details that the demo server is using that makes the collabora office integration work as intended? |
the demo server that's available from https://www.filestash.app/word-online.html has this config:
|
Okay it looks from the demo config, the collabora server needs to be exposed as well as the main filestash app. @homegrownhrbs I have tested it and the collabora documents become accessible once you add an entry in your reverse proxy for the document server and specify the URL in the docker compose environment variables: environment:
Maybe some Documentation or Comments in the docker compose file would alleviate some of the confusion about this going forward (Especially considering this step was not necessary with the original onlyoffice backend) |
I see, Is it possible to go back to onlyoffice that did not require that? Currently i am having to import all my documents back to google drive because i cannot get document-viewing working properly :( @mickael-kerjean do you happen to have a docker-compose.yml script with an alternative document viewer enabled instead of the collabora? Sorry to be such a hassle :< I'd gladly send you a donation for your time |
There is no need to expose Filestash or Collabora. I was struggling a lot just because my docker host was not able to properly resolve my own domain... |
What about the |
This is my compose.yaml
In my LAN there is pihole running which acts as an DNS server which points the files and collabora subdomains to nginx proxy manager . This npm serves these subdomains with an wildcard certificate *.DOMAIN.XYZ as mentioned above the host running the docker containers wasn‘t using the pihole DNS server but my routers DNS… |
If anyone wants to use onlyoffice at the moment, i have made this fork that has the onlyoffice plugin installed and a working example of the docker compose file with onlyoffice. 😄
|
I have a setup with a caddy reverse proxy on an opnsense box getting lets encrypt cert and pointing to collabora and filestash. I could not get it to work with ur compose also not with edding the filestash url. It also doesnt work with the original compose. Do i need a special setting for caddy? The onlyoffice fork works perfectly though, but i would like to stay on the official docker branch. What du you guys suggest to do? |
My fork is working because I've added the onlyoffice plugin. I am actually using the fork until the main one gets fixed. I'll be trying to sync the fork each week too. I don't know what you could do, we may have to wait until mickael fixes the main version and collabora 😛 |
Are you publishing docker images or do I need to build my own with your fork? |
That was different on mine I'm using caddy internally as with a wildcard cert - and overrides in unbound within the lan. |
You can use my fork by just copying the onlyoffice docker compose file and do a: docker compose up -d --build |
I've published my fork to abeloris/filestash-onlyoffice in dockerhub, let me know if it works as intended. |
Bug Report: Unable to Access Office Docs in Fresh Install of Filestash
Description of the Bug
After a fresh installation of Filestash, attempting to open Office Docs like
.DOCX
or.CSV
files via the WebDAV integration results in a failure to load. Errors related toContent-Security-Policy
are observed in the browser console.Steps to Reproduce
curl -O https://downloads.filestash.app/latest/docker-compose.yml
docker-compose up -d
https://domain.tld/admin
) and enable only WebDAV.https://domain.tld/
..DOCX
or.CSV
file.Observed Errors
Firefox Console Error:
Content-Security-Policy: The page’s settings blocked the loading of a resource (frame-ancestors) at because it violates the following directive: “frame-ancestors http://127.0.0.1/:* http://app:*”.
Network Tab:
![Network Tab Screenshot](https://private-user-images.githubusercontent.com/140937030/404416196-58b75fd2-5bed-4ca7-a5ca-c4a1aedb7704.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mzk3OTE3MjAsIm5iZiI6MTczOTc5MTQyMCwicGF0aCI6Ii8xNDA5MzcwMzAvNDA0NDE2MTk2LTU4Yjc1ZmQyLTViZWQtNGNhNy1hNWNhLWM0YTFhZWRiNzcwNC5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjUwMjE3JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI1MDIxN1QxMTIzNDBaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT1mZTkyZGRiMzYwMmRmMmQ2YmY4NzJmYzZjMzFhOTgxYTI2MGVmMzE4MmE1NjI3Y2NhMzQ5OTllZmU4ODg2OWE3JlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.3U5TvLev_LBUXUruhxubxbWTU5ZFNfQgROMePvzrZHk)
Notes
https://demo.filestash.app
) as no office documents seem to be available to attempt opening.Expected Behavior
Office documents, such as
.DOCX
or.CSV
files, should load successfully by default when opened through Filestash.Additional Information
Current Docker Compose (Default):
version: '2'
services:
app:
container_name: filestash
image: machines/filestash:latest
restart: always
environment:
- APPLICATION_URL=
- CANARY=true
- OFFICE_URL=http://wopi_server:9980
- OFFICE_FILESTASH_URL=http://app:8334
- OFFICE_REWRITE_URL=http://127.0.0.1:9980
ports:
- "8334:8334"
volumes:
- filestash:/app/data/state/
wopi_server:
container_name: filestash_wopi
image: collabora/code:24.04.10.2.1
restart: always
environment:
- "extra_params=--o:ssl.enable=false"
- aliasgroup1="https://.*:443"
command:
- /bin/bash
- -c
- |
curl -o /usr/share/coolwsd/browser/dist/branding-desktop.css https://gist.githubusercontent.com/mickael-kerjean/bc1f57cd312cf04731d30185cc4e7ba2/raw/d706dcdf23c21441e5af289d871b33defc2770ea/destop.css
/bin/su -s /bin/bash -c '/start-collabora-online.sh' cool
user: root
ports:
- "9980:9980"
volumes:
filestash: {}
The text was updated successfully, but these errors were encountered: