@pravin
I have the same issue and also a reboot doesnât help.
Did you use the redirection of all http to https during the Letâs Encript installation?
Colabora seems to be started, but it is not reachable in the Nextcloud Settings.
Also I got an Apache default Website if I try to open the FQDN of the colabora server:
Instead of the public IP, I used 127.0.0.1 for NEXTCLOUD_IPADDRESS variable. After I fixed this, rebuilding the container and rebooting the server, everything is working fine now.
When inserting the Collabora server address (office.domain.com) in the Nextcloud settings, I get following error: âCould not establish connection to the Collabora Online serverâ
Additionally I expected Collabora to show up at my âoffice.domain.comâ website but the Apache welcome-page was there instead.
Installing and enabling the built-in CODE failed as well.
Any hints on how I can solve this issue.
I double checked the config files and repeated the installation already.
@anjo.weichbrodt Please start your own thread and show your Apache and Docker configs. If youâre seeing the Apache default site, then most likely something is wrong with the Apache config.
I opened the developer console and found an error thatâs relevant:
Mixed Content: The page at 'https://cloud.domain.com/apps/files/?dir=/Documents&fileid=122' was loaded over HTTPS, but requested an insecure form action 'http://cloud.domain.com/custom_apps/richdocumentscode/proxy.php?req=/loleaflet/ed4f732/loleaflet.html?WOPISrc=https%3A%2F%2Fcloud.domain.com%2Findex.php%2Fapps%2Frichdocuments%2Fwopi%2Ffiles%2F126_ocbttb0r5cs1&title=Welcome%20to%20Nextcloud%20Hub.docx&lang=en&closebutton=1&revisionhistory=1'. This request has been blocked; the content must be served over HTTPS.
(I replaced my domain). Any ideas? Iâm using the built-in CODE server and Iâm updated to 19.0.2. This seems like a bug.
I carried out the installation exactly according to the following HowTo: Ubuntu + Docker + Nextcloud + Talk + Collabora - How to - Nextcloud community. This HowTo is using docker-compose and therefore a docker-compose.yml, which has some variables in it. I made the mistake that I have assigned the localhost IP to the variable NEXTCLOUD_IPADDRESS. Thus some port bindings was only set to the localhost ip and external access was not possible.
Hmm⌠no, not necessarily. The reason for using the LAN IP is that the loopback address doesnât work as you might expect inside a Docker container.
In a case like that, you might have to use the public IP. Youâll also need to make sure the VPS is allowed to connect to itself on that port (UFW or equivalent may block it), but not the rest of the internet.
I have to use the WAN IP in my case. I have ufw active but open ports for mail and http/https⌠it works now. Collabora wasnât working at the beginning. Thanks a lot for your gift to the community! Great work!!
I read it could have to do with âHeader always setâ options, but I havenât found any on my Apache configs. Maybe in the Nginx config inside the containers?
EDIT: Firefox gave away the problem. Certificate is untrusted. Something is not properly configured with the certificate.