Goal: Homeserver Debian 9 with Docker NC15 + LOOL HTTPS behind Apache Reverse Proxy
Symptom: Can not create or edit LOOL Documents in NC Instance everything else works like a charme
Docker Image Nextcloud 15.0.5 stable
Docker Image LibreOffice Online 6.3 (Docker Tag: master)
LetsEncrypt Cert for FQDN okay
LetsEncrypt Cert as Sub Domain for NC Instance okay
LetsEncrypt Cert as Sub Domain for LOOL Instance okay
For debugging *** complete disabling of HTTPS *** for LOOL Docker Instance (ssl.enable=false and ssl.termination=false as Docker ENV; ssl set to disable in loolwxsd.xml with separate Volume for /etc to preserve override)
My APACHE Conf looks this:
…
SetEnfIf Host “^(.*)$” THE_HOST=$1
RequestHeader setifempty X-Forwarded-Proto http
RequestHeader setifempty X-Forwarded Host %{The_HOST}e
ProxyAddHeaders off
AllowEncodedSlashes NoDecode
ProxyPreserveHost On
ProxyPassMatch (.*)(/websocket)$ “ws://127.0.0.1:9980/$1$2”
ProxyPass / “http://127.0.0.1:9980/”
ProxyPassReverse / “http://127.0.0.1:9980”
…
No errors appears in the apache Debug Logfile.
LOOL Instance Basics are working -IMHO-, because …
http:///hosting/discovery
–> show wopi-dicovery XML
http:///loleaflet/dist/loleaflet.html
–> show message box “wrong or missing WOPISrc parameters” but this is okay because the NC document URL is missing.
Enabling Browser Developer Options (Firefox 65.0.1) shows me:
(Ressource Load failed caused of blocking “frame-src”)
Content Security Policy: Die Einstellungen der Seite haben das Laden einer Ressource auf http://127.0.0.1:9980/loleaflet/8a61a5302/loleaflet.html?WOPISrc=https%3A%2F%2F%2Fapps%2Frichdocuments%2Fwopi%2Ffiles%2F166_ocriym9yrysd&title=Neues%20Dokument.odt&lang=de&closebutton=1&revisionhistory=1 blockiert (“frame-src”).
I am looking around at the filesystem of my LOOL Instance and found empty sub-dirs under the /tmp path and the “child-roots” under /opt/lool/ are successfull created. It seems to me i have to take additional settings in my APACHE Conf. I found a similar mistake in the forum and a possible solution with nginx but - shame over me - i am not able to translate this in a successfull apache syntax.
Or is there another mistake? Thanks a lot in advance!