Collabora not accessible over vHost

To debug nextcloud set the Log Level and again, see here
https://docs.nextcloud.com/server/16/admin_manual/configuration_server/index.html

Without DNS its a little bit tricky to configure this.
Take a look here: https://nextcloud.com/collaboraonline/

I also looked at that howto.

I really begin to think the problem is, I’ve not ssl encrypted my nextxloud domain.

Do you know how I add another ssl encryption for localhost:8080 , cause :9980 is already passed on collabora?
I already got an ssl conf file that looks like:

<IfModule mod_ssl.c>
<VirtualHost *:443>
  ServerName other-40.umwelt-campus.de

  SSLCertificateFile /etc/apache2/ssl/nextcloud.crt
  SSLCertificateKeyFile /etc/apache2/ssl/nextcloud.key

  # Encoded slashes need to be allowed
  AllowEncodedSlashes NoDecode
  # Container uses a unique non-signed certificate
  SSLProxyEngine On
  SSLProxyVerify None
  SSLProxyCheckPeerCN Off
  SSLProxyCheckPeerName Off
  # keep the host
  ProxyPreserveHost On
  # static html,
 js,
 images,
 etc. served from loolwsd
  # loleaflet is the client part of LibreOffice Online
  ProxyPass /loleaflet https://127.0.0.1:9980/loleaflet retry=0
  ProxyPassReverse /loleaflet https://127.0.0.1:9980/loleaflet
  # WOPI discovery URL
  ProxyPass /hosting/discovery https://127.0.0.1:9980/hosting/discovery retry=0
  ProxyPassReverse /hosting/discovery https://127.0.0.1:9980/hosting/discovery
  # Main websocket
  ProxyPassMatch "/lool/(.*)/ws$" wss://127.0.0.1:9980/lool/$1/ws nocanon
  # Admin Console websocket
  ProxyPass /lool/adminws wss://127.0.0.1:9980/lool/adminws
  # Download as,
 Fullscreen presentation and Image upload operations
  ProxyPass /lool https://127.0.0.1:9980/lool
  ProxyPassReverse /lool https://127.0.0.1:9980/lool
</VirtualHost>
</IfModule>

Can I add something to this file or do I need a new one?
(Also new key and crt files for localhost:8080)

This shout be your first setup. Then expand the setup step-by-step.

Okay, using owncload at least I get no error. The files just keep loading after opening them in owncloud. With.

Collabora Online: No connection can be established to the host “http://localhost:9980”.

Please ask your administrator to check the Collabora Online server settings. The exact error message was:cURL error 7: Failed to connect to localhost port 9980: Connection refused

Okay, I added http://other-40.umwelt-campus.de:9980 instead of localhost:9980 and the error disappeared. It just keeps loading…
“Waiting on localhost…”

Following this I don’t need ssl:

firewall open for port 9980?

@Reiner_Nippes yes.

I finally got to access collabora on https://other-40.umwelt-campus.de:9980 to get an “ok” response by setting ssl true with:
docker exec -it collabora /bin/bash -c "apt-get -y update && apt-get -y install xmlstarlet && xmlstarlet ed --inplace -u \"/config/ssl/enable\" -v true /etc/loolwsd/loolwsd.xml && xmlstarlet ed --inplace -u \"/config/ssl/termination\" -v true /etc/loolwsd/loolwsd.xml".

But connecting to it in owncloud I get:

other-40.umwelt-campus.de hat die Verbindung abgelehnt.

As you can see Quick try out works, and also nextcloud / lool works the same way. Forget to use copy / paste or try everything you can read …

@Combo_Breaker

is that a typo or why are you changing between http and https?


why do you try to edit the loolwsd.xml when you can do that with the extra parameters?

No, it’s on purpose. I tried both - http and https. But on https I get no access on owncloud even if I change the port.

ok. it’s only confusing.

on which protocol nextcloud is running? is it running in docker or native on os?

would you mind to draw a small sketch of your environment? the draw.io plugin in nextcloud might be helpful. :wink:

I changed to owncloud as ralfi recommended.

And I’m running everything as docker container. Owncloud and Collabora. And the only problem is the accessibility of owncloud via https.
There nust be something to change in my office.conf file in the vHost. But I don’t know what…

if this apache conf snippet is used inside your docker container, “127.0.0.1” is the same docker container. it’s not the “127.0.0.1” of the host system. and not the collabora container.

inside a docker container you have to use the “name” of the other docker container to start networking between them. docker uses it’s own internal network and dns to enable docker to talk to each other.

if you launch your collabora container with docker run -n collabora ...

ProxyPass /loleaflet https://collabora:9980/loleaflet retry=0

should do the trick.

but only if other-40.umwelt-campus.deis your nextcloud web server.

that is to say: all https request are processed by this web-server and therefore nextcloud.

only the /loleaflet, /hosting, /lool, ... requests are passed to the collabora container.

I don’t exactly get what you are trying to say by this. But I don’t use the apache conf file inside the container. It’s all defined on the host system. (If that’s what you meant)

Is not the owncloud service. Owncloud is running on other-40.umwelt-campus.de:8082