Closed nursoda closed 3 years ago
I found the solution myself as I re-read the SSL configuration documentation again. It would have been helpful to have an example there… So the solution is:
-e 'extra_params=--o:ssl.enable=false' -e 'extra_params=--o:ssl.termination=true"'
-e 'extra_params=--o:ssl.enable=false ssl.termination=true"'
-e 'extra_params=--o:ssl.enable=false --o:ssl.termination=true"'
In case anyone else stumbles upon this, I leave the description as it was.
Would be great having someone proof-reading this and put into README. E.g. in above example I spotted a couple of extra "
, which are probably not necessary.
I'm having this same problem and I have my environment variables set up the same as yours. I've confirmed these are being passed to the web server with ps
. But I still get the "mixed active content" error and Collabora fails to load. I might just set up TLS between code and Nextcloud just to get this working but that seems like a pain. Is there a quick way to do that?
ps aux output:
UID PID PPID C STIME TTY TIME CMD
cool 1 0 0 22:29 ? 00:00:05 /usr/bin/coolwsd --version --o:sys_template_path=/opt/cool/systemplate --o:child_root_path=/opt/cool/child-roots --o:file_server_root_path=/usr/share/coolwsd --o:logging.color=false --o:ssl.termination=true --o:ssl.enable=false
Relevant sections of docker compose file:
app:
image: nextcloud:22-apache
hostname: HOSTNAME
restart: unless-stopped
ports:
- 8082:80
volumes:
- /etc/localtime:/etc/localtime:ro
- /mnt/data/nextcloud/data:/var/www/html
environment:
- POSTGRES_HOST=db
- REDIS_HOST=redis
env_file:
- .env
depends_on:
- db
- redis
networks:
- proxy-tier
- default
- code
code:
image: collabora/code:21.11.1.4.1
restart: unless-stopped
networks:
- default
- code
env_file:
- .env
ports:
- 9980:9980
volumes:
- /etc/localtime:/etc/localtime:ro
depends_on:
- app
cap_add:
- MKNOD
environment:
- "extra_params=--o:ssl.termination=true --o:ssl.enable=false"
I came to the same conclusion, disliked the error handling of the setup the most.
Describe the bug
Due to resource URLs delivered with
http://
proto, I cannot use CODE without TLS in the backend (behind a terminating reverse-proxy).To Reproduce
Server setup
Collabora Configuration
-e 'extra_params=--o:ssl.enable=false ssl.termination=true"'
.Expected behavior
ssl.termination=true
does make sure that URLs in ressources are written ashttps://
although the server itself runs without SSL. I deduct that from the comment within/etc/loolwsd/loolwsd.xml
(from the container):Actual behavior
ps ax
I see the proper extra_params:curl http://localhost:9980
within the container and on the host, and a green check mark within my Nextcloud page /settings/admin/richdocuments – so that part works as expected.Additional context / Possible cause
http://…
-URLs that due to thessl.termination=true
parameter really should behttps://…
-URLs likehttp://MYSERVER/loleaflet/…
Complete listing of https://MYSERVER/hosting/discovery